Expand description
Transcript data types for ceremony audit trails.
These types model the structure of ceremony execution records. A transcript
is a hash-chained sequence of ChainedEvent values that captures what
happened during a ceremony run, who participated, and what was produced.
The runtime-side functions (read_transcript, verify_transcript,
compute_fingerprint) live in rite-runtime — their signatures may still
evolve before the first stable release. The types here are the stable,
semver-committed portion of the transcript API.
Structs§
- Artifact
Verification - Result of verifying a single artifact file.
- Binary
Info - Information about the rite binary.
- Ceremony
Info - Information about the ceremony definition.
- Chained
Event - A hash-chained event in the JSONL transcript.
- Event
Outcome - Outcome of a step execution as recorded in the transcript.
- Image
Component - A single component in the release manifest (filesystem or binary).
- Image
Manifest - Release manifest, inlined from the USB image at ceremony runtime startup.
- Initrd
Component - A single component measured by the initrd hook.
- Initrd
Measurements - Measurements written by the initrd hook before squashfs was mounted.
- Instance
Info - Information about resolved ceremony inputs (parameters, materials).
- Parsed
Transcript - A fully parsed and verified transcript.
- Participant
Record - A participant assigned to a role for this ceremony execution.
- Step
Evidence - Evidence produced by a step execution.
Enums§
- Event
Data - Event data types for JSONL transcript entries.
- Transcript
Status - Transcript completion status.
- Verification
Result - Result of transcript verification.
Constants§
- GENESIS_
HASH - Genesis hash for the first event in the hash chain.
- TRANSCRIPT_
SCHEMA_ VERSION - Schema version for the JSONL transcript format.