Full arc42, chapter by chapter
Every one of the twelve arc42 sections — from Introduction and Goals through
Quality Requirements to Architecture Decisions — is generated as its own task,
with the context of the previous chapters and the role that chapter plays in the document.
Diagrams as a first-class output
Container, component, sequence, deployment, context — generated as code (Mermaid, PlantUML, C4-DSL),
not as flat images. Embedded in the chapter where they belong, edited in the same editor as the
prose, rendered live in the browser.
Re-runs that don't trash the document
When the system changes, you regenerate one chapter or one diagram. The rest of the document stays
put. No "ChatGPT just rewrote section 4 in a slightly different style than section 5" — Architeeli
re-uses the same chapter template, the same glossary, the same decisions.