MSP (Mandatory Session Protocol) is a development workflow that ensures you never lose context again. By following a simple three-phase pattern, MSP creates a persistent knowledge graph of your entire development journey.
MSP implements a memory-augmented development loop that treats coding like GPS navigation:
Define your destination. Load previous context. Set clear goals for this session.
Restore your position. Surface relevant decisions, blockers, and progress from your knowledge graph.
Capture your journey. Track decisions, update progress, document learnings for future sessions.
msp start → work & track → msp end
Every decision, every progress update, every blocker - captured and connected in your knowledge graph.
Export your entire project context to Claude, GPT, or Copilot with one command. No more repeated explanations.
MSP doesn't replace your tools - it orchestrates them. Mix and match to fit your workflow.
Watch a real development session with MSP tracking every decision, progress update, and context change.
73% → 85% in one session
Every choice tracked
Neo4j + Obsidian + Linear
Every MSP session follows a structured flow that preserves your context and tracks your progress. From initialization to completion, your development journey is captured in a persistent knowledge graph.
Never lose your place. Every session builds on the last with full context restoration.
Quantify your work with granular updates. Know exactly where you are.
Route your goals, Recall your context, Record your progress. Simple. Powerful.
MSP acts as the operating system for context engineering, orchestrating your favorite tools into a unified workflow. The framework is tool-agnostic—choose one tool from each column to implement the Route-Recall-Record protocol.
While other frameworks chase the myth of "one-shot" development—trying to perfect upfront context or extend single sessions indefinitely—MSP embraces how developers actually work: across days, weeks, and months of iterative sessions.
Command Interface: PowerShell, Bash, VS Code, or any IDE
Project Management
Persistent State
Documentation
Choose one tool from each column to implement the R³ Loop
ROUTE tells you where to go next session.RECALL restores your entire context instantly.RECORD captures every decision for future you.
Stop pretending development happens in one sitting. Start building systems that grow with you.
Built for how you actually work—across days, weeks, and months.
Every session builds on the last. Your AI never forgets.
All three R's working together. Not just tasks or docs—everything.
While others use flat files and linear text, MSP captures the web of relationships that represents how software actually evolves. Every decision, every connection, every outcome—preserved in a queryable graph.
Neo4j Graph Structure for Context Persistence
# Find decision patterns
MATCH (s:Session)-[:DECIDED]->(d:Decision)
WHERE d.why CONTAINS 'performance'
RETURN d.what, s.date
# Trace blockers
MATCH (t:Task)-[:BLOCKED_BY]->(issue)
-[:LED_TO]->(d:Decision)
RETURN issue, d.what
# Evolution tracking
MATCH (s1:Session)-[:PREVIOUS*]->(s2)
WHERE s1.goal = s2.goal
RETURN s1, s2, duration
Find patterns, trace decisions, understand evolution—all with simple queries.
Not just data storage—a living web of relationships that grows smarter over time.
Navigate your project's history. See how decisions evolved, when patterns emerged.