Architecture Docs Maintainer

Use this skill when any of the following are true:

• a doc in docs/architecture/ is created or updated
• docs/README.md changes to reflect architecture entrypoints
• docs/task.md changes because architecture status or seams changed
• a proposal's Disposition, Current Slice, or active seam list changes
• current implementation truth changed and ARCHITECTURE_STATUS.md may need an update
• a doc needs frontmatter, domain assignment, or relationship links

Workflow

1. Identify each touched doc's role:
   • status
   • reference
   • proposal
   • workflow
   • historical
2. Assign exactly one primary domain from the project's controlled vocabulary unless the doc is intentionally broad status/reference.
3. Ensure frontmatter exists and includes the minimum fields:
   • title
   • doc_type
   • domain
   • status
   • last_updated
   • tags
   • related_docs
   • task_refs when implementation work is relevant
4. Check that metadata and body agree:
   • proposal status matches the document's disposition language
   • status/reference docs describe current truth rather than aspiration
   • historical docs are labeled as such and not presented as active authority
5. Check the source-of-truth chain:
   • if current implemented behavior changed, update ARCHITECTURE_STATUS.md
   • if durable runtime structure changed, update ARCHITECTURE.md
   • if design direction or near-future work changed, update the relevant proposal
   • if execution sequencing changed, update docs/task.md
6. Add or refresh cross-links:
   • proposal -> status doc
   • proposal -> task surface
   • status doc -> active proposals/seams
   • docs index -> current entrypoints
7. Note stale prose or outdated references exposed by the metadata pass and either fix them or call them out explicitly.

Frontmatter Schema

Primary doc_type values:

• status
• reference
• proposal
• seam
• task-surface
• workflow
• historical

Primary status values:

• proposal or seam docs: proposed, accepted-current-slice, implemented, superseded, deferred
• status, reference, workflow docs: active, historical

Non-Negotiable Rules

• One primary domain per active doc.
• Keep tags lightweight; do not build a taxonomy cult.
• ARCHITECTURE_STATUS.md is for current truth and active seams, not wishlist prose.
• ARCHITECTURE.md is for durable architecture reference, not live queue state.
• Proposal docs are design space unless clearly marked implemented.
• docs/task.md is the execution surface, not the architecture encyclopedia.

Output Expectations

Report:

• which docs received metadata or linkage updates
• whether current truth, reference truth, and proposal truth still align
• any stale docs or historical narratives that remain risky
• the next doc seam worth tightening