Architecture System Map

Architecture pages are system maps with invariants: they name boundaries, components, flows, failure modes, and proof obligations so future implementation can preserve the system's shape.

Use this page when choosing which architecture article to read or update. Use the wiki/architecture/README.md router for the category writing standard. Use Filing Decision Tree when deciding whether a new page belongs in architecture/ at all.

Architecture Families

Merge Decisions

No existing architecture pages were merged in the 2026-07-01 pass. The reason is not "never merge architecture"; it is that the current pages mostly answer different boundary questions.

Page Contract

An architecture article should answer five questions:

1. What system boundary does this page own?
2. What components are inside the boundary?
3. What data/control flow crosses the boundary?
4. What invariants prevent the known failure modes?
5. What proof should an agent collect before claiming the architecture still holds?

If an article cannot answer those questions, fold it into a stronger page, move it to concepts/, or turn it into a ledger row.

Update Rule

When updating any architecture page:

• update its updated: date
• add or preserve a one-line lead
• keep related architecture family links current
• preserve timeline evidence
• cite project/source pages when the architecture is project-specific
• regenerate _index.md, backlinks, and qmd
• log structural changes in wiki/log.md

---

Timeline

• 2026-07-16 | Added the workflow-first brain family and kept the Daily Brief control plane separate from source evidence, master planning, and exhaustive workflow/capability census because each owns a distinct boundary and update path. Source: User request; Daily Brief Control Plane
• 2026-07-01 | Created as the category-level system map for the Architecture rewrite. Added architecture families, merge decisions, and the page contract used to update all architecture articles. Source: User request, 2026-07-01