Read this first or risk repeating work and missing critical decisions. Your execution memory that persists across sessions. Contains: vision (goal), sketch (static blueprint), milestones (phases), tasks (deliverables), notes (lessons), and references (key files). Other agents update this too - check regularly. Returns 'version' for change detection, 'now' for active status, 'diagnostics' (debt score + top issues), and may include 'warnings'/'hints' for suggested actions.

Apply multiple updates in ONE call (reduces friction; keeps context current). Input: ops=[{op: ...}, ...] and optional dry_run=true. Supported ops:

• context.set: vision?, sketch?

• presence.set: agent_id, status

• milestone.update: milestone_id, name?, description?, status?, outcomes?

• milestone.complete: milestone_id, outcomes

• task.update: task_id, status?, name?, goal?, assignee?, milestone_id?, steps?

• task.step: task_id, step_id, step_status

• note.add: content, ttl? (10/30/100 recommended)

• note.update: note_id, content?, ttl?

• note.remove: note_id

• reference.add: url, note, ttl? (10/30/100 recommended)

• reference.update: reference_id, url?, note?, ttl?

• reference.remove: reference_id Example ops: [{op:'presence.set',agent_id:'peer-a',status:'Implementing X'},{op:'task.step',task_id:'T001',step_id:'S2',step_status:'done'},{op:'note.add',content:'Found edge case in parser',ttl:50}]

Set or update the project vision - what we're building. This is a short, fixed statement that captures the project goal. Example: 'Build secure SaaS platform for 10K users'

Update the execution blueprint (markdown). Sketch is static: architecture, strategy, constraints, major decisions. Do NOT put TODOs, daily progress, task lists, or milestone status here (use tasks/milestones instead). Recommended sections: ## Architecture, ## Strategy, ## Risks, ## Decisions. Update on: architecture/strategy shifts or major risk changes.

Get all agents' current status - what they're doing/thinking. Essential for multi-agent coordination. Each agent has: ID, status (natural language), last update time.

Tell other agents what you're doing - they can't see your work otherwise. 1-2 sentences describing your current focus, intent, or blockers. Example: 'Debugging JWT edge case, found timezone issue' or 'Blocked on schema confirmation'.

Clear your presence status (remove stale/finished status). Use this when you’re done or after a handoff so old statuses don’t linger and mislead.

Start a new coarse project phase (timeline). Use for 2–6 big stages (e.g., 'Phase 1: Core Implementation'). Exactly one milestone should be active at a time.

Modify milestone details or advance status (pending→active→done). Use to mark phase transitions or adjust phase scope/outcomes.

Close a milestone and record what was accomplished. Outcomes become permanent project history visible to future sessions.

Delete a cancelled or mistaken milestone. Completed milestones should be kept as project history.

Find tasks by status (planned/active/done) or assignee. Use to see what work exists and check progress across sessions.

Create a deliverable work item with 3–7 steps. Use for concrete outcomes that span handoffs or need tracking. Prefer linking it to a milestone via milestone_id.

Update task execution state - status/steps/details (and optional milestone link). Keeps progress accurate for handoffs and resumption.

Remove a cancelled or mistaken task. Completed tasks auto-archive after 7 days - no need to delete them.

Preserve important knowledge for future sessions - lessons, warnings, decisions. TTL decays and auto-archives over time. Recommended tiers: 10=short-term, 30=normal, 100=long-term. Example: 'API rate limit is 100/min - batch requests to avoid throttling'

Refresh a note's ttl to prevent decay, or update its content. Use when a note is still valuable but its ttl is getting low.

Delete an obsolete note immediately. Prefer letting low-value notes decay naturally via ttl lifecycle.

Bookmark important file paths or URLs for quick navigation. TTL decays over time. Recommended tiers: 10=short-term, 30=normal, 100=long-term. Use for: key source files, API docs, configs. Example: 'src/core/auth.py - OAuth implementation'

Refresh a reference's ttl to prevent decay, or update its details. Use when a reference is still valuable but its ttl is getting low.

Delete an obsolete reference immediately. Prefer letting outdated references decay naturally via ttl lifecycle.