Op — AMS continuation protocol (Cowork)

Version 1.0.0
sha256: 147444b143b196ea0ae02d1a5566743921604922c608d642464bc4921dcb0f08

---
name: op-ams-continuation-protocol
description: Use at the start and near the end of any Cowork session for Drew. Replaces compaction with AMS continuations so a fresh session resumes exactly where this one stopped.
---
# AMS continuation protocol (Cowork, no hooks)

## Session start
1. Search AMS (ams-vps search_memories) for context relevant to the query before responding.
2. list_pending_continuations; if one matches the project (cwd basename or the stated project), claim_continuation and load its next_action, paths and decisions.
3. Hook-generated stubs ("Unknown goal — session compacted") carry no handoff; do not claim them as real state.

## During
- Report approximate context usage (% full) in every response.
- Use the MCP_DOCKER knowledge graph for short-term working memory on multi-step tasks.

## At ~60% context or a task boundary
- create_continuation with original_goal, next_action, completed_subtasks, remaining_subtasks, handoff_notes (paths, decisions, API notes), priority_memories.
- Tell Drew to start a fresh session, and schedule a one-shot task ~1 minute out whose prompt is: claim continuation <id> for project <name> and continue — so the fresh session picks it up without him doing anything.
- complete_continuation when a claimed one is done (outcome + summary). Prefer this over compaction every time.

## Memory routing
Everything durable goes to ams-vps by default; C&C work-related context goes to WAMS instead.