Skip to main content
A diagram that shows Application → Gateway → Provider does not require three separately deployed servers. It describes responsibilities and an interaction. The physical arrangement must be established separately. Gateway is designed as a composable engine. Platform can embed it through an in-process adapter, while external clients enter through HTTP and the provider leg sends network requests.

​
Different entrances, shared decisions

The source design includes text-oriented HTTP and trusted-host entry paths, with buffered and incremental delivery where the relevant profile supports them. An edge may format Chat-style or Messages-style responses differently. These differences must not create separate retry policies, hidden provider sends or competing accounting records. Request parsing and wire formatting belong at the edges. The common execution rules belong in the core. The inspected source history still contained older direct adapter paths. Their existence is an integration obligation, not evidence that every entrance already converges on the selected core.

​
Caller delivery and provider transport are independent

A provider may stream internally while the application receives one complete answer. That is useful when Gateway must hold a document until validation finishes. The opposite claim is not valid: collecting a complete provider response and splitting it into chunks afterward does not demonstrate genuine live streaming. A caller requiring incremental output needs the applicable offering and route to support it.

​
A shared database does not merge ownership

Different engines may use separate schemas and permissions inside a common PostgreSQL deployment. Sharing the physical database does not let one engine write another’s facts freely. Conversely, Gateway’s required execution-record and native-capacity changes must use the same actual transaction where that profile requires atomicity. Two independently committed database helpers are not equivalent merely because they address the same server. The company core PostgreSQL profile and the isolated Gateway evidence experiments also have different role and durability requirements. A role arrangement observed in one cannot be promoted into a universal company rule.

​
Text scope does not authorize breaking existing consumers

The selected work concentrates on ordinary text, reasoning-enabled text, structured results and incremental delivery. It does not add speculative persistent voice-resource management. That boundary is not permission to remove existing consumer capabilities such as speech or embedding interfaces during a shared-adapter migration. Existing callers and outstanding obligations must be inventoried and preserved under the accepted compatibility plan.

​
What establishes a real deployment

A deployment statement needs the actual binary or image, source and dependency versions, effective configuration, database installation, permissions and suppliers. A local qualification setup using a fake provider is a different profile from production serving. This guide explains the architecture; it does not invent a public endpoint, SDK method or installed service. Use Implementation status to understand the available evidence, and Database boundaries for the storage responsibilities.