Architecture Filing
Specific system architecture, service boundaries, infrastructure, and technical designs go in
architecture/.
Resolver Status
This is a resolver companion page. The canonical filing rule lives in Filing Decision Tree. Use Wiki Brain Operating Model first to decide whether the knowledge should become a standalone page, section, ledger row, generated view, redirect, or no durable write. Then use this page as a compact retrieval handle for the local rule. Source: User request, 2026-07-01
File Here
- Data flow, service boundaries, infra topology, auth/billing/deployment architecture, system comparisons, and technical design records.
- Architecture that is reusable but still tied to a concrete system.
- Harness, runtime, memory, control-plane, distributed-system, product-system, or research-infrastructure designs that need boundaries, invariants, flows, and proof obligations.
Do Not File Here
- General reusable principles: use
concepts/. - The project's whole operating context: use
projects/. - Code-style conventions: use
style/.
Local Routing
Read Architecture System Map after this page. It names the current architecture families and records why the 2026-07-01 pass added Agent Harness Architecture rather than merging existing harness pages.
Create a new architecture article only when the subject owns a distinct system boundary. If it only compares sibling pages, update the relevant family page. If it only records one implementation detail, fold it into the project page or the existing architecture article.
Every architecture page should answer:
- boundary owned
- components inside the boundary
- data/control flow
- invariants and failure modes
- proof needed before claiming the architecture still holds
Closeout
If this rule changes, update Filing Decision Tree first, then this companion page, relevant directory READMEs, generated packs if routing changed, wiki/_index.md, qmd, and wiki/log.md. Source: Index Logging Protocol, 2026-07-01
Timeline
- 2026-07-01 | Linked this resolver companion to Architecture System Map and the new Agent Harness Architecture family page so architecture filing uses the same boundary, invariant, and proof contract as the refreshed article category. Source: User request, 2026-07-01
- 2026-07-01 | Updated this resolver companion to align with the current filing authority stack: Wiki Brain Operating Model for shape, Filing Decision Tree for directory placement, and Index Logging Protocol for closeout. Source: User request, 2026-07-01
- 2026-05-31 | Architecture filing from RESOLVER. Source: public wiki expansion, 2026-05-31