A redacted local record for the running gateway and the kimi-k3 example.
Read the simple version or open technical detail in any section.
1
Big idea
kimi-k3 is the public name; k3 is the upstream name. The same example must respond in chat, structured Responses, and tools.
Think of it as… It is an interpreter between two languages: a local alias does not change the name the provider understands. The analogy breaks because every protocol has its own envelope..
Under the hood
Chat returned upstream k3 and a sentinel; structured Responses returned completed and a sentinel; tools preserved echo_probe without sending tool_choice. reasoning_effort=max is recorded in both protocols.
2
In one picture
public kimi-k3 alias — governs — kimi-k3 maps to upstream k3.
3
In the code
This is the real local path and a safe read-only command.
CONFIG-MODEL-POLICY-EVIDENCE.md
# trecho real, não editado
node validation-harness/validate-gateway-full-window.mjs
# use structured Responses input; keep the local credential outside output
Open it yourself
node validation-harness/validate-gateway-full-window.mjs
# use structured Responses input; keep the local credential outside output
4
Try it
Use the controls to retrieve the evidence before reading the explanation.
upstream k3 name — matches — Structured Responses returned message and sentinel.chat request envelope — routes to — echo_probe arrived without tool_choice.chat sentinel output — excludes — kimi-k3 maps to upstream k3.structured Responses input — proves — Structured Responses returned message and sentinel.reasoning item — bounds — echo_probe arrived without tool_choice.message item — maps to — kimi-k3 maps to upstream k3.completed status — restarts as — Structured Responses returned message and sentinel.reasoning effort max — preserves — echo_probe arrived without tool_choice.tools array — compares with — kimi-k3 maps to upstream k3.echo_probe call — returns — Structured Responses returned message and sentinel.tool_choice filter — confirms — echo_probe arrived without tool_choice.K2.7 regression — qualifies — kimi-k3 maps to upstream k3.public kimi-k3 alias verification record — records — Structured Responses returned message and sentinel.
Three-frame summary
1 Map the public alias to k32 Use the structured Responses envelope3 Verify tool delivery without tool_choice
Chat returned upstream k3 and a sentinel; structured Responses returned completed and a sentinel; tools preserved echo_probe without sending tool_choice. reasoning_effort=max is recorded in both protocols.
Record the observation, preserve the exception, and choose the next narrow proof.
retrievePublic alias kimi-k3click to flip
kimi-k3 maps to upstream k3.
retrieveStructured Responses envelopeclick to flip
Structured Responses returned message and sentinel.
retrieveecho_probe toolclick to flip
echo_probe arrived without tool_choice.
Predict before revealing
Why does structured Responses input matter here?
The observed structured form returns a message item and requested sentinel, unlike the exploratory scalar form.
Worked example
1Send the chat sentinel to public kimi-k3.
2Send the structured Responses sentinel.
3Confirm echo_probe arrives while tool_choice is absent.
Retrieval review
Why does structured Responses input matter here?
The observed structured form returns a message item and requested sentinel, unlike the exploratory scalar form.
Ask which boundary you would prove next; the next lesson narrows a different operational risk.