Skip to main content

Module input

Module input 

Source
Expand description

§8 Input types — the 6 input variants accepted by the runtime layer.

Core never sees these. The runtime’s policy table resolves each Input to a PolicyDecision, then the runtime translates accepted Inputs into RunPrimitive for core consumption.

Structs§

ContinuationInput
Explicit continuation request that asks the runtime to keep draining ordinary work after a boundary-local event (for example, terminal peer responses injected into session state).
ExternalEventInput
External event input.
FlowStepInput
Flow step input from mob orchestration.
InputHeader
Common header for all input variants.
InputVisibility
Visibility controls for an input.
OperationInput
Explicit operation/lifecycle input admitted through runtime instead of being smuggled through transcript projections or peer-only paths.
PeerInput
Peer-originated input from comms.
PromptInput
User/operator prompt input.

Enums§

Input
The 6 input variants accepted by the runtime layer.
InputDurability
Durability requirement for an input.
InputOrigin
Where the input originated.
PeerConvention
Peer communication conventions.

Functions§

externalize_input_images
hydrate_input_images
peer_response_terminal_input
response_terminal_status_from_wire

Type Aliases§

ResponseProgressPhase
Phase of a response progress update. This is the core projection enum, not a runtime-local duplicate.
ResponseTerminalStatus
Terminal status of a response. This is the core projection enum, not a runtime-local duplicate.