Expand description
The deterministic execution spine: load manifest → validate authority hashes → execute stages → seal → emit.
The runtime is intentionally thin. Its only jobs are (1) to validate the frozen manifest, (2) to gate each
stage — refusing any stage that declares no authority, or whose declared authority is not in the manifest’s
frozen allow-list — and (3) to seal the ordered stage receipts into a tamper-evident RuntimeReceiptV1.
It never mutates authority, never performs I/O, and admits no claim without an authority anchor.
Because RuntimeStage is generic over I/O, a heterogeneous multi-stage pipeline is built by the caller
(each stage’s O feeding the next stage’s I); the runtime’s contribution is the per-stage gate +
record, and the final seal. The chemical crate is one such caller; this crate carries no chemical logic.
Structs§
- Runtime
- Accumulates the gated, validated stage summaries of one run, then seals them.