EP056 — Map how the business works

Modular implementation workflow · Load business information and build interactive maps of internal activities, inputs, outputs, deliverables and data movement.

6Standalone functional modules
M01 firstNotes → interactive process map
1 / 6M01 complete · five modules planned

First understand the business today. Revenue generation, cost reduction and opportunity recommendations are outside this implementation scope. This page is a delivery plan, not evidence that the application has been built.

What “standalone” means for every module
Common record contract · small, portable and versioned

Each package has schemaVersion, packageId, revision, businessId (optional), createdAt, sources and module-specific entities. Entities use stable IDs. Claims carry status, sourceId + locator, and an inference reason when applicable. Unknowns remain explicit; source presence alone does not establish truth.

A workflow activity contains purpose, trigger, inputs, work/decisions, outputs, deliverables, actor, systems and data operations. Edges distinguish control flow, data flow and cross-function hand-offs. Store JSON plus source files initially; keep analysis and validation separate from the renderer.

Every tool validates imported versions and references before modifying its saved record. Unsupported versions get a clear error, not a partial silent import. Export includes unresolved references and available provenance.

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.

  1. Choose one real process and record the explicit facts and source excerpts expected in its map.
  2. M01 is complete for its deterministic parser scope; let the business owner correct the map before adding the next module.
  3. As modules become available, test M02 source bundle → M01, M01 → M03, M03 → M04/M05, and exported packages → M06.
  4. 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.
  5. 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.