Constitutional Dynamics Engine — provable state evolution
across the ICore ecosystem
The formal layer that models, verifies, and visualises provable state evolution across the ICore ecosystem. Every constitutional change — a package publish, agent birth, delegation update, or knowledge revision — is a verified transition that preserves all CITS invariants.
Dynamics answers the constitutional question: "Is this change valid?" — not as a static audit, but as a live, continuous proof that every state transition maintains or improves conformance.
6 constitutional states with 5 verified transitions. Every package evolves through a provable lifecycle.
4 constitutional states. Every agent lifecycle is a verified trajectory from birth to retirement.
3 constitutional states. Trust relationships are formal state machines with provable transitions.
The set of all reachable constitutional states from a given initial state — the map of constitutional possibility. Dynamics tracks every verified trajectory and projects future constitutional evolution.
Signed, verified chains of transitions from genesis to present. Each trajectory is tamper-evident via chain root hashing.
Every transition is checked against CITS invariants. Critical failures block transitions. Major failures warn. Minor failures inform.
Every state and transition is content-addressed. Same logical content = same ID across time and space. No silent state changes.
Built on CBOR-LD for compact, content-addressed storage and JSON-LD for human/audit display. Linked data proofs ensure deterministic verification across all runtimes.