SDKs
12 items
Conventions
Response envelope, KError, naming and casing, HTTP methods, versioning, pagination, retry, idempotency, headers, status codes, wire format, SDK packages — the cross-cutting rules every endpoint follows.
Auth
Sign-up, sign-in, refresh, JWKS, identity providers, MFA, sessions, and the transactional-email triple-trigger — the identity surface every other API call depends on.
Data
Collections, migrations, the query builder, full-text search, read-only SQL, realtime subscriptions, streams, object storage and durability — Pillar A's API surface.
Security
Identity model (RBAC + JWT claims), the audit log (envelope, catalogue, query, export, SIEM), transport security (TLS, HSTS), and credential lifecycle — Pillar B's API surface.
Control
JSON-policy attribute-based access control (ABAC and PBAC) for collections, IRREVERSIBLE_ACTION_GATE for destructive actions, Maker-Checker for data-write approval workflows — the Control pillar's API surface.
Compute
Function compute in Firelock, with a Bun guest and a Wasmtime guest, the function registry, the trigger registry, invocation routing, model generation and embeddings, and the extensions Kilimanjaro builds.
Extensions
The extension entity, manifest schema, lifecycle state machine, hook invocation contract, management-plane endpoints, and per-project surface — the platform primitive for installable modules.
Errors
The closed-taxonomy error catalogue — family taxonomy, HTTP status conventions, warning vs error distinction, lifecycle, and where to look up specific codes.