Core concepts
A short glossary of the terms the rest of these docs use.
Household
Section titled “Household”The unit of data isolation. Every product’s data belongs to a household, and you only ever see your own household’s data. Full detail: Households.
Member / principal
Section titled “Member / principal”A person within a household. Some surfaces are member-private — visible only to the member they belong to — enforced in the database, not just the UI.
A commercial grouping of a product’s surface. Each product ships a personal suite
(vonkara, heldaro, kragara). A suite has tiers (Free, Starter, Pro, Premium).
See Entitlements & suites.
Entitlement / capability key
Section titled “Entitlement / capability key”A grant that says what you may access. Capability keys look like cap:<product>:<feature> (for
example cap:vonkara:pack-flow) and tier keys look like tier:<suite>:<ordinal>. These travel from
the platform to the products as gateway-injected headers.
The a-la-carte unit of a paid product surface — a bundle of features named by a cap:<product>:pack-*
key. Tiers bundle packs; some packs are also sold on their own. See Billing.
AI egress
Section titled “AI egress”Products never call a cloud AI provider directly. All AI calls go through one House chokepoint that
holds the provider credential, enforces a data boundary, meters usage per person, and gates access
behind a held cap:ai:use capability. This is also what powers Ask the docs.
The Aerial Lot
Section titled “The Aerial Lot”The shell’s home screen — an isometric “lot” where your products appear as rooms. See The Aerial Lot shell.