Glossary

The terms below name different facts and responsibilities. Similar words should not make those boundaries disappear.

​

Request, call and attempt

Caller — The application or component asking Gateway to perform an inference. A durable caller also preserves the original invocation and any answer it promises to replay. Invocation — A particular caller-owned request for work. Retrying its delivery should preserve its identity; a genuinely separate turn needs a distinct identity even if the text is identical. Logical call — One original model-execution request in Gateway. It can contain several permitted physical attempts without becoming several independent calls. Physical attempt — One permitted provider dispatch, with its own identity and place in the original call’s attempt history. A skipped planning candidate is not an attempt. Idempotency key — A stable request key within an authenticated scope. Reusing it asks about the original operation; it is not permission to generate another answer. Request fingerprint — A canonical digest used to check that the meaning of a repeated request matches the original. It is not a prompt archive or a substitute for authenticated identity.

​

Planning and supply

Offering — The particular model/provider/deployment or account/protocol combination whose capabilities and restrictions matter for execution. Qualified supply — Offering information supported by the required review and evidence. A model name or adapter registration alone is not qualified supply. Registry — The owner that approves and publishes the applicable catalogue and policy. Runtime feedback does not automatically rewrite those approved facts. Snapshot — A coherent version of the published supply and policy references. Gateway must not combine incompatible pieces from different versions. EffectiveCall — The resolved execution controls produced by the planner from requirements, approved capabilities and policy. An adapter translates this decision rather than making a different one.

​

Outcomes and recovery

Outcome certainty — What is actually established about an operation. A failure category and certainty are separate: a connection failure can leave remote execution unknown. Unknown — The available evidence cannot establish the relevant fact. It does not mean false, zero, unsupported or an unclassified error. Output commitment — The protected boundary recording that meaningful output may be exposed. It is not proof of user receipt, but it prevents hidden replacement of the answer. Terminal outcome — The accepted ending of one attempt. The final logical-call outcome is a related but separate record. Replay — Resolving an existing operation or returning its retained result. It does not silently run the model again. Fencing — Preventing an old execution instance from making unauthorized new changes after ownership or history has moved on. Backpressure — Slowing the producer-facing path because the caller cannot drain output, rather than accumulating unlimited buffered data.

​

Records and business responsibilities

O1 — Gateway’s protected, content-free execution record and write boundaries. It does not store the answer or own customer payments. Native G4 — The native provider-capacity effects that the applicable Gateway profile couples to execution records. It is distinct from host Gauge and customer money. Outbox — A durable notification obligation committed with the relevant local record. Its presence does not prove the receiving owner has completed the work. Settlement acknowledgement — An exact receipt for a qualified original financial result. Transport success alone is not that result. R9 — Gateway’s separate provider-observation reporting path. Observations are not automatically approved capabilities or financial facts. Context / Authority / Warrant — Owners of applicable source material, currentness, disclosure conditions and grants. Data identifiers cannot grant themselves permission. Guild / Work / Platform — Components in the surrounding professional and application system. Their current and target ownership scopes must be distinguished; Gateway does not own their business fulfillment. CRL / TENURE — Composed responsibility commitments and the delivery program respectively, not extra model-execution services. RPO / RTO — Recovery point and recovery time objectives under a stated failure model. An objective is not a measured deployment guarantee. Use the reading paths for a connected explanation or the FAQ for a focused answer.