arc42-arch-doclisted

# arc42-arch-doc Produces a **software architecture document** following the **arc42** template (arc42.org): a stable, 12-section structure for describing what a system is, how it is built, and why those choices were made. The output is *declarative knowledge about a system* — semantic, not a time-stamped event log and not a step-by-step procedure. ## The 12 arc42 sections (industry pattern) Document them in order. Each has a defined job; do not merge or skip the load-bearing ones (Section 1, Section 3, Section 5, Section 8, Section 9). 1. **Section 1 — Introduction and Goals** — what the system does, its top 3–5 quality goals, and the key stakeholders (role → concern/expectation). 2. **Section 2 — Architecture Constraints** — fixed rules the architecture must obey (technical, organizational, regulatory) that are *not* free design choices. 3. **Section 3 — Context and Scope** — the system as a black box: external actors and neighboring systems, plus the business and technical interfaces crossing the boundary. Defines what is in vs. out of scope. 4. **Section 4 — Solution Strategy** — the handful of fundamental decisions (technology, decomposition approach, key patterns) that shape everything else; a short bridge from goals (Section 1) to structure (Section 5). 5. **Section 5 — Building Block View** — the static decomposition: the system broken into black-box building blocks (level 1), then their responsibilities and, where useful, their internal