Bind curators to memory engines #18
Notifications
Due Date
No due date set.
Depends on
Reference: sam/archie#18
Reference in new issue
Block a user
Wire the attached-memory-engine part of a curator's declared shape once the memory engine family exists, so a curator reads and writes through the engine contract rather than a concrete store.
Acceptance Criteria
A curator declares which memory engine it uses and receives it as a typed dependency. Swapping the configured engine changes where a curator's memories land with no change to the curator. A curator with no declared memory engine is a valid configuration and is rejected only if it attempts a memory operation.
Notes
Blocked on its own stated prerequisite, which is also still open: archie-core-1786637490069-11-e245c170 (Memory engine contract and owning registry). Current state: Manifest.MemoryEngine (internal/domain/curator/contract.go:59-63) is only a declared string name; Registrar (registrar.go) has no memory-engine field at all, so nothing actually binds an engine instance to a curator yet -- registry.go:128's agentic() check only tests MemoryEngine != "", it doesn't inject anything. Do not start this until the memory engine contract exists; there is nothing to bind to yet.
Close reason
Complete, all three AC clauses:
receives it as a typed dependency: curator.Registrar.MemoryEngines
(Get(name) (domainmemory.MemoryEngine, bool)), same trust model as
ToolBuilder.Build(ctx, declared) -- the curator calls Get with its own
declared name, not handed a pre-resolved instance. Registration
enforces presence exactly like Tools/Skills: declared with no
MemoryEngineSource on the host is rejected at Register
(TestRegistryDeclaredCapabilitiesRequireHostServices' two new cases),
and filter() clears the field from a curator's view when undeclared
(TestRegistryBindFiltersToDeclaredCapabilities).
curator code change: nothing about a curator names a concrete engine,
only the string it declared, resolved fresh through whichever registry
it was bound to.
now covered by table cases) and can only ever be affected by a memory
operation it structurally cannot attempt, since MemoryEngines is nil
in its view.
Wired end to end: internal/app/archied/bootstrap.go:setupCurators passes
b.memEngines (*domainmemory.Registry, set by setupMemoryAll which Run()
calls before setupCurators) straight in -- it already satisfies
MemoryEngineSource with no adapter.
go test ./... is green; task lint is 0 issues.
Imported from beads
archie-core-1786637499636-376-2f94082e· GitHub #397 · type feature · priority P2 · created 2026-08-08 · closed 2026-09-01