Expand description
Live re-execution evidence, rustev.live-reexecution/1 (spec 026).
A live re-execution is a new decision: a new decision id, a newly
identified snapshot, a fresh evaluation time, fresh admission and budgets
and new runtime observations. Its run record (rustev.run/1) remains the
evidence of execution. This document is a separate, bounded companion
that binds what the run record cannot: the link to a historical case (a
digest plus identities, never historical content), the host’s
authorization answer for every proposed external attempt, every effect
with its charge and remote state, the evidence delivery observation, the
capture and retention posture, and an optional comparison.
Rustev defines no authorization token. What the runtime presents to the
host before an attempt is an AuthorizationRequest; what this document
keeps of the answer is the host’s opaque, non-secret
AuthorizationReference or the refusal. Neither is permission, neither
authorizes any downstream action, and this document is not proof that
the host’s authorization decision was correct (spec 026, 3.3 and 3.6).
Structs§
- Admission
- The new decision’s admission (spec 003, 3.4): a document exists only for an admitted decision.
- Authorization
Reference - The host’s opaque, non-secret reference to its own authorization decision, kept for evidence. Rustev compares and records it, and never interprets it: it is not a token, a credential or a permission, and it authorizes nothing.
- Authorization
Request - What the runtime presents to the host immediately before one external attempt (spec 026, 3.3): the exact decision, scope, backend, artifact, operation, canonical request identity, maximum cost exposure, remaining time and role. It carries opaque handles and identities only, never a credential.
- Comparison
Definition - What is compared: an explicitly named proposal payload or outcome category, chosen by a versioned task adapter. Full judgment bytes are never the agreement metric.
- Cost
Comparison - Observed, estimated and unknown cost, kept apart, of each side.
- Exposure
- The worst-case cost of one proposed attempt: the backend’s disclosure and the units reserved for it before it was presented.
- Historical
Link - A historical case, linked by digest and identities only: never embedded historical content (spec 026, 3.7).
- Identity
Changes - Identity changes between the historical case and the live run.
- Item
Observation - One historical item’s availability, as observed at comparison.
- Live
Comparison - The comparison of a finished live run with a verified historical case.
- Live
Effect - One proposed external attempt of the new decision: what was presented, the host’s answer, and the effect. Every attempted effect is attributable to the new decision by its attempt id (spec 026, 3.6).
- Live
Reexecution rustev.live-reexecution/1: one live re-execution, bounded byREPLAY_V1. Holds no credential and no secret authorization material.- Observation
Changes - New backend, policy, calibration and runtime observations.
- Other
Changes - Cancellation, remote-state, retention and delivery differences.
- Reference
Error - Why a string is not an authorization reference.
- Retention
Posture - RunLink
- The new run record, linked by digest; it stays the evidence of execution.
- Runtime
Observations - Counts of runtime observations of one side.
Enums§
- Attempt
Role - Which kind of external attempt is proposed.
- Authorization
Outcome - What the host answered for one proposed attempt, as kept for evidence.
- Authorization
Refusal - Why an attempt was not authorized. Each prevents dispatch and is
recorded as
authorization_refused(spec 026, 3.3). - Capture
Posture - The new run’s capture, chosen independently of the historical case and off by default (spec 026, 3.7).
- Change
- Whether a compared member changed. Unknown is never unchanged.
- Comparison
Outcome - The result of comparing the live proposal with the historical one.
- Comparison
Section - The comparison member of a live document.
- Delivery
Observation - What became of the new run record’s delivery (spec 003, 3.9.4).
- Dispatch
- Whether a proposed attempt was sent, and what it observably did.
- Historical
- The historical case, or its explicit absence.
- Historical
Retention - What is known of the historical case’s retention. Live re-execution never extends it and never restores an item (spec 026, 3.7).
- Live
DocError - Why a live document is not well formed.
- Result
Change - How the compared result changed.
Constants§
- AUTHORIZATION_
REQUEST_ TAG - The tag of an authorization request’s digest. The request is presented in process and is not a wire document; its digest binds an answer to exactly one proposed attempt.
- MAX_
EFFECTS - The most effects one live document lists: one per proposed attempt, so at most the plan’s attempt bound, and never more than this.
- MAX_
HISTORICAL_ ITEMS - The most historical item observations (a bundle’s items plus itself).
- MAX_
NOTES - The most named fields, exclusions or limitations of one comparison.
- MAX_
REFERENCE_ BYTES - The most bytes of an authorization decision reference.
- MAX_
TEXT_ BYTES - The most bytes of one free-text member (a detail, a receipt, a note).
Functions§
- attempt_
prefix - The prefix every attempt id of
decision_idstarts with (spec 003, 3.9.2: the decision id is its first, escaped, component).