# AccelMars Documentation

> Gateway Reader Edition 1.1, based on Gateway Final Design 1.0; implementation qualification separately evidenced.

- [AccelMars Documentation](https://docs.accelmars.com/index.md): Explore officially published AccelMars product documentation.
- [Gateway, explained](https://docs.accelmars.com/public/gateway.md): Understand how AccelMars plans AI requests, tracks execution and handles uncertainty.
- [Why Gateway exists](https://docs.accelmars.com/public/gateway/start/why-gateway.md): An AI connection is easy to start. Consistent execution, recovery and accountability need more.
- [Choose a reading path](https://docs.accelmars.com/public/gateway/start/reading-paths.md): Start with the question you need to answer, not an internal document number.
- [How Gateway works](https://docs.accelmars.com/public/gateway/architecture/how-it-works.md): Follow the responsibilities behind a request—from requirements to evidence and delivery.
- [Who owns what](https://docs.accelmars.com/public/gateway/architecture/responsibilities.md): Understand the boundaries between model execution, permissions, application results and money.
- [Interfaces are not deployment boxes](https://docs.accelmars.com/public/gateway/architecture/interfaces-and-deployment.md): The same execution rules can serve different entry formats without requiring a new service for every role.
- [Gateway is not a workflow engine](https://docs.accelmars.com/public/gateway/architecture/not-a-workflow-engine.md): A model call can support a task without owning the task, its approval or its side effects.
- [Why an approved model catalogue matters](https://docs.accelmars.com/public/gateway/supply/approved-models.md): A model name is not enough: the exact offering must support the request and its restrictions.
- [Planning a compatible request](https://docs.accelmars.com/public/gateway/supply/planning-a-request.md): Resolve what the caller needs before a provider adapter writes the request.
- [Reasoning and answer budgets](https://docs.accelmars.com/public/gateway/supply/reasoning-and-budgets.md): Allowing a model to think must not accidentally consume all the room reserved for its answer.
- [When the answer must follow a schema](https://docs.accelmars.com/public/gateway/supply/structured-answers.md): JSON-looking text, valid JSON and a schema-valid result are different promises.
- [Your first request](https://docs.accelmars.com/public/gateway/journeys/first-call.md): Follow a simple text request and see why the record, the answer and the business result are separate.
- [Following a live stream](https://docs.accelmars.com/public/gateway/journeys/live-stream.md): Show text as it is generated without hiding partial failure or joining two different answers.
- [Restarting without repeating the work](https://docs.accelmars.com/public/gateway/journeys/restart-and-replay.md): Recover the original invocation and saved result instead of quietly generating another answer.
- [When a confirmation is lost](https://docs.accelmars.com/public/gateway/journeys/lost-confirmation.md): A database may have committed even when the caller never receives its acknowledgement.
- [Attempts and retries](https://docs.accelmars.com/public/gateway/reliability/attempts-and-retries.md): A retry is another physical action, not a reset of the original request.
- [The point where an answer cannot be replaced](https://docs.accelmars.com/public/gateway/reliability/output-boundary.md): Once part of an answer may be visible, a different model cannot quietly finish it.
- [Cancellation and slow readers](https://docs.accelmars.com/public/gateway/reliability/cancellation-and-backpressure.md): Keep work owned and buffers bounded without confusing a slow caller with a stalled provider.
- [Understanding timeouts](https://docs.accelmars.com/public/gateway/reliability/timeouts.md): Connection, provider progress and caller delivery need different clocks.
- [Execution evidence without storing the answer](https://docs.accelmars.com/public/gateway/records/execution-evidence.md): Record what Gateway did while keeping prompts, responses and private reasoning out of its execution ledger.
- [Usage, provider cost and customer payment](https://docs.accelmars.com/public/gateway/records/usage-cost-and-payment.md): Three related questions must not collapse into one precise-looking number.
- [The owners of a payment](https://docs.accelmars.com/public/gateway/relationships/money-owners.md): Execution evidence can support settlement, but it cannot substitute for the systems that move and record money.
- [Database boundaries](https://docs.accelmars.com/public/gateway/relationships/database.md): Sharing PostgreSQL does not erase ownership, and separate commits do not become atomic by sharing a server.
- [Data and permissions](https://docs.accelmars.com/public/gateway/relationships/context-and-permissions.md): Being able to read information is not the same as being allowed to send it to any model.
- [A model call inside a larger task](https://docs.accelmars.com/public/gateway/relationships/business-work.md): Preserve responsibility for the work while Gateway takes responsibility for the inference.
- [Ready to serve is more than running](https://docs.accelmars.com/public/gateway/operations/startup.md): A live process is not proof that a request can be executed under the required controls.
- [Investigating a request](https://docs.accelmars.com/public/gateway/operations/monitoring.md): Follow the original operation and ask each record only for the fact it can establish.
- [Security and privacy in practice](https://docs.accelmars.com/public/gateway/operations/privacy.md): Protect the request at admission, at provider disclosure and in the records left afterward.
- [Recovery after a storage failure](https://docs.accelmars.com/public/gateway/operations/restore.md): Recover the acknowledged history and its owners, not just a database that starts.
- [Why the design makes these trade-offs](https://docs.accelmars.com/public/gateway/design/tradeoffs.md): Understand what the selected controls protect—and what they make more demanding.
- [What has actually been demonstrated](https://docs.accelmars.com/public/gateway/design/implementation-status.md): Read local progress, known limitations and production evidence as separate statements.
- [How the design evolved](https://docs.accelmars.com/public/gateway/design/evolution.md): The useful history is what each step taught—not a wall of internal decision identifiers.
- [Glossary](https://docs.accelmars.com/public/gateway/reference/glossary.md): Plain-English definitions for the terms used in this guide.
- [Frequently asked questions](https://docs.accelmars.com/public/gateway/reference/faq.md): Direct answers about scope, retries, streaming, records and evidence.
- [Where to go deeper](https://docs.accelmars.com/public/gateway/reference/engineering-map.md): A reading map for moving from an explanation to the exact implementation contract.
- [About this edition](https://docs.accelmars.com/public/gateway/reference/about-this-edition.md): What Reader Edition 1.1 explains, what it preserves and how future updates should stay consistent.


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