Module attempt 

Execution-attempt lifecycle contracts.

An attempt represents an isolated execution lifecycle, with contracts documented in website/docs/design/admission.mdx#from-capability-validation-to-admission. lifecycle contains the underlying state machine, owner supplies drive capabilities, queue buffers uncollected reports, and execution tracks occurrence claims within an invocation round. Query service completion interfaces remain pub(crate), exposing only owner, handle, binding, and completion types to external adapters.

Structs

AttemptAdmissionBinding

Opaque, identity-bound admission attachment for one execution attempt.

AttemptAdmissionRejection

Opaque authority for rejecting an admission request before it receives a grant.

AttemptBackendCounters

Process-lifetime counters for one backend’s attempts. Each is monotonic and exact. attempts_begun is incremented under the observation permit that begin_attempt takes, and every begun attempt publishes one report, so attempts_begun - reports_ready is the number of attempts whose report is still pending.

AttemptBackendCountersSnapshot

Monotonic attempt and abandoned-report delivery counters for one backend. A report becomes ready after cleanup and sealing, independently of whether a caller retains a completion receiver.

AttemptBegin

The attempt owner and its completion factory, created together at begin.

AttemptCancellation

The attempt’s cooperative cancellation signal and optional deadline.

AttemptCompletion

Independent receiver for the bounded terminal attempt report.

AttemptCompletionFactory

Adapter-internal minting capability for one attempt’s completion receivers.

AttemptHandle

Cloneable record-only capability shared by every native fragment of one invocation. It cannot terminalize the attempt.

AttemptOwner

Terminalization authority for one execution attempt.

BeginAttemptRequest

Caller inputs to begin one execution attempt before planning.