Expand description
Persistent interactions: cards, confirmations, selections (spec §15).
An interaction is a durable, server-owned record. The client only ever
sends back an interaction id, an option id and the case revision it saw
(I7); the meaning of the click is the StoredInteractionAction persisted
with the option. validate_response is the pure gate every response
passes through before anything executes.
Structs§
- Accepted
Response - A response that passed every §15.5 rule.
- Interaction
- A persisted interaction (spec §15.1).
- Interaction
Option - A stored option (spec §15.3).
- Interaction
Option View - Client-facing option: no server action.
- Interaction
Payload - Immutable content of an interaction (spec §15.1).
- Interaction
Spec - What a reducer or workflow asks the engine to create (spec §13.3, I6).
- Interaction
View - Client-facing projection of an interaction (spec §18.1).
- Review
Diff Entry - One line of a review card: a field before and after the proposed change.
Enums§
- Action
Class - What a stored option authorizes when it is chosen (spec §15.3).
- Field
Value - One side of a field change: absent, or an explicit JSON value.
- Freeform
Policy - Whether an option accepts free text (spec §15.5).
- Interaction
Kind - The shape of an interaction (spec §15.2).
- Interaction
Rejection - Why a response was not accepted (spec §15.5).
- Interaction
Status - Lifecycle status of an interaction (spec §15.4).
- Option
Style - Visual emphasis of an option, for clients.
- Stored
Interaction Action - The server-side meaning of an option (spec §15.3). Never supplied by the client.
- Text
Resolution Policy - Whether and how typed text may resolve an interaction (spec §15.7).
Functions§
- validate_
response - Pure validation of a client response against the stored interaction (spec §15.5).