58f3d40683a3b261bf22c6dcbe88a9b4fe153f9a
The layering was written down in docs/architecture/organisation.md and approved, but nothing an agent reads first pointed at it. Reading internal/ cold shows ~35 packages side by side, so the obvious move is to add a thirty-sixth -- which is how the flat layout kept regrowing, and untangling it cost a week. The section states the four layers and their ownership, names the dependency direction as the invariant, and explains why the layers stay under internal/: it is a compiler-enforced visibility boundary, so hoisting one to the repository root would make Archie's domain types importable by any dependent module and commit us to API stability on exactly the code that most needs to keep changing. Cross-cutting packages get a checkable definition rather than a vibe: a package that may be imported by any layer and imports none of them. logging, events, eventbus and taskstate each have zero inward imports today, which is what lets them sit outside the dependency direction -- they are sinks, never sources. It doubles as the failure test: the moment one imports a domain type it has become misfiled domain code. Deliberately no shared/ directory. A directory named for a category becomes where things go when nobody can say what they are. Refs archie-core-5d7
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.8%
Vue
13.1%
TypeScript
7.8%
JavaScript
1.2%
Shell
0.6%
Other
0.4%