Module loop_state 

Public loop state namespace. Use it for the documented loop state API surface; prefer crate-root re-exports for common imports. Module items must preserve the core ownership and side-effect boundaries described in this file. Application-layer coordination over core primitives. Use these services to lower helpers, drive runs, validate output, coordinate tools, approvals, delivery, isolation, telemetry, and feature layers. Methods in this layer may call configured ports, mutate in-memory stores, append journals, or publish events as documented. This file contains the loop state portion of that contract.

Structs

AgentStateMachine

Holds agent state machine application-layer state or configuration. Use it with the documented coordinator methods; run, journal, event, provider, or port effects are called out on those methods rather than on construction.

LoopTerminalResult

Holds loop terminal result application-layer state or configuration. Use it with the documented coordinator methods; run, journal, event, provider, or port effects are called out on those methods rather than on construction.

TransitionGuardSet

Holds transition guard set application-layer state or configuration. Use it with the documented coordinator methods; run, journal, event, provider, or port effects are called out on those methods rather than on construction.

TransitionInput

Holds transition input application-layer state or configuration. Use it with the documented coordinator methods; run, journal, event, provider, or port effects are called out on those methods rather than on construction.

TransitionOutput

Holds transition output application-layer state or configuration. Use it with the documented coordinator methods; run, journal, event, provider, or port effects are called out on those methods rather than on construction.

TransitionRule

Holds transition rule application-layer state or configuration. Use it with the documented coordinator methods; run, journal, event, provider, or port effects are called out on those methods rather than on construction.

Enums

CheckpointPolicy

Enumerates the finite checkpoint policy cases. Serialized names are part of the SDK contract; update fixtures when variants change.

LoopEventKind

Enumerates the finite loop event kind cases. Serialized names are part of the SDK contract; update fixtures when variants change.

LoopState

Names the finite phases of the SDK run loop. Use it in state tables, journal records, and tests to describe where a run is paused or executing; the enum is a marker only and side effects happen in the driver transition that enters the phase.

LoopStopReason

Enumerates the finite loop stop reason cases. Serialized names are part of the SDK contract; update fixtures when variants change.

LoopTerminalStatus

Enumerates the finite loop terminal status cases. Serialized names are part of the SDK contract; update fixtures when variants change.

LoopTrigger

Enumerates the finite loop trigger cases. Serialized names are part of the SDK contract; update fixtures when variants change.

MaxIterationOutcome

Enumerates the finite max iteration outcome cases. Serialized names are part of the SDK contract; update fixtures when variants change.

SideEffectPolicy

Enumerates the finite side effect policy cases. Serialized names are part of the SDK contract; update fixtures when variants change.

TransitionGuard

Enumerates the finite transition guard cases. Serialized names are part of the SDK contract; update fixtures when variants change.

Functions

contract_state_names

Returns the contract state names derived from this value. This derives SDK state locally and does not call host adapters.

transition_table

Returns the transition table derived from this value. This derives SDK state locally and does not call host adapters.

validate_transition

Validates the application::loop_state invariants and returns a typed error on failure. Validation is pure and does not perform I/O, dispatch, journal appends, or adapter calls.