Outcomes and requirements
Capture the behaviors, constraints and obligations that should survive implementation churn.
Intent memory
Keep product intent durable while implementation accelerates.
Xohre stores outcomes, requirements, constraints, decisions and architecture as connected records with stable identity. The goal is durable intent and traceability, while implementation details can evolve through controlled reconciliation.
- Durable intent
- Decision rationale
- Traceable relationships
CANONICAL RECORD GRAPH
REQRequirementv8 · accepted
DECDecisionaccepted
CTXContext Packsealed
EVDEvidencefresh
RLSReleaseready
Preserve meaning, not document volume
Give humans and agents an addressable model of what matters.
The workspace separates durable product meaning from implementation detail, then keeps both connected through lifecycle, relationships and change.
Decisions and rationale
Preserve choices, alternatives, consequences and supersession so later agents can understand why the system took its current shape.
Architecture and interfaces
Represent design boundaries as addressable records that can be affected, refined or superseded as code evolves.
Typed relationships
Connect intent, design, work and verification with explicit semantic links rather than relying on proximity in documents.
Lifecycle and baselines
Separate draft thinking from accepted intent and preserve exact baselines for tasks, reviews and releases.
Reconciliation targets
Mark which records may need attention when observed implementation reality moves beyond the currently accepted model.
Intent becomes agent context
Give agents the current truth without asking them to rediscover the entire product.
Use governed records to assemble bounded context, then capture the agent's material discoveries and implementation choices as a semantic delta.