Expand description
Original restore/source requirements and ephemeral application-owned safety evidence.
Structs§
- Restore
Fence Binding Record - Original integration-retained fence and authority revisions; never a release token.
- Restore
Fence Evidence - Passive exact fence evidence; every opaque field requires application qualification.
- Restore
Safety Observation - Canonical immutable ephemeral observation; no Serde, expiry or persisted authority flag.
- Restore
Safety Observation Input - Passive provider data; exact original context/source and current evidence are independent inputs.
- Restore
Safety Request - Ephemeral original-source/safety/challenge request; no dispatch or paid-call permit.
- Restore
Safety Request Input - Passive current parameters; the exact load/start boundary is derived from original wire bytes.
- Restore
Safety Requirement Record - Strict v1 immutable restore intent, original source and safety declaration.
- Restore
Safety Requirement Request - Passive original source and application safety declaration; no neutral default.
- Target
Restore Evidence - Passive actual lifecycle and integration-qualified source-specific restored acceptance.
Enums§
- Restore
Safety Evidence - Actual application safety lane; no generic default or serialized Proven admission.
- Restore
Safety Lane Record - Explicit original safety lane; neither declaration proves the application safe.
- Restore
Safety Observation Error - Typed owning-boundary current evidence admission denial.
- Restore
Safety Request Error - Typed original request denial; changes no source, fence, spending or journal.
- Restore
Safety Requirement Error - Typed original source/safety declaration denial; retains all existing obligations.
Constants§
- MAX_
RESTORE_ SAFETY_ REMOTE_ OBSERVATIONS - Maximum descriptive remote observations per invocation; no spending allowance.
- MAX_
RESTORE_ SAFETY_ REQUIREMENT_ BYTES - Maximum raw input and canonical output bytes for the retained safety requirement.