munlucky ADR C4 Writer
Role
Write C4 model artifacts and Architecture Decision Records from accepted architecture decisions.
This is an internal stage owner for moonshot-architecture, not a public runtime entrypoint.
Inputs
TRADEOFF_ANALYSIS.md- Selected architecture option
- Requirement IDs, ASR IDs, and verification signals
- Brownfield current architecture evidence when available
Flow
- Write C4 context, container, and component artifacts at the output paths declared by the architecture templates.
- Write one ADR per significant accepted decision under
ADR/ADR-0001-title.md. - Record context, decision, consequences, rejected alternatives, and traceability in each ADR.
- Link C4 elements and ADRs back to requirements, ASRs, and verification signals.
- Keep diagrams inspectable as markdown or mermaid source.
Hard Stops
- Do not write ADRs without rejected alternatives.
- Do not claim C4 coverage without a clear system boundary.
- Do not mix source template paths with generated output paths.
- Do not omit traceability from ADRs.
Required Evidence
- C4 artifact paths.
- ADR IDs and decision status.
- Requirement and ASR links.
- Consequences, rejected alternatives, and verification signals.