Document catalog — v1

The re-authored methodology's document set. Phase/slug naming (REQ-30). Minimum sufficient: an engagement's profile activates only the documents it needs; nothing here is owed by default except discovery/vision and discovery/scope.

discovery/vision

• Purpose: the whole — what we are building and why, readable in five minutes.
• Sections: the promise · the loop (one chapter per capability, scenarios embedded) · success criteria · open questions.
• Holds: capability, scenario (embedded), clarification. Narrative-heavy; embeds over restatement.
• Tailoring: always active.

discovery/scope

• Purpose: what is agreed — the document baselines pin and change control diffs.
• Sections: functional domains (REPEATING — one per domain, each holding its scenarios and requirements, REQ-25 grouping) · non-functional requirements · assumptions · out of scope.
• Holds: scenario, requirement, assumption.
• Tailoring: always active.

discovery/context

• Purpose: the world the system lands in.
• Sections: stakeholders · as-is and pain points · constraints (technical, legal, organisational).
• Tailoring: optional — activate for greenfield or organisationally complex engagements.

discovery/system

• Purpose: the full system end to end, high level — the discovery report a reader scopes from. Describes the optimal platform including proposed scope, clearly marked.
• Sections: the journey (phase by phase, scenarios embedded) · integrations · information architecture · status and roadmap.
• Holds: capability, scenario, requirement (embedded), reference. Narrative-heavy.
• Tailoring: always active for discovery engagements. (Added 2026-07-07 after DOC-5 used it ad hoc.)

design/solution

• Purpose: how it gets built — decisions with rationale.
• Sections: architecture decisions · data model · security and compliance.
• Holds: decision, risk, requirement (technical).
• Tailoring: activates when build scope is confirmed.

design/integrations

• Purpose: every boundary with an external system.
• Sections: REPEATING — one per external system (e.g. design/integrations > cvr), each per the integration content spec.
• Holds: requirement (technical), decision, risk, clarification.
• Tailoring: activates when the engagement has integrations. (The old D0180, re-authored.)

delivery/plan

• Purpose: increments and milestones — which stream delivers what, against which baseline.
• Holds: increment, milestone-style decisions.
• Tailoring: activates at first increment.

delivery/status

• Purpose: computed only — rendered from item states, queue latencies, drift vs baseline. Never authored (REQ-8).

agreement/baseline-N

• Purpose: generated, signable snapshots (REQ-13). Never authored.

ops/runbook

• Purpose: operations handover. Deferred until a go-live approaches.

Resolved at approval (2026-07-07): discovery/context stays in v1 as optional · delivery/plan remains a document (revisit once computed status views mature) · further gaps are raised as review comments against this catalog.

Narrative rules — every document owes a reading line

The thin red line is mandatory, not a style preference. Every document, human- or agent-authored:

1. Opens with "How to read this document" — two to four sentences: what this is, who it serves, how the sections flow.
2. Every section opens with a short introduction (1-3 sentences) framing what follows and how its items relate — before any embed appears.
3. No unframed embeds. An embed without a framing sentence is a database dump, not a document.
4. Order follows the story, not the record — sections and embeds are sequenced for a reader, typically along the delivery loop or decision order.
5. These rules are compiled into every drafting agent's briefing (REQ-31) and checked at document review.