Module outbox
Expand description
Durable terminal-finalization intent types.
The outbox is deliberately a capability value rather than a queue API. A lifecycle backend stores one record for a terminal owner epoch, advances that record through explicit phases, and lets recovery replay every phase until it reaches the done phase.
Structs§
- Finalization
Intent - The durable initial intent and pre-terminal seam-state baseline for one finalization.
- Outbox
Advance Request - One atomic callback-phase advance request.
- Outbox
Effect Completion - A request to acknowledge one externally executed outbox effect.
- Outbox
Effect Intent - A stable effect id and its durable action.
- Outbox
Effect Key - The stable key for one effect in one terminal finalization.
- Outbox
Key - The durable identity of one terminal finalization.
- Outbox
Record - A durable snapshot of one outbox record.
- Replacement
Spec - Typed retry/fork metadata attached to a replacement creation effect.
Enums§
- Outbox
Effect - One action discovered while finalizing a terminal trial.
- Outbox
Phase - The ordered callback phases of a terminal finalization.
- Replacement
Outcome - The result of an idempotent replacement creation operation.
Constants§
- REPLACEMENT_
BLOB_ KIND - The kind tag used for core-owned replacement lineage state.
- REPLACEMENT_
BLOB_ VERSION - The schema version used for core-owned replacement lineage state.
Functions§
- replacement_
scope - Returns the typed state scope for a replacement’s attempt metadata.
Type Aliases§
- Effect
Intent - Alias for callers that refer to effects as intents.
- Finalization
Advance Request - Alias using the finalization terminology used by lifecycle callers.
- Finalization
Phase - Alias using the finalization terminology used by lifecycle callers.