Workflow - New Capability to Final Architecture

Use this when a capability does not yet exist in the vault and you need to go from idea to an approved architecture.

5-Minute Path

1. Create investigation note in 10-topics/domain-folder/.
2. Create a minimal architecture note early with status: draft.
3. Capture options, risks, and open questions.
4. Promote to reference topic when the story stabilizes.
5. Record the decision in an ADR.
6. Evolve draft architecture to active architecture as decisions close.
7. Link TOGAF/workpackage notes only when they add traceability value.

Detailed Steps

1) Investigation

• Create topic-your-scope-investigation.md (type: topic, subtype: investigation).
• Focus on unknowns, alternatives, assumptions, and decision drivers.

1b) Early Architecture Draft

• Create a lightweight type: architecture note in 20-architecture/domain-folder/ with status: draft.
• Keep it small: scope, assumptions, and open questions are enough for the first version.
• Use workflow-draft-architecture-first for the minimum checklist.

2) Reference Topic

• Create topic-your-scope.md (subtype: knowledge) when findings become reusable knowledge.
• Set investigation to status: closed and link via promoted_to or related.

3) ADR

• Create 30-decisions/domain-folder/adr-XXX-your-scope.md.
• Capture options, trade-offs, and consequences.

4) Architecture

• Create or update a type: architecture note in 20-architecture/domain-folder/.
• Include ## Applicable Principles and links to driving ADR/topic notes.

5) Optional Traceability Lenses

• TOGAF: add ABB/SBB notes if capability-to-solution mapping needs to be explicit.
• Workpackage: add/update when implementation sequencing, ownership, or dependencies matter.

Done Criteria

• Decision is traceable (topic -> ADR -> architecture).
• Links are resolvable and validation passes.
• Domain landing/index pages reference the new canonical note where appropriate.