Expand description
Trusted-host lifecycle ownership for runtime resources.
A ResourceScope closes admission and accounts for accepted work under
one synchronous gate. Completion is retained: dropping an HTTP request or
another waiter cannot cancel a scope finalizer once it has started.
Structs§
- Admission
Closed - Admission was closed before an operation could be registered.
- Close
Report - The terminal result retained by a resource scope.
- Operation
Lease - An admitted operation. It is completed exactly once when released.
- Resource
Scope - One trusted-host scope. Clones are access capabilities, never ownership transfers; resource finalization remains retained by the shared scope.
- Resource
Snapshot - Inspectable state for one trusted-host resource.
- Runtime
Handle - A cloneable command and observation capability for a supervisor.
- Runtime
Supervisor - Trusted host owner for all runtime resource scopes.
- Weak
Resource Scope - A non-owning observation capability for finalizers and controller facades. It prevents a resource’s retained finalizer from strongly owning its scope.
Enums§
- Lifecycle
Dependency Failure - A dependency graph cannot establish an ordered finalization for a resource.
- Lifecycle
Readiness Error - A resource cannot be published as ready after admission closes or a tracked task has already made its lifecycle unavailable.
- Lifecycle
Registration Error - A lifecycle resource can no longer accept registration changes.
- Lifecycle
State - A resource’s retained lifecycle state.
- Resource
Ownership - Which layer owns the underlying resource rather than merely a scoped capability to use it.
- Shutdown
Observation - A bounded observation of retained supervisor shutdown work.
- Shutdown
Outstanding Resources - The current availability of shutdown inventory for a budget-limited
observer.
SnapshotPendingnever means that no resources remain.
Functions§
- current_
scope - The trusted host scope carried by the currently admitted task, if any.
- spawn_
blocking - Start blocking work with its admission lease inside the actual worker. Dropping or timing out its join waiter cannot release that lease. Work started by an admitted host task inherits its lifecycle authority; direct compatibility callers retain an independent operation scope instead.