Governed project context
Keep project reality current. Give everyone the right context.
SPM keeps decisions, constraints, obligations and evidence current and verifiable, then gives each person or AI only what they need to act correctly.
The project persists. People, agents and tools move through it without becoming the owner of its truth.
Integration release
Current Reality, with its history intact
A temporal view of one integration decision. The owner's original stable-key decision remains current, a lower-authority conflicting note is retained as working context, and a release obligation stays open. Developer, AI agent and release-owner handoffs receive distinct governed views from that same project.
- Original12 May
Delivery keys remain stable across retries.
Owner decision · authority retained
- Working18 Jun
A later note proposes rotating the key.
Lower authority · tension recorded
- CurrentNow
Retries keep the original delivery key.
Source backed · owner authority
- HistoryOpen
Validation report is still required before release.
Obligation · evidence pending
Anchor · authority-backed fact
Stratum · temporal layer
Trajectory · governed handoff
- 01Know what is current
- Resolve decisions, constraints, obligations and conflicts.
- 02Give each participant the right context
- Deliver only what matters for the task and audience.
- 03Verify why it is true
- Keep authority, evidence and change history attached.
A decision through time
A project changes. SPM keeps the operative state coherent.
Current Reality is not a rewritten summary. It is the readable surface of durable decisions, working change, open obligations and retained history.
- 01
The decision is anchored
An owner-backed integration decision enters the project with its source, authority and date.
Original · authority retained
- 02
The work changes around it
Tests, notes and agent actions add working context without silently replacing the decision.
Working · tension visible
- 03
The next participant starts from reality
A governed view carries the current decision, open obligation and evidence path into the next task.
Current · receipt attached
One project, distinct views
Access follows the participant and the task.
The evidence remains one governed project. Each participant receives a bounded view with its authority and source path intact.
Review security and access controls- Developer
- Current decisions, implementation constraints, pending work and test evidence.
- Partner
- Approved integration behavior and obligations inside the shared boundary.
- AI agent
- Task-specific project context, active constraints and source references.
- Owner or auditor
- Authority, lifecycle, conflicts, delivery history and verification evidence.
Agent continuity
The participant changes. The project does not reset.
Agent continuity is one use of the wider project-context model. A handoff carries authorized state and a verifiable workspace reference, not a flattened transcript.
- Codexhandoff 1
- Claudehandoff 2
- Cursorhandoff 3
- MCP clientshandoff 4
- API and CLIhandoff 5
Every continuation can be aligned, verified and revoked within its project boundary.
Explore agent integrationsStart with one project