Expand description
Turn input protocol (spec §9).
A turn may carry free text, a structured interaction response, attachments and a server-issued origin reference at the same time. Mutual exclusion between text and a card reply is forbidden by design: a user may click “Confirm” and ask a question in one message.
Structs§
- Actor
Context - The authenticated actor of a turn, supplied by the application’s authentication middleware. Trusted after authentication (spec §25.1).
- Attachment
Content - The bytes of one attachment, as the application holds them.
- Attachment
Ref - Reference to an attachment uploaded with the turn. The content itself is fetched by the application; the core only tracks identity and metadata.
- Interaction
Response - A structured reply to a persisted interaction (spec §9).
- Origin
Ref - A server-validated origin reference (spec §12.4): the UI surface that knows the exact record the user is looking at names it, so the model does not have to rediscover it from prose.
- Turn
Input - One user turn as accepted by the runtime (spec §9).
- Turn
Limits - Size limits on one turn’s input, checked before anything is interpreted.
Enums§
- Attachment
Error - Why an attachment could not be fetched.
Traits§
- Attachment
Source - Where the bytes of a turn’s attachments come from.