| title | Claim Lifecycle Demo — End-to-End Governed Claim Example | ||||||
|---|---|---|---|---|---|---|---|
| filetype | documentation | ||||||
| type | guidance | ||||||
| domain | case-study | ||||||
| version | 0.3.3 | ||||||
| doi | TBD-0.3.3 | ||||||
| status | Active | ||||||
| created | 2026-02-05 | ||||||
| updated | 2026-03-03 | ||||||
| author |
|
||||||
| maintainer |
|
||||||
| license | Apache-2.0 | ||||||
| copyright |
|
||||||
| ai_assisted | partial | ||||||
| dependencies |
|
||||||
| anchors |
|
This repository is a minimal, end-to-end demonstration of a governed scientific claim lifecycle backed by a real enforcement engine.
It demonstrates two distinct but related boundaries:
- A governed claim lifecycle (evidence → proposal → enforcement → state mutation).
- A hardened kernel enforcement showcase (structural, authority, and integrity gating).
The lifecycle demo shows how a claim moves through:
proposed → supported → contradicted → superseded
Each transition is:
- triggered by submitted evidence
- validated against explicit transition rules
- materialized as a CRI-CORE run artifact
- passed through a deterministic enforcement decision boundary
- and recorded as an immutable event
This repository demonstrates governance boundaries, not infrastructure scale.
Shows:
- Evidence-driven transition proposals
- Rule validation (transition graph constraints)
- CRI-CORE enforcement integration
- Authority boundary enforcement (self-approval denial)
- Append-only transition logging
- Commit gating via
commit_allowed
This runner models a governed scientific workflow.
Demonstrates enforcement behavior in isolation, without lifecycle semantics.
Scenarios:
- Authority failure → fix
- Integrity tamper detection → fix
- Structural contract failure (missing required artifact)
This harness proves:
- Structural admissibility enforcement
- Role separation enforcement
- SHA256 artifact integrity verification
- Stage cascade logic
- Centralized commit gating
It isolates the enforcement engine from lifecycle logic.
The primary object is a claim.
A claim represents the smallest testable scientific statement that downstream conclusions depend on.
Example:
A specific model version achieves at least a declared performance threshold under a defined dataset and evaluation configuration.
This demo focuses on governance mechanics rather than executing experiments.
A claim may change state only when a new evidence submission:
- references the claim by ID
- declares an intended state transition
- satisfies transition rules
- is materialized as a CRI-CORE run artifact
- passes enforcement validation
Claim state is never edited directly.
This repository demonstrates:
- Rule validation (transition graph constraints)
- Run structure contract enforcement
- Structural version gating
- Identity separation enforcement
- SHA256 integrity verification
- Integrity finalization cascade
- Explicit allow/deny decisions
- Centralized commit gating
- Append-only transition logging
This demo depends on the public CRI-CORE enforcement kernel.
Install it from PyPI:
pip install cricore>=0.6.0
No local clone of the CRI-CORE repository is required.
From the root of 'claim-lifecycle-demo'
python demo_runner/run_demo.pypython demo_runner/run_kernel_showcase.pyAuthority only:
python demo_runner\run_kernel_showcase.py authorityIntegrity only:
python demo_runner\run_kernel_showcase.py integrityStructure only:
python demo_runner\run_kernel_showcase.py structureMost research workflows track files and artifacts.
This demo treats claims themselves as governed objects whose status changes only through validated evidence and deterministic enforcement.
That enables:
- Deterministic lifecycle control
- Explicit role accountability
- Tamper-detectable execution artifacts
- Clear governance boundaries between proposal and mutation
This repository demonstrates a governed lifecycle boundary and a hardened kernel enforcement boundary.
CRI-CORE remains a separate enforcement engine.
This repository shows what governed claim mutation looks like in practice.