Engine · Solution Partial
Definition Manager — Systemic Intelligence Engine.
Keep system definitions versioned, accessible and governed through change.
REST APIs, retained snapshots and transition controls provide the current implementation scope. Tenant/object authorization, current graded validation and revision-bound decisions are being completed; committed change notifications and MCP access are planned.
Values
Value delivered by the product
- Value Partial
Make transitions inspectable.
Check lifecycle advancement against defined transitions, with authentication, policy and current grammar alignment completing the governance boundary.
Supported by Affordances(1)
Supported by Capabilities(3)
Supported by Features(2)
Realized through Use cases(6)
- Assess dependent definitions after foundation invalidation
- Author and approve a shared definition
- Read and revise definitions through the API
- Hold definitions as the authoritative, revision-bound source
- Enforce definition lifecycle boundaries
- Make review and activation boundaries explicit
- Value Partial
Access snapshots programmatically.
Reuse structured snapshots across tools instead of manually exchanging documents, within each route's validated isolation, pagination and performance scope.
Supported by Capabilities(1)
Supported by Features(1)
Realized through Use cases(2)
- Value Implemented
Reuse retained lifecycle evidence.
Start review from retained version history. Linking actors, rationale and retention policy completes the evidence needed for a stated audit scope.
Supported by Features(1)
Realized through Use cases(2)
- Value Partial
React to committed changes.
Use planned change notifications to replace repeated polling, with replay and recovery for missed events.
Supported by Capabilities(1)
Supported by Features(1)
Realized through Use cases(2)
Features
Implemented and planned features
- Feature Implemented
GSM Definitions management RESTful API
Access Definitions and Ascriptions through the REST implementation. Completion covers current graded-create semantics, tenant/object policy and coherent queries.
Addresses Pain points(2)
Supports Values(1)
Serves Use cases(1)
Used by Actor types(2)
- Feature Implemented
GSM Definitions lifecycle controls
Validate Ascription state transitions. Current graded checks, revision-bound decisions and differentiated cascades include inspecting dependent eligibility after foundation invalidation, beyond state legality alone.
Addresses Pain points(1)
Supports Values(1)
Serves Use cases(1)
Used by Actor types(2)
- Feature Implemented
GSM Definitions retention
Retain versioned snapshots and stable identities. Retrieve historical decision evidence and agree purpose, duration, access and disposal constraints; decision attribution, recovery and verified policy enforcement remain completion boundaries.
Addresses Pain points(3)
Supports Values(7)
Serves Use cases(2)
Used by Actor types(3)
- Feature Planned
GSM Definitions lifecycle events mediation
Notify authorized consumers of committed changes, with ordering, replay, deduplication and crash recovery in a dedicated lifecycle event stream.
Addresses Pain points(1)
Serves Use cases(1)
Used by Actor types(2)
- Feature Planned
MCP
Give AI tools MCP access to policy-filtered, pinned definitions and bounded operations, alongside direct API access and independently of sourcing.
Addresses Pain points(1)
Supports Values(2)
Serves Use cases(1)
Used by Actor types(2)
Roadmap
Where Definition Manager is going.
Recorded version: v1.0. Historical release labels do not establish the current feature scope above.
- v1.0 Implemented Recorded release: MVP/GA — Definitions management API, lifecycle enforcement, retention
- v1.1 Planned Planned milestone: GSM Definitions lifecycle events mediation
- v1.2 Planned Planned milestone: MCP
Implemented and Planned qualify the features in each milestone. Recorded releases and planned milestones preserve history, not delivery dates or hosted availability. See the Milestones & Versions register.
Qualities
What Definition Manager claims about how it behaves.
- Tenant-scoped storage Partial Definitions never leave their tenant schema
Retained snapshots and queries resolve within a tenant boundary. Tenant/object authorization across the full API surface is being completed.
- Revision-bound decisions Partial A decision names the revision it was made on
Transition controls bind a decision to the revision it reviewed, so a stale write is refused rather than silently applied.
Usage
Use cases involving Definition Manager
- Use case Implemented
Retrieve the basis of a historical decision
Retrieve the decided revision, recorded identity, supporting evidence and conditions relevant to a historical decision, retaining attribution gaps.
Supported by Features(1)
Addresses Pain points(2)
Realizes Values(5)
Performed by Actor types(2)
- Use case Implemented
Assess dependent definitions after foundation invalidation
Inspect dependent definition eligibility after a referenced foundation is invalidated and determine which continued uses require renewed review.
Supported by Features(1)
Addresses Pain points(1)
Realizes Values(1)
Performed by Actor types(2)
- Use case Implemented
Agree evidence-preservation requirements
Agree retention purpose, duration, access and disposal constraints for decision evidence, distinguishing agreed policy from demonstrated enforcement.
Supported by Features(1)
Addresses Pain points(1)
Realizes Values(4)
Performed by Actor types(3)
- Use case Planned
React to a committed definition change
Refresh a downstream view from committed changes without repeated full polling.
Supported by Features(1)
Addresses Pain points(1)
Performed by Actor types(2)
- Use case Implemented
Read and revise definitions through the API
Create, query and revise typed definitions through the REST contract, inspecting validation, revision and access responses without treating a successful draft write as approval.
Supported by Features(1)
Addresses Pain points(2)
Realizes Values(1)
Performed by Actor types(2)