Skip to main content

​
Can an application use Gateway without Guild?

Yes, under the applicable authenticated ordinary-caller profile. Gateway is an execution engine, not a requirement to create a professional-work system before making a text request. See Gateway is not a workflow engine.

​
Does one request always mean one provider call?

No. A logical call may include several permitted physical attempts. Every real send must be counted inside the original plan and remaining limits; hidden client-library retries are not exempt. See Attempts and retries.

​
Can Gateway retry when the outcome is unknown?

Only in the specific live, pre-output cases permitted by the accepted recovery policy and current authority, preserving the earlier uncertainty and possible consumption. Same-target transport retry requires known certainty. A crash-recovery sweeper never redispatches an uncertain attempt.

​
Can another model finish a broken stream?

Not secretly under the same call after meaningful output may have been exposed. Gateway must keep the incomplete result honest. A caller may explicitly request new work under a distinct identity. See The output boundary.

​
Will the same key give me the same answer again?

The key resolves the original operation; Gateway’s content-free execution record cannot recreate answer bytes. An application can replay its saved answer if it retained one under the correct invocation. Otherwise the replay limitation must be reported rather than hidden with another generation. See Restart and replay.

​
Why refuse a model that probably supports the feature?

A mandatory requirement needs applicable approved evidence, not probability or a marketing claim. Unknown capability is different from proven lack of support, but neither authorizes an unsupported mandatory combination. See Approved model supply.

​
Does a schema-valid answer mean the business result is correct?

No. The output contract checks the declared structure. The application still owns the acceptance criteria and any later action. A tool-call object is data, not permission to execute a tool. See Structured answers.

​
Does cancellation stop provider billing?

A legitimate cancellation stops local owned work under its contract. It does not prove that the remote provider stopped computing or charging. A passive viewer disconnect is also not necessarily a cancellation by the durable work owner. See Cancellation and slow readers.

​
Does a heartbeat prove that the model is making progress?

No. Gateway’s edge heartbeat indicates liveness. Provider transport activity, generation progress and the overall lifetime have separate controls. See Understanding timeouts.

​
Does missing usage mean the request was free?

No. A reported zero is known zero; an absent usage or price dimension is not. Provider cost, reserved capacity and customer charge are separate facts. See Usage and payment.

​
Does HTTP success from the settlement receiver prove payment?

No. Gateway needs the qualified original result from the relevant financial owners and the exact accepted receipt boundary. A transport acknowledgement or self-asserted JSON field cannot establish every foreign effect. See The owners of a payment.

​
Is the entire design running in production?

The source evidence summarized here does not establish that. It includes specific local experiments and known integration, supplier and qualification gaps. See Implementation status, dated 12 October 2026.

​
Can engineering work proceed before all real suppliers exist?

Yes. The final handoff permits source-bound pure and consumer work with conforming synthetic fixtures. Real side effects and capability claims require the genuine dependencies and relevant activation evidence. Missing runtime qualification does not prevent reading or implementing the documented design.

​
Does Reader Edition 1.1 change the engineering design?

No. It reorganizes and explains Final Design 1.0 for readers. The original engineering authority and historical evidence remain separate. See About this edition.