Skip to content

Commit 0da9e20

Browse files
authored
Merge pull request #2049 from lidge-jun/codex/wp9-structure04-drift
docs(structure): scope canonical Fast injection to the bridged Chat path
2 parents e446607 + 383d959 commit 0da9e20

1 file changed

Lines changed: 4 additions & 3 deletions

File tree

‎structure/04_transports-and-sidecars.md‎

Lines changed: 4 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -660,9 +660,10 @@ normalization, credential and provider headers, capability-specific fields, and
660660
messages (including `name` and separate `system`/`developer` entries), Chat token controls,
661661
sampling/logprob fields, caller identity/metadata, and caller stream options retain their wire
662662
shape. For streams, caller `stream_options` are merged with mandatory `include_usage: true`. On
663-
classified Fast-capable routes, canonical Fast follows the resolved Fast policy and does not require
664-
`chatServiceTier`; foreign caller tiers still require `chatServiceTier: true`, as does every caller
665-
tier on an unclassified Chat route. `parallel_tool_calls` is emitted only for providers opted into
663+
the native passthrough there is no canonical Fast injection and no wire mapping: every caller
664+
`service_tier` — canonical or foreign — is forwarded raw and only under `chatServiceTier: true`,
665+
and `fastMode` injects nothing here. Resolved-Fast-policy injection applies only to routes that
666+
take the Chat -> Responses -> Chat bridge below. `parallel_tool_calls` is emitted only for providers opted into
666667
parallel tools (or pinned false by the existing provider opt-out contract).
667668
Combo/policy routes and requests that need Responses-only hosted tools, continuation, background,
668669
or storage semantics retain the existing Chat -> Responses -> Chat bridge.

0 commit comments

Comments
 (0)