Session Notes Protocol
What Changed
Rejected the March 24 session-handoff and AgenticComm governance batch and replaced it with a smaller session-notes protocol.
Removed:
docs/session-handoff-and-messaging.md.cursor/rules/session-handoff.mdcprompts/patterns/session-handoff.mdprompts/queue/PR-0033_cursor_session-handoff-implementation.mdprompts/queue/PR-0034_codex_agents-md-update.mdprompts/queue/PR-0035_claude-code_claude-md-update.mdproject-log/handoffs/README.mdproject-log/handoffs/_index.yaml
Added:
docs/session-notes.mdproject-log/agent-workspace/session-notes/README.md- a concise Session Notes section in
AGENTS.md
Why
The rejected batch solved a real problem but overreached. It introduced a new real-time messaging system, required a git-tracked binary coordination file, blurred the existing human-routed prompt relay model, and added prompts that did not fit the repo's current validation and ownership rules.
The replacement keeps the useful part: a lightweight way to preserve session state when work is long, interrupted, or left dirty.
Type
Architectural and governance cleanup.
Follow-Up
- If session notes prove useful in practice, add a small reusable template later.
- Keep prompt relay as the canonical cross-agent routing mechanism unless the human explicitly chooses a broader coordination system.