Three defects the first sweep left behind, each caught by a rule the guard did not yet have. Statuses. RULES.md gives three; the tree had 25 values, and the free-text ones were carrying progress. "Implemented (wiring landed)" and "Ratified (rev. 2e). Rev. 2e adds the OpenTaskByPR lookup. Rev. 2d revised section 10..." were both changelogs living in the one field the other rules exempt. Every PRD now declares Draft, Approved or Finalised and nothing else; five that declared nothing now declare one. A revision number moves to **Revision:**, a pointer to the authoritative document to **Authority:**, and what a past revision changed to git. CLAUDE.md's citation of state-store-contract rev. 2e still resolves. Stale cross-references. "Supersedes the 2026-09-03 open question", "this bullet previously said", "an earlier draft of this document claimed" all point at text the reader cannot see, because it was replaced. A supersede marker survives only when it names a file, a section or a symbol that can be found. Temporal hedges. 100 uses of today, currently and right now across 31 files. Each dates its sentence to the day it was written: "[notify] today is one webhook URL, read in one place" stops being true the moment this design lands, while still reading as the premise it rests on. The header-field exemption was also too wide. "**Date:** 2026-09-03, Channel resolved 2026-09-22" smuggled a dated status into the one line the rules did not read; the exemption is now a Date holding only a date and a Status holding only one of the three.
4.2 KiB
Architecture Decision Index
Status: Approved
Date: 2026-07-28
Beads issue: archie-core-5d7
Purpose
This file is the navigation point for Archie's target architecture. It is deliberately short. Architectural decisions are separated by domain or requirement so an implementation task can load only the rules governing its scope.
Implementers MUST read the decision document for the domain or requirement they are changing. They MUST NOT infer permission to change neighbouring domains from a broader restructuring objective.
Global invariants
- Organise code around cohesive application responsibilities, not generic technical mechanisms.
- Domains own their behaviour, vocabulary, state, commands, events, policy implementations, runtime settings, and required service contracts.
- Domains do not depend on infrastructure or manipulate another domain.
internal/appowns composition;cmd/*remains thin.- Cross-domain work uses an explicitly owned command, event, or approved shared contract.
- Process boundaries are deployment choices and do not determine source-code ownership.
- Existing package names and boundaries have no presumption of survival.
The words MUST, MUST NOT, SHOULD, and MAY are normative.
Decision documents
| Scope | Authoritative document |
|---|---|
| Repository layout, domains, composition, deployments, and optional material | architecture/organisation.md |
| Dependency direction, domain contracts, infrastructure, commands, events, and wire contracts | architecture/dependencies-and-contracts.md |
External configuration, runtime settings, and dissolution of internal/config |
architecture/configuration.md |
| Persistent actor identity, ownership, lifecycle, and attribution | architecture/identity.md |
| Agent definitions, workflows, workflow executions, tools, and worker boundaries | architecture/agent-system.md |
| Personal-assistant interactions, messaging channels, and optional promotion into durable work | architecture/messaging-and-work-intake.md |
| Shared policy evaluation and domain-owned policy semantics | architecture/policy.md |
| Safe source/configuration changes, health supervision, and recovery | architecture/safe-change-and-recovery.md |
| Plugin framework, plugin implementations, and extension isolation | architecture/plugins-and-extensions.md |
| Generated references, deprecations, and changelog generation | architecture/generated-documentation.md |
| Remaining package destinations, data migrations, runtime cutover, and completion criteria | architecture/migration-decisions.md |
| Domain/feature research, design interview, and required handoff | architecture/package-review.md |
Deferred decisions
The remaining package-placement, data-migration, shared-mechanics, process- boundary, and cutover decisions are maintained in architecture/migration-decisions.md.
Each decision is made in its focused document after code-grounded review.