Architecture, schemas, capsule contracts, and the reproducibility spec. Documentation lives next to the code and is versioned with it — each release ships a documentation snapshot whose hash matches the binary it describes.
SHIVA OS is built around twelve cooperating engines. They divide into six pairs by responsibility. Each pair is summarised below; per-engine reference documentation is being lifted from the source tree as each capsule earns its release.
Identity binds every actor — clinician, attestor, capsule run — to a DID with explicit role scopes and attestor eligibility. Nothing executes anonymously. Ontology binds every claim to a versioned schema and vocabulary; no executable claim can exist without a binding, so vocabulary drift never silently changes meaning between humans and machines.
Ingestion takes raw artifacts and emits typed candidate claims; the original source remains immutable. Provenance maintains an event-sourced lineage DAG over those claims. Every transformation is appended, never overwritten. The history of any claim is reconstructable back to the artifact it came from.
The Evidence Vault is content-addressed and encrypted storage for the raw artifacts behind claims, with optional anchoring and tombstone-with-proof for deletion. Graph Core is the semantic graph over the claims themselves — including conflict edges, so contradictions coexist with explicit status rather than being silently resolved.
Attestation issues signed witness events from eligible attestors. High-stakes claims require multi-party attestation; revocation is first-class. Policy evaluates rules and jurisdiction overlays against attested claims and emits a verdict; no action executes downstream without one.
Execution converts authorized knowledge into action, with every action linking back to the claims that authorized it. Governance handles proposals, voting, and disputes over the rules themselves. Constitutional invariants protect the system from changes that would break the chain of attestability.
Reflection lets SHIVA inspect and repair its own state, with recursion bounded by policy. Checkpoint produces Merkleized digests of the whole system at scheduled intervals; anchored roots make the entire state replayable across years from a single hash.
Contracts a capsule has to fulfil to ship under the SHIVA banner.
One HTML file. No build step. Optional companion ProofPack.
Loads, runs, and finishes with no network access required.
Every input and output schema-bound, with a public JSON Schema.
Same inputs at the same version → bit-identical outputs. Recorded by ProofPack.
Every formula or rule used is visible in the source. No external black boxes.
Each release has a SHA-256 in the manifest. RoCrate Verifier+ can confirm it.
A ProofPack is the unit of replay — a small, self-describing JSON document that bundles inputs, version, derived values, and a hash.
The schemas, contracts, and architecture chapters are stable. The longer reference text is being authored against each engine's source tree so the doc snapshot matches the binary.