Persistent session-memory curator (reference implementation) #14

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

Ship a curator that maintains durable memory across sessions -- extracting and consolidating what is worth keeping from conversation history into the attached memory engine. The second contract consumer, and the one that exercises the curator/memory-engine binding.

Acceptance Criteria

Registers and runs through the registry with no special-casing. Writes through the memory engine contract rather than any concrete store. Extraction runs off the hot path so a chat turn never waits on it. What it wrote and why is inspectable. Honours the trigger-accounting invariant so its own writes do not reschedule it.

Close reason

Complete, all four AC clauses. Design decided first in
docs/prds/session-memory-curator.md, most notably: Observation.Identity
is the session ID, not a user/cross-session identity -- migration-
decisions.md#5's memory-scope mapping is still explicitly open and this
issue has no business deciding it unilaterally.

  • Registers and runs through curator.Registry with no special-casing
    (TestRegistersAndRunsThroughTheRegistry).
  • Writes through the memory engine contract, never a concrete store:
    Registrar.MemoryEngines.Get(name).Write, same trust model every other
    curator capability uses.
  • Extraction runs off the hot path: the model call happens inside Pass,
    which the curator runtime already runs off a chat turn's own
    goroutine.
  • What it wrote and why is inspectable: one memory.extracted Action per
    session with a count, through the existing curator activity tracker.
  • Honours the trigger-accounting invariant: Manifest.OnInput = true
    wakes it via the existing WakeOnPrimaryInput wiring, which already
    excludes every curator-derived event kind -- no new code needed for
    that guarantee to hold here.

Wired end to end: internal/app/archied/bootstrap.go:setupCurators,
adapters for gateway.SessionStore (internal/infrastructure/
sessioncurator/adapter.go) and the shared ai-sdk runtime
(curatorLLMRunner, main.go).

Caught and fixed during implementation: a model-call failure and an
unparseable model response were originally conflated into the same
swallowed-error path, which would have hidden a real provider outage as
"nothing to extract." Split into two paths;
TestPassPropagatesALLMFailure is the regression test.

task check is green (full Go suite + dashboard tests).


Imported from beads archie-core-1786637499114-354-e5b475b4 · GitHub #375 · type feature · priority P2 · created 2026-08-08 · closed 2026-09-01

Ship a curator that maintains durable memory across sessions -- extracting and consolidating what is worth keeping from conversation history into the attached memory engine. The second contract consumer, and the one that exercises the curator/memory-engine binding. ### Acceptance Criteria Registers and runs through the registry with no special-casing. Writes through the memory engine contract rather than any concrete store. Extraction runs off the hot path so a chat turn never waits on it. What it wrote and why is inspectable. Honours the trigger-accounting invariant so its own writes do not reschedule it. ### Close reason Complete, all four AC clauses. Design decided first in docs/prds/session-memory-curator.md, most notably: Observation.Identity is the session ID, not a user/cross-session identity -- migration- decisions.md#5's memory-scope mapping is still explicitly open and this issue has no business deciding it unilaterally. - Registers and runs through curator.Registry with no special-casing (TestRegistersAndRunsThroughTheRegistry). - Writes through the memory engine contract, never a concrete store: Registrar.MemoryEngines.Get(name).Write, same trust model every other curator capability uses. - Extraction runs off the hot path: the model call happens inside Pass, which the curator runtime already runs off a chat turn's own goroutine. - What it wrote and why is inspectable: one memory.extracted Action per session with a count, through the existing curator activity tracker. - Honours the trigger-accounting invariant: Manifest.OnInput = true wakes it via the existing WakeOnPrimaryInput wiring, which already excludes every curator-derived event kind -- no new code needed for that guarantee to hold here. Wired end to end: internal/app/archied/bootstrap.go:setupCurators, adapters for gateway.SessionStore (internal/infrastructure/ sessioncurator/adapter.go) and the shared ai-sdk runtime (curatorLLMRunner, main.go). Caught and fixed during implementation: a model-call failure and an unparseable model response were originally conflated into the same swallowed-error path, which would have hidden a real provider outage as "nothing to extract." Split into two paths; TestPassPropagatesALLMFailure is the regression test. task check is green (full Go suite + dashboard tests). --- _Imported from beads `archie-core-1786637499114-354-e5b475b4` · GitHub #375 · type feature · priority P2 · created 2026-08-08 · closed 2026-09-01_
sam added the mediumfeature labels 2026-10-27 13:34:35 +00:00
sam self-assigned this 2026-10-27 13:34:35 +00:00
sam closed this issue 2026-10-27 13:34:36 +00:00
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: sam/archie#14