Concepts overview

These pages explain the ideas that carry Flightdeck’s architecture. Read them in order for the whole model, or jump to the one you need:

1. Architecture — one deployable, strictly-bounded modules, two network edges, and the exact path a request takes from edge to module to response.
2. Tenancy — every request resolves its tenant from a credential, never a parameter. There is no default tenant.
3. Topology — modules, edges, and surfaces. Ownership boundaries are enforced, not just documented.
4. Events — an in-process dispatcher today; the contract shape (registered schema, required tenant_ref, self-contained payload) is the same shape a future out-of-process bus would use.
5. Money — integer cents everywhere, double-entry bookkeeping in the accounting module, deterministic idempotency keys.
6. Idempotency — why keys are deterministic, header versus body, replay semantics per route class, and how to build safe retries.
7. Performance & caching — ETag/304 on site reads, CDN and asset resolution, the manifest last-good cache, and what is honestly not cached.
8. Security — the trust model: credential-carries- ownership, scopes, server-side tokens, the SSRF guard, the secret model, and the RUO-claims guardrail.
9. Manifest & sections — a store’s look and layout as data: theme tokens, a typed section registry, and the versioned publish flow.
10. Provenance & verification — the supplier-side partner registry behind the provenance seal, a public fail-closed endpoint a storefront cannot fake.