Bind curators to memory engines #18

Closed
opened 2026-10-27 13:34:37 +00:00 by sam · 0 comments
Owner

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:

  • A curator declares its memory engine via Manifest.MemoryEngine and
    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).
  • Swapping the configured engine changes where memories land with no
    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.
  • A curator with no declared engine stays valid (pre-existing behavior,
    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

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: - A curator declares its memory engine via Manifest.MemoryEngine and 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). - Swapping the configured engine changes where memories land with no 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. - A curator with no declared engine stays valid (pre-existing behavior, 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_
sam added the mediumfeature labels 2026-10-27 13:34:37 +00:00
sam self-assigned this 2026-10-27 13:34:37 +00:00
sam closed this issue 2026-10-27 13:34:37 +00:00
sam added a new dependency 2026-10-27 13:41:39 +00:00
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Reference: sam/archie#18