Expand description
Operation taxonomy: what a request is, independent of any provider.
v2’s model, kept: an Operation names the action, an OperationKind
names the wire shape it arrives in, and the pair (OperationKey) is
what routing rules and transforms key on. Content generation has several
kinds because OpenAI Responses and Chat Completions are genuinely
different wire shapes, not labels.
Every enum here is exhaustive-feature gated: workspace builds match
exhaustively (adding a variant is a compile-error checklist), external
consumers see #[non_exhaustive]. The starter variant set covers the
first porting wave; it grows port by port, compiler-enforced.
Structs§
- Operation
Key - What routing rules, transforms, and channel support tables key on.
- Operation
KeyError
Enums§
- Content
Generation Kind - The distinct content-generation wire shapes.
- Operation
- Concrete action.
- Operation
Group - Broad capability a client asks for.
- Operation
Kind - Wire shape of an operation.
- Wire
Family - Wire family for provider-shaped (non-content-generation) operations.
v2 called this
Provider; renamed — it names a wire dialect, not a configured backend.