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.
Evidence and changes
- Owner decision
- Original key retained
- Test result
- Partner contract passed
- Release check
- Validation report missing
Current reality
Source backedRetries keep the original delivery key.
- Obligation
- Attach the validation report before release.
- Constraint
- Partner payloads exclude internal commercial fields.
- Conflict
- A newer low-authority note does not replace the owner decision.
Same project, task-specific views
Developer
Decision, tests and open work
Partner
Approved behavior only
AI agent
Task context and sources
Product proof
A project changes. SPM keeps the operative state coherent.
When retry behavior changes, SPM keeps the old decision historical, the owner-approved replacement current and the validation report open.
- Know what is current
- Resolve decisions, constraints, obligations and conflicts.
- Give each participant the right context
- Deliver only what matters for the task and audience.
- Verify why it is true
- Keep authority, evidence and change history attached.
How it works
Maintain the project once. Compose the view for the work at hand.
- 01
Connect a project
Link the sources and working agents that are allowed to contribute project evidence.
- 02
Establish what is current
SPM evaluates changes, authority, lifecycle and evidence without erasing disagreement or uncertainty.
- 03
Deliver the relevant view
Each task receives authorized context and a path back to the evidence when more detail is needed.
One project, distinct views
Access follows the participant and the task.
Each view comes from the same project evidence, then applies the relevant authority, lifecycle and audience boundary.
- Developer
- Current decisions, implementation constraints, pending work and test evidence.
- Partner
- Approved integration behavior, examples and obligations within 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.
Trust boundary
- Tenant and project access boundaries
- Source-backed state and change history
- Authority and lifecycle kept with each claim
- Audience-specific access with expiry and revocation
Works across participants
Keep the project available when the tool or team changes.
Agent continuity is one use of the wider project-context model. Setup and continuation details remain available on the dedicated agents page.
Explore agent integrationsStart with one project