# What can I read?

The proposed YamRail product catalog supplies the page and its default question panel from the same JSON. It is a static, read-only snapshot; it changes when an updated package is published, not on every live service event.

**Publication: candidate pending Human confirmation.** These new URLs are planned at the existing origin; this document does not assert that they are already served.

| GET / HEAD path | Content |
|---|---|
| `/Fuel/api/catalog.json` | Capabilities, architecture, specifications, scoped tests, failures, unfinished work and participation |
| `/Fuel/api/catalog.schema.json` | Strict JSON Schema 2020-12 |
| `/Fuel/api/catalog-evidence.json` | Earlier CF-only observation summaries; retained separately |
| `/Fuel/api/product-evidence.json` | Whole-system stages and historical, self-preserving task-load summaries |
| `/Fuel/api/catalog.openapi.json` | Current catalog and existing read-only API specification |

No token, new infrastructure or paid model request is required for these reads. Requests cannot change project data, grant permission or make a payment.

```sh
curl https://yamrail.ai/Fuel/api/catalog.json
```

# How do I interpret it?

- Human text is a map with `ja`, `en` and `pt` keys. `revision` identifies this catalog; `as_of` is its assembly time, not the time every fact was observed.
- `historical_load.tasks` records separate finite task executions: unit, exact period, load vector, protection actually bound at execution, outcome and limits. Model441 and CAD8,161 are different units; do not merge them. Duration2554.531s is the model controller's monotonic interval; the request timestamp interval is2554.229339s. These are bounded historical observations, not a claimed global capacity maximum.
- Graph stages distinguish Human authority, design, implemented prototypes, scoped deployment, public service and unknown. `DESIGN_DEPENDENCY` edges do not prove runtime wiring.
- Each numeric test or failure row carries its own period, scope and source references. Sources resolve in `sources[]`. Do not add different rows into a whole-product total.
- `null` is unknown or not established, not zero. `UNKNOWN`, `NOT_RUN` and `UNVERIFIED` are distinct from `PASS`. A bounded display or restoration pass does not qualify unrelated product behavior.
- Capability `PUBLIC` describes an existing accessible function. `DEVELOPMENT` describes work still being developed, including this candidate. `NOT_AVAILABLE` is unavailable here.
- Rewards are proposals. `amount_usd` preserves ranges or open-ended values as strings. Payments remain inactive.

# What does the question panel send?

The default panel searches this catalog in the browser and returns fixed, referenced answers. It makes no provider call and does not submit a question to the operator. Out-of-catalog questions receive no invented answer. It supports examples, retrying the catalog load and explicit reply-language changes.

The existing, separately selected AI explanation service remains available through its original route and consent screen. It is outside this read-only catalog contract; it sends input to an external model only after the existing send action and retains its existing authentication and cost controls. Do not enter personal or confidential information there, and verify important answers against original sources.

# Are the earlier endpoints still available?

The existing five read-only snapshots remain unchanged at `/Fuel/api/v1/about`, `/Fuel/api/v1/milestones`, `/Fuel/api/v1/rewards`, `/Fuel/api/v1/funding` and `/Fuel/api/v1/chat-policy`. Their dated metadata describes those earlier snapshots; it is not a current release selector. Their existing schemas remain under `/Fuel/api/schemas/`.

The older `openapi.yaml` and `ROUTE_STATUS.json` are preserved design documents containing unimplemented proposals. Use [catalog.openapi.json](/Fuel/api/catalog.openapi.json) for the current read-only scope. Preserving a proposal does not create its route.