Stable routing
Object type determines location. Directory structure represents operational purpose rather than lifecycle state.
DEEP BUILD · MULTI-AGENT · ARCHITECTURE
A deterministic memory architecture experiment.
A substantial engineering project that explored how Codex, Claude Code and Hermes Agent could share one routing discipline, one durable business-memory vault and explicit read-only quality checks.
Codex / Claude Code / Hermes AgentMultiple agents, one memory contract
↓
Shared SkillBehavior and routing discipline
↓
Router + explicit diagnosticsDeterministic destinations · read-only quality checks
↓
Durable VaultBusiness memory remains separate from architecture code
01 / CORE IDEAS
Memory without lifecycle bureaucracy.
The architecture tried to keep routing deterministic while avoiding recurring human chores such as moving projects between Active and Completed folders or repeatedly approving decisions already made.
Skill vs. storage
The Skill controls behavior and routing; the durable Vault stores business memory. Derived tools are not allowed to become a second source of truth.
Human-cost policy
Routine routing, metadata and deterministic maintenance should be handled by the Agent, reserving human attention for real ambiguity, authority and risk.
02 / ARCHITECTURE
A small set of explicit layers.
The repository stores architecture, router code, tests and maintenance tooling — not live business memory itself.
Shared SkillDefines memory behavior and routing discipline across supported agents.
RouterResolves deterministic destination paths before persistent writes when the destination is not already explicit.
Knowledge qualityRead-only checks for authority, provenance and possible duplicate-title issues.
VaultThe durable business-memory store, deliberately separated from code and diagnostics.
03 / ENGINEERING LESSON
Do not turn memory into a second operating system.
The project progressively removed migration-only tooling and superseded architecture copies from the active tree, relying on Git history instead of keeping old rules beside current rules.
Lifecycle-neutral projects
Named project work stays in one stable project home. Draft, review, publication or retirement status does not require moving the source between root folders.
Explicit maintenance
No silent self-update or automatic repository-version checking during normal memory work. Updates are initiated deliberately.
Current status
armor-memory is now best understood as a standalone engineering artifact from an earlier stage of the EAO architecture. The current EAO knowledge architecture has moved on and does not use armor-memory / armor-vault as its authority. The repository remains useful as a record of the routing, authority and human-cost design problems explored during that stage.