| title | Governed Mutation Model | ||||||
|---|---|---|---|---|---|---|---|
| filetype | documentation | ||||||
| type | repository-overview | ||||||
| domain | governance | ||||||
| version | 0.1.0 | ||||||
| status | Active | ||||||
| created | 2026-03-12 | ||||||
| updated | 2026-03-16 | ||||||
| author |
|
||||||
| maintainer |
|
||||||
| license | Apache-2.0 | ||||||
| copyright |
|
||||||
| ai_assisted | partial | ||||||
| anchors |
|
The Governed Mutation Model defines a minimal object structure for artifacts undergoing governed state transitions.
It provides a deterministic envelope for representing:
- object identity
- object type
- lifecycle state
- artifact binding
The mutation model does not enforce governance rules and does not perform enforcement.
Instead, it defines the object identity layer used by governance systems that generate mutation proposals evaluated by enforcement engines such as CRI-CORE.
Governed systems typically separate object identity, mutation requests, and enforcement.
Conceptually:
artifact payload
↓
mutation object
↓
proposal object
↓
CRI-CORE enforcement
↓
commit authorization
Each layer has a distinct responsibility.
| Layer | Responsibility |
|---|---|
| Artifact | Domain payload (claim, dataset, decision, release, etc.) |
| Mutation Object | Identity and lifecycle envelope |
| Proposal Object | Mutation request |
| Enforcement Engine | Structural validation and authorization |
This repository defines the mutation object layer.
A governed mutation object minimally contains four fields:
object_id
object_type
state
artifact
Example:
{
"object_id": "claim-001",
"object_type": "claim",
"state": "proposed",
"artifact": {
"path": "claims/claim-001.yaml",
"sha256": "aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa"
}
}These fields provide deterministic identity and artifact binding without embedding governance semantics.
Mutation proposals represent requests to mutate governed objects.
Proposal objects include:
- proposing actor
- governance contract identity
- mutation description
- artifact references
Example conceptual flow:
mutation object
↓
proposal referencing object artifact
↓
CRI-CORE enforcement pipeline
↓
commit_allowed decision
The mutation object represents the object being mutated, while the proposal represents the mutation request.
CRI-CORE is a deterministic enforcement engine that evaluates mutation proposals and run artifacts.
CRI-CORE enforces:
- structural validity
- identity independence
- cryptographic integrity
- repository publication invariants
CRI-CORE does not interpret mutation object semantics.
This separation ensures:
- enforcement remains domain-agnostic
- governance policies remain external
- mutation objects remain portable across governance systems
Governed objects transition through lifecycle states.
Example conceptual progression:
draft → proposed → supported → superseded
Lifecycle rules are defined by governance policy or compiled governance contracts.
The mutation model tracks current state only.
Transition rules are enforced externally.
The canonical mutation object schema is located at:
schema/object.schema.json
The schema defines the deterministic structure for governed mutation objects.
The governed mutation model follows several core constraints.
Objects maintain stable identity across lifecycle transitions.
Objects reference payload artifacts using deterministic hashing.
Mutation objects are not interpreted by enforcement engines.
Lifecycle semantics and transition rules remain external.
This model can represent governed artifacts such as:
- research claims
- datasets
- governance decisions
- financial approvals
- software releases
The model provides a consistent identity envelope across governance domains.
Version 0.1.0 establishes the initial governed mutation object model and schema.
Future revisions may expand metadata capabilities while preserving the minimal core identity structure.
© 2026 Waveframe Labs — Independent Open Science Research