f4438843fee206a13d25878fffc8be7065fe130b
The Scope discipline section used to open by declaring the architecture documentation "complete and authoritative ... not a draft to extend", and then banned producing "new architecture documents, migration plans ... decision records" outright. That was already false in this tree. docs/architecture/migration-decisions.md is titled "Active migration inventory" and exists to record "what remains to be decided before Archie's current implementation can be migrated into the approved domain-oriented structure". The Architecture section of this same file points agents at it for "the recorded position and what was agreed next". docs/prds/ holds an active PRD and docs/archive/prds/ shows PRDs are a normal artifact here. So the rule asserted the design was finished while the repo shipped an open decision register, and banned the exact artifact type that register is made of. What changed in MEANING: the gate used to be "is this a document" and is now "is there a settled design for this". Where a settled design exists, nothing changes -- implement it, and prose instead of a diff is still the failure. Where none exists (new capability, or an open item in migration-decisions.md) designing first is now REQUIRED rather than prohibited. The old ban was a proxy. What it meant to stop was prose substituting for a diff, and it stopped that by banning the artifact instead of the behaviour. Proxy rules hold right up until the work is genuinely new -- which is when this one broke, and when designing first matters most: accreting diffs toward a new architecture without deciding its shape is how the flat internal/ layout happened, and CLAUDE.md already says undoing that is measured in weeks. The anti-sprawl teeth are kept and made checkable rather than categorical: one page, it decides rather than surveys, it lands in a named home (docs/prds/ or migration-decisions.md), it is unfinished until a diff follows, and anything a reader could have learned from the code gets cut. Ownership ledgers, inventories, current-state traces, review campaigns and planning/refactor issues stay prohibited -- none of those were ever design. AGENTS.md is a symlink to this file, so every harness picks this up.
Description
Archie connects events from your systems to agents that can investigate, reason, and act.
Define what an event means, map its data into a workflow, and give that workflow an agent equipped for the job: its own execution environment, tools, and identity.
https://archie.catlow.cloud
133 MiB
0 Stars
1 Watchers
0 Forks
Releases
11
Archie v1.62.0
Latest
Languages
Go
76.7%
Vue
13.1%
TypeScript
7.8%
JavaScript
1.2%
Shell
0.6%
Other
0.4%