Context
For the Shared Deployment MVP (#10721), the summarization coordinator primitive (claimSummarizationJob) was shipped in #10693. However, the automated trigger that invokes this coordinator when a client disconnects is missing.
The Problem
Without a disconnect trigger, session summarization relies on manual invocation or out-of-band cron jobs. To provide a seamless team-shared deployment, the Memory Core must automatically queue and process session summaries when an agent disconnects (indicating session completion or suspension).
The Architectural Reality
This requires bridging MCP client-disconnect events and the claimSummarizationJob coordinator. It necessitates introducing a "session completion" marker concept (a data shape, a writer, and a detector) to safely transition sessions from active to summarizable.
The Fix
Wire the MCP disconnect event to a trigger mechanism. Define the "session completion" marker data shape. Implement the detector that invokes the claimSummarizationJob coordinator upon detecting a completion/disconnect marker. The coordinator handles concurrency; this task provides the missing trigger.
Contract Ledger Matrix
| Target Surface |
Source of Authority |
Proposed Behavior |
Fallback |
Docs |
Evidence |
| Disconnect Trigger |
MCP Server Lifecycle |
Write "session completion" marker on client disconnect and queue summarization job. |
If write fails, rely on standard periodic sweep (if implemented) or manual purge. |
Update learn/agentos/SharedDeployment.md |
L3 (Integration test verifying summarization queued on disconnect event) |
Acceptance Criteria
Out of Scope
- Modifying the underlying TTL-lease and atomic SQLite transactions of the coordinator (already shipped).
Avoided Traps
- Rejected: Immediate synchronous summarization on disconnect. Summarization can be slow. The trigger must queue the job for the asynchronous coordinator rather than blocking the disconnect lifecycle.
Related
Origin Session ID: 79042442-bebc-431d-8968-8a2e7d7a1151
Retrieval Hint: query_raw_memories(query="Disconnect-triggered summarization wiring claimSummarizationJob marker")
Context
For the Shared Deployment MVP (#10721), the summarization coordinator primitive (
claimSummarizationJob) was shipped in #10693. However, the automated trigger that invokes this coordinator when a client disconnects is missing.The Problem
Without a disconnect trigger, session summarization relies on manual invocation or out-of-band cron jobs. To provide a seamless team-shared deployment, the Memory Core must automatically queue and process session summaries when an agent disconnects (indicating session completion or suspension).
The Architectural Reality
This requires bridging MCP client-disconnect events and the
claimSummarizationJobcoordinator. It necessitates introducing a "session completion" marker concept (a data shape, a writer, and a detector) to safely transition sessions from active to summarizable.The Fix
Wire the MCP disconnect event to a trigger mechanism. Define the "session completion" marker data shape. Implement the detector that invokes the
claimSummarizationJobcoordinator upon detecting a completion/disconnect marker. The coordinator handles concurrency; this task provides the missing trigger.Contract Ledger Matrix
learn/agentos/SharedDeployment.mdAcceptance Criteria
claimSummarizationJobupon marker write.SummarizationJobsprimitive (#10693) without re-architecting it.Out of Scope
Avoided Traps
Related
Origin Session ID: 79042442-bebc-431d-8968-8a2e7d7a1151 Retrieval Hint:
query_raw_memories(query="Disconnect-triggered summarization wiring claimSummarizationJob marker")