Concepts overview

These pages explain the concepts you rely on when building against the RUO Pro API. Read them in order, or jump to the one you need:

1. Tenancy — every request resolves its tenant from a credential, never a parameter. There is no default tenant.
2. Money — integer cents everywhere, fail-closed on overdraw and refund, deterministic idempotency keys.
3. Idempotency — why keys are deterministic, header versus body, replay semantics per route class, and how to build safe retries.
4. Performance & caching — ETag/304 on site reads, asset resolution, and what is honestly not cached.
5. Security — the trust model: credential-carries- ownership, scopes, server-side tokens, and webhook signature verification.
6. Manifest & sections — a store’s look and layout as data: theme tokens, a typed section registry, and the versioned publish flow.
7. Provenance & verification — the partner registry behind the provenance seal, a public fail-closed endpoint a storefront cannot fake.