Expand description
Plan bundle integrity documents (spec 042, 3.3). Signatures and registrations describe integrity, never execution authority.
Structs§
- Bundle
Definition - A bundle’s definition (3.3.1, 3.3.8): a definition document, or a spec
034 template, a
rustev.definition/2document declaringparametersorvariants. A concrete definition is checked by its own parser; a template is bounded here and checked by instantiation (034 3.9 stage 1), whose refusal iscompile_refused, so anything else is refused here. - Bundle
Variant - The variant a bundle is instantiated for (3.3.8):
{"named": <name>}, the name matching[a-z][a-z0-9_]{0,63}(034 3.1.3). The variantnoneis spelled by omitting the member. - Compile
Report - Successful output of the existing surface compile command. Output paths are report observations; they never become an endpoint in a binding.
- Plan
Bundle - Plan
Bundle Signature - Plan
Registration - Registration
Id - Sigstore
Bundle - A Sigstore bundle is a third-party document: its bytes are bounded to 1 MiB, must parse as a JSON object, and are kept exactly as received so the verifier sees the signed bytes unchanged. This type makes no verification claim.
Enums§
- Compile
Command - Compile
Status - Plan
Bundle Schema - Plan
Bundle Signature Schema - Plan
Registration Schema - Signature
Scheme - Signer
- Signing
Mode
Type Aliases§
- Ed25519
Signature - Ed25519 signature octets, exactly 64. No encoding ambiguity and no key material is carried in a plan bundle.