> ## Documentation Index
> Fetch the complete documentation index at: https://docs.accelmars.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Who owns what

> Understand the boundaries between model execution, permissions, application results and money.

A useful architecture map does more than connect boxes. It identifies who is allowed to decide a fact—and who must obtain that fact from someone else.

Gateway's central responsibility is model-call execution. It must not acquire new authority merely because several systems send information through it.

## The application owns the purpose and the answer

An application decides what it wants to accomplish. Under a durable-work profile, its caller component preserves the original invocation before sending and saves the answer when exact replay is required.

Gateway owns the associated inference history, not the application's business commitment. A recorded model success does not establish that the application saved the answer or accepted the surrounding task.

## Registry owns approved supply

Registry publishes the approved model offerings and policy. Gateway consumes a coherent version and uses it to plan a call.

A runtime failure may exclude a candidate temporarily. It cannot make an unsupported feature supported, publish a new official model profile or remove a privacy restriction. Reporting an observation and approving a capability are separate actions.

## Permissions and data handling have their own owners

The authenticated host establishes the caller's identity. Authority and Warrant supply applicable grants. Context supplies governed source material, its current version and disclosure restrictions where that profile requires them. Credential and egress owners control the authorized credential and destination.

Gateway checks and respects these inputs. A valid model profile is not permission to send any data to that model; possession of a credential is not permission to use it for any tenant or purpose.

## Gateway owns execution evidence

Gateway keeps the original call identity, permitted attempts, output-exposure boundary and execution outcome. Its protected record contains references and evidence, not copies of prompts, answers or private reasoning.

The applicable native-capacity record must agree with the execution record across failures. These capacity effects are not customer charges.

## Financial owners establish financial facts

Tender owns applicable wallet or commerce effects; Ledger owns financial journal effects; Gauge owns its usage or capacity facts. Platform composes the original financial result across the participating owners.

Gateway can deliver execution evidence and record an exact, qualified receipt of the resulting settlement. It cannot turn a transport acknowledgement into proof that all financial effects committed.

## One example across the boundaries

In an illustrative expense-classification application, a model returns a category for an invoice. Gateway can record which attempt produced that result and what usage was reported.

The application must still decide whether the category is acceptable. A tool owner must authorize any subsequent posting. The financial owners must establish whether money moved. None of those outcomes follows automatically from receiving valid JSON.

Some AccelMars sources describe a future transfer of work ownership to Work/Execution. The current reviewed caller is Guild/Platform, with interim commitments remaining Guild-owned. A planned transfer is not a second, already-active owner. TENURE names the delivery program, not a running component that issues requests or cancellation grants.

Read [Gateway is not a workflow engine](/public/gateway/architecture/not-a-workflow-engine) and [Data and permissions](/public/gateway/relationships/context-and-permissions) for the practical consequences.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.