> ## 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.

# Where to go deeper

> A reading map for moving from an explanation to the exact implementation contract.

This guide builds understanding. An implementation also needs exact types, canonical encodings, database boundaries and the current source that owns each interface.

The engineering collection remains separate so that these details do not interrupt the reading path. This page explains what to look for when you need that precision.

## Planning and provider integration

For model eligibility or parameter encoding, start with the approved offering schema, the pure planner's rules and the provider-adapter contract. Check mandatory versus optional features, unknown facts, reasoning/output arithmetic and the actual native request.

The provider adapter translates a resolved call. The supply publisher and planner decide what that call is allowed to mean. Changing one should not silently transfer the other's responsibility.

Reader starting points: [Approved model supply](/public/gateway/supply/approved-models) and [Planning a request](/public/gateway/supply/planning-a-request).

## Execution identity and recovery

For idempotency, follow the original caller invocation through Gateway's logical call and attempt identities. Bind the exact canonical fingerprint and persisted timestamp rules; do not invent them from prose.

For recovery, use the full accepted failure matrix, certainty rules, reason ordering and shared limits. The summary table in this guide highlights important branches but does not replace the complete contract.

Reader starting points: [Restart and replay](/public/gateway/journeys/restart-and-replay) and [Attempts and retries](/public/gateway/reliability/attempts-and-retries).

## Protected storage and streaming

For database work, inspect the actual adopted SQL bodies, installation, grants and same-transaction native effects. A signature in a document is not a current installed routine.

For streaming, inspect the canonical event model, all seven policy fields, parser and byte bounds, output confirmation and cancellation ownership. A local six-field structure is not automatically the complete accepted policy.

Reader starting points: [Execution evidence](/public/gateway/records/execution-evidence), [Live streaming](/public/gateway/journeys/live-stream) and [Timeouts](/public/gateway/reliability/timeouts).

## Caller and financial composition

The source tour places catalogue and provisioning responsibilities with Platform, protected execution and readback with Gateway, and durable invocation/result handling with the caller implementation. These areas were reviewed at different source versions.

The streaming and caller branches are separate descendants of the local non-streaming baseline. Use the exact source map before combining their interfaces or claiming joint coverage.

Financial integration additionally needs the real producer, expected effect plan, current receiver and required witnesses. A fixed data validator can be implemented with fixtures before those live suppliers exist; it cannot manufacture them.

## Make an implementation task concrete

A useful task names its source version, permitted files, actual input/output types, prerequisites, finite resources, positive and negative observations and stop conditions. It distinguishes a compile, an isolated test and a production qualification.

The internal edition package retains the exact source crosswalk and the treatment of all 46 original reader documents. Readers do not need those hashes or private archive links in order to understand the guide. Engineers should obtain the controlled Engineering Design of Record through the workspace, not infer a callable API from this website.

See [Implementation status](/public/gateway/design/implementation-status) and [About this edition](/public/gateway/reference/about-this-edition) before treating an explanation as a release claim.


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