The knowledge base comes from the model itself (Path D). The first real step is mapping the whole app, run without asking, followed by the one question the user owns: what to do with each top finding. The project may park there until a change is named; Stage 0b then adds the blast radius of the slice, read from the map. A regression net goes under the app before anything changes, and every gate from Stage 5 on is also a regression gate.
+The knowledge base comes from the model itself (Path D). The first real step is mapping the whole app, run without asking, followed by the one question the user owns: what to do with each top finding. The project may park there until a change is named; Stage 0b then asks what the user wants to work on, whether there are input documents, and what else it touches, read from the map. A regression net goes under the app before anything changes, and every gate from Stage 5 on is also a regression gate.
flowchart TD P["P Kickoff light
./mxcli in place, then init-project.sh
open question: what is driving it?
register: Change an existing app CONFIRMED"] --> M["0a Map the app, not asked, just run
bin/app-facts.sh then bin/app-report.sh
(app-analysis.md, about a minute)"] @@ -254,18 +254,18 @@Change an existing app A live .mpr yo PARK -.->|change arrives| S0 PK -- "only audits / tests wanted" --> AS["switch to existing-app-assurance
Track A starts from the same report"] PK -- "yes" --> S0 - S0["0b Triage ✋ which slice,
what is its blast radius"] --> S0a["blast radius into triage.md, read from the map:
dependencies.json tangles and edges,
then associations, SEARCH, SHOW PAGES IN,
published / consumed services"] + S0["0b Scope ✋ what do you want to work on,
what else does it touch"] --> S0a["what it touches into triage.md, read from the map:
dependencies.json tangles and edges,
then associations, SEARCH, SHOW PAGES IN,
published / consumed services"] S0a --> S0b["capability map from SHOW MODULES
extraction rows N/A
CAC-1, sign-off"] S0b --> RN["Regression net under the app
Track B baseline from existing-app-assurance"] - RN --> S1["1 Analysis Path D
DESCRIBE ENTITY, SHOW MICROFLOWS IN,
graph-report scoped to slice + blast radius
counts recorded, Path A = N/A, CAC-1b"] - S1 --> S2["2 Requirements
slice-only BRDs, as-is / to-be
CAC-2, CAC-3"] + RN --> S1["1 Analysis Path D
DESCRIBE ENTITY, SHOW MICROFLOWS IN,
graph-report scoped to the change + what it touches
counts recorded, Path A = N/A, CAC-1b"] + S1 --> S2["2 Requirements
BRDs for what changes only, as-is / to-be
CAC-2, CAC-3"] S2 --> Q{"crosses a module boundary,
adds an integration,
alters the domain model?"} Q -- "yes" --> S3["3 Architecture and Design ✋ in full
wireframes for changed screens only
design system = captured existing styling"] Q -- "no" --> S3b["3 collapses to:
which existing module owns this"] S3 --> S4 - S3b --> S4["4 Build Plan ✋ slice only
respects live data
coverage ledger = mxcli brain plan
CAC-5, build-ready"] + S3b --> S4["4 Build Plan ✋ what changes only
respects live data
coverage ledger = mxcli brain plan
CAC-5, build-ready"] S4 --> S5["5 Build
module loop + regression net must stay green
mxcli brain capture per leaf"] - S5 --> S6["6 Test
slice journeys + full regression suite"] + S5 --> S6["6 Test
journeys of the change + full regression suite"] S6 --> S7["7 Cutover N/A: the app is live"] classDef stop fill:#f8dedb,stroke:#b3261e,color:#1d2430 class S0,S3,S4 stop @@ -278,12 +278,12 @@Change an existing app A live .mpr yo
Step What it does Scripts and commands P light Scaffold. Intake answers come from the model, not from the user's memory. Run the machine check once. bin/doctor.shbin/init-project.sh <project>- 0a Map the app Run, do not ask: it is read-only and takes about a minute. Inventory, module tangles, loop-risk microflows, dead elements, with a fix-first list. Show the report and ask the user to disposition each top finding (fix in this work / log / accept); answers go to PROJECT.md. The project may then park until a change is named. Owed in this mode as theapp-reportartifact. Lint, security matrix and marketplace drift fill the report's Security and Lint sections.bin/app-facts.sh(app-analysis.md)bin/app-report.sh <project>./mxcli lint -p app.mpr./mxcli -p app.mpr -c "SHOW SECURITY MATRIX"./mxcli marketplace diff <content-id> -p app.mpr(v0.18+)+ 0b Triage ✋ Once the change is named: which slice, and what is its blast radius, starting from the map's tangles and edges. The radius is written into triage.mdas its own section, with counts. Capability map from the module list. CAC-1 and sign-off.SHOW ASSOCIATIONS IN <Module>·DESCRIBE ENTITY M.ESEARCH '<entity>'·SHOW PAGES IN <Module>SHOW REFERENCES OF M.E·SHOW IMPACT OF M.Eanalysis/app-facts/dependencies.jsonfor the tanglebin/gate-check.sh <project> 00b Scope ✋ Once the change is named: what do you want to work on, do you have input documents, and what else does it touch — starting from the map's tangles and edges. What it touches is written into triage.mdas its own section, with counts. Capability map from the module list. CAC-1 and sign-off.SHOW ASSOCIATIONS IN <Module>·DESCRIBE ENTITY M.ESEARCH '<entity>'·SHOW PAGES IN <Module>SHOW REFERENCES OF M.E·SHOW IMPACT OF M.Eanalysis/app-facts/dependencies.jsonfor the tanglebin/gate-check.sh <project> 0- Regression net Track B from the assurance skill, before any change: harness, action inventory, one journey per action, DB assertions, wiring sweep, LOOK pass, committed baseline. see Track B below project-bin/coverage-preflight.sh --assess --module <M>+ 1 Path D Query the model into the knowledge base, scoped to slice plus blast radius. Record counts. Path A declared N/A with attribution. Path C matters most here: the people who know why the app is the way it is. SHOW ENTITIES IN·DESCRIBE ENTITY·SHOW MICROFLOWS INDESCRIBE MICROFLOW·DESCRIBE PAGEbin/extraction-report.sh <project>bin/gate-check.sh <project> 11 Path D Query the model into the knowledge base, scoped to the change plus what it touches. Record counts. Path A declared N/A with attribution. Path C matters most here: the people who know why the app is the way it is. SHOW ENTITIES IN·DESCRIBE ENTITY·SHOW MICROFLOWS INDESCRIBE MICROFLOW·DESCRIBE PAGEbin/extraction-report.sh <project>bin/gate-check.sh <project> 12 Requirements One as-is / to-be BRD per capability being changed. Nothing for the untouched rest. bin/brd-report.sh·bin/open-questions.sh --stage 2- 3 Design Full only when the change crosses a module boundary, adds an integration or alters the domain model. Otherwise "which module owns this". Wireframes for changed screens only. bin/gate-check.sh <project> 3+ 4 Build plan ✋ Slice-only plan that respects live data. Coverage ledger lives in the brain, not a hand-kept file. ./mxcli brain init·./mxcli brain planbin/gate-check.sh <project> build-ready4 Build plan ✋ Plan for what changes only, that respects live data. Coverage ledger lives in the brain, not a hand-kept file. ./mxcli brain init·./mxcli brain planbin/gate-check.sh <project> build-ready5–6 Module loop unchanged. Every gate also re-runs the regression net. Each finished leaf is captured in the brain. bin/exec.sh s.mdl·project-bin/verify-module.sh <M>./mxcli brain capture "<leaf>"·./mxcli brain check7 N/A in the register: the app is already live. register line only