Record the memory engine family alongside the existing engine documentation so the contract, its lifecycle guarantees, and the trust boundary for third-party memory backends are written down where the plugin engine rule already lives.
Acceptance Criteria
ARCHITECTURE.md describes the memory engine contract, its owning manager, lifecycle and failure isolation, and states the trust boundary for an out-of-process or third-party memory backend. The shared CLAUDE.md/AGENTS.md source is updated if the rule surface changes.
Close reason
Documented the memory engine contract, owning manager, lifecycle/failure isolation, and third-party trust boundary in ARCHITECTURE.md; focused memory tests pass.
Imported from beads archie-core-1786637489985-8-13b9d8a8 · GitHub #29 · type task · priority P2 · created 2026-08-08 · closed 2026-08-15
Record the memory engine family alongside the existing engine documentation so the contract, its lifecycle guarantees, and the trust boundary for third-party memory backends are written down where the plugin engine rule already lives.
### Acceptance Criteria
ARCHITECTURE.md describes the memory engine contract, its owning manager, lifecycle and failure isolation, and states the trust boundary for an out-of-process or third-party memory backend. The shared CLAUDE.md/AGENTS.md source is updated if the rule surface changes.
### Close reason
Documented the memory engine contract, owning manager, lifecycle/failure isolation, and third-party trust boundary in ARCHITECTURE.md; focused memory tests pass.
---
_Imported from beads `archie-core-1786637489985-8-13b9d8a8` · GitHub #29 · type task · priority P2 · created 2026-08-08 · closed 2026-08-15_
sam
added the mediumtask labels 2026-10-27 13:34:33 +00:00
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Record the memory engine family alongside the existing engine documentation so the contract, its lifecycle guarantees, and the trust boundary for third-party memory backends are written down where the plugin engine rule already lives.
Acceptance Criteria
ARCHITECTURE.md describes the memory engine contract, its owning manager, lifecycle and failure isolation, and states the trust boundary for an out-of-process or third-party memory backend. The shared CLAUDE.md/AGENTS.md source is updated if the rule surface changes.
Close reason
Documented the memory engine contract, owning manager, lifecycle/failure isolation, and third-party trust boundary in ARCHITECTURE.md; focused memory tests pass.
Imported from beads
archie-core-1786637489985-8-13b9d8a8· GitHub #29 · type task · priority P2 · created 2026-08-08 · closed 2026-08-15