Specimen. The structure of the process map, re-drawn. The content is the method as already published on The operating model §2, generalised; no project's source text, names or figures.

The process map: one session, six phases, one phase of the release

Each session runs the six phases once, for one phase of the release. The documents carry the state between sessions, not the session itself. The loop closes by writing the next session's starting point.

1. 1Sync and orient

   Fetch from the remote before reading any file; bring the local copy level if it is behind.

   Readsprogress log + next pickrelease master spec
   Writesnothing

   Each is read once. A status question is never answered from a tree that has not been fetched.

2. 2Scope and gate

   Confirm the one phase with the owner, its boundaries and open decisions; then the standing gates.

   Readsthe standing gates, in order
   Writesnothing yet: the scope is agreed, then written in phase 3

   Scope shape by risk: extending existing plumbing is scoped and built in one pass; a new model or an open external question stops at the spec.

3. 3Spec first

   Write the phase spec before any code: objective, scope in and out, exit checks.

   Readsmaster spec
   Writesphase spec

   Non-functional targets are declared as numbers to be measured. If the scope moves, the spec says so.

4. 4Build and verify

   Exercise the increment against the running stack with re-runnable scripts; measure each target at a stated scale.

   Readsphase spec
   Writescode-review file + resolutionsbacklog or desktop queue

   Every number tagged measured or projected. The review is written to its own file before the reviewer returns; each finding gets fixed, not taken (with the reason) or deferred.

5. 5Demo and sign-off

   Run the demo on real data from the runbook; capture the evidence.

   Readsrunbook
   Writesrunbook journeyssign-off log

   Journeys go into the runbook before the demo runs; a serving check confirms the running server is the committed code. No self-sign-off: until the owner approves, it is "built, awaiting sign-off".

6. 6Close out and hand off

   Commit what changed and why, tag the phase, push, roll off the progress log if over its cap, then end the session.

   Writesuser guideas-built diagrams (at a release)progress log + next pick

   A phase that changed what a user sees updates the user guide in the same session, or the gap is recorded as debt.

The next session starts at phase 1 by reading the progress log and the next pick this one wrote.