Concepts
The ideas behind the product pages: windows, thresholds, the receipt chain, fail-open and fail-closed, roles and keys.
Concepts explain why the gateway behaves the way the product pages say it does: how a cap counts spend against a window, how one receipt chains to the one before it, what fails open and what fails closed, and who in your organization may change what. Each page teaches one idea and names the code it was written from.
- Caps and windows The five windows a cap runs on, their UTC boundaries, what the week means in the code, and how several caps on one scope combine.
- Alert thresholds The percentages a cap warns at: whole numbers from 1 to 100, up to ten per cap, each fired once per window and re-armed at the reset.
- The hash-chained ledger The recipe recovea-chain-v1: fourteen fields in order, joined by U+001F, hashed with SHA-256 from a genesis of 64 zeros, and how to re-derive one receipt.
- Fail-open and fail-closed What the gateway does when part of it fails: it passes your traffic through, except where you armed a cap, which refuses rather than guess.
- Content-free by schema The metering record has no field that can hold a prompt, a completion or a tool argument. That is a property of the schema, not a retention policy.
- Roles The five roles, Owner, Admin, Member, Billing and Viewer, and what each may do, from the capability table the server enforces on every platform route.
- Organization and keys Your organization, the gateway keys it mints, and the project a key can carry: what each one is and who may change it.
- Tags The x-recovea-tags request header: its shape, its limits, the four namespaces, and the rule that it never reaches your provider.
- Glossary One-line definitions of the words these docs use, each pointing at the page that explains it.