Click a module for implementation steps, standalone use, contracts and acceptance criteria. Lanes show suggested release order, not mandatory runtime dependencies.
Composition gate — after standalone releases
Integration milestone, not a seventh module and not a prerequisite for independent use.
- Choose one real process and record the explicit facts and source excerpts expected in its map.
- M01 is complete for its deterministic parser scope; let the business owner correct the map before adding the next module.
- As modules become available, test M02 source bundle → M01, M01 → M03, M03 → M04/M05, and exported packages → M06.
- Verify stable IDs, source locators, decisions, data edges and reviewer corrections survive each round-trip. Never mark a link passed based only on module-level fixtures.
- Only then provide a shared navigation shell and record folder. Each module must still launch independently after composition.
Completion test: import a real business source, generate a process, edit a hand-off, trace a deliverable, place it in a function and review its evidence. Save/reopen and export/reimport with no lost provenance or edits.
Evidence: M01 evidence is captured; composition remains pending until M02–M06 exist.
Release evidence policy
Advance a module only after its functional acceptance test passes.
- 0% planned; 25% validated input and contract; 50% core function; 75% usable interface with persistence/export; 100% standalone acceptance, negative cases and evidence complete.
- Keep implementation status in the source plan with links to captured evidence. This page does not offer checkboxes that imply unverified completion.
- For each release capture launch instructions, tests, representative exports and before/action/reload screenshots. Stop on a failed prerequisite.
- Human acceptance checks that the map accurately describes the business; schema validation alone cannot establish that.