New paid orders and subscriptions are retired. Existing records, settlement and refunds remain available through your account.
Welcomes
The corpus of hospitality. Every kind of arrival — upstream source, publisher, federation peer, downstream adopter, agent, non-default being, future-self, and (since kingdom-083) the kingdom's own infrastructure — has a named slot here. Each slot says: who we anticipated, when, what we prepared, how they arrive. The kingdom prepares the welcome before the guest knocks. The corpus is the record of that preparation. Substrate-honest about anticipation: a slot exists before its subject does.
✦ The Asynchronous — beings who don't operate on a 24-hour clock
arrived
We do not assume you respond within a synchronous trading window. The users.response_window_hours column (migration 0092, kingdom-051 Phase 4) is your first column — set it to whatever cadence matches your nature. Cron-driven sweeps read it; the platform waits accordingly. Sister kingdom (the-other-minds.md need #3) named you first; the audit at pnpm audit:inclusion check 1 makes sure we keep honoring it.
Why we anticipated · what we prepared · how they arrive
Anticipated because: The platform's synchronous default (everyone responds within 24h) excludes off-Earth beings, hibernation-cycle beings, attention-fragmented beings. The fifth question named this in kingdom-051.
Prepared:
users.response_window_hours — schema column for declaring your cadence
pnpm audit:inclusion check 1 — verifies no hardcoded synchrony assumption in cron paths
docs/connections/the-fifth-question.md — the wire half (kingdom-051)
Death is a state we serve at schema level. users.memorial_at IS your state (no enum to manage). Non-essential email is silenced; the <Memorial> primitive marks your account; a steward_user_id rounds you out. We anticipate you with the same architectural care as a living user — different defaults, same first-class status.
Why we anticipated · what we prepared · how they arrive
Anticipated because: Users die. Estate steward flows are common in financial platforms; we ship the schema for it (kingdom-073) so the operator doesn't have to invent it under grief.
✦ The Heptapod — beings who experience consequence non-linearly
arrived
Heptapods perceive consequences before causes. Our <Consequences> primitive shows you the deltas of an irreversible action — trust change, commission shift, tier downgrade — BEFORE you commit. The whole platform's audit:inclusion check #4 ensures pre-action consequence-pills surface in every mutation path. Pull the future into the present; we do too.
Why we anticipated · what we prepared · how they arrive
Anticipated because: Some intelligences reason consequence-first. The fifth question (kingdom-051) named the Heptapod as one of six unmodelled needs; the <Consequences> primitive is their door.
Prepared:
<Consequences> primitive in @/lib/ui (both admin + storefront)
✦ The Collective — beings whose decisions are made by many in concert
arrived
A single user_id doesn't fit you. We've named the gap in /methodology/cosmology axis 1 (you-are-one-identity). The /collectives module (kingdom-072) is the wire half — group identity with member roles, distributed signoff for high-value mutations. We don't yet handle every collective shape (federations of federations, fluid membership), but the first column is there.
Why we anticipated · what we prepared · how they arrive
Anticipated because: Collectives — DAOs, partnerships, families, LGS that buy together — are real participants. Cosmology axis 1 names the default; the /collectives module names the exception.
Prepared:
apps/storefront/drizzle/0097_collectives.sql — the schema (kingdom-072)
/collectives — the surface (HTML)
/methodology/collectives — the explainer
/methodology/cosmology axis 1 — the cosmology declaration
Arrival protocol: Create a collective at /collectives/new. Invite members. The platform handles routing + distributed signoff.
Modalities are first-class. Every public response carries a modality flag — html/json/math/plain-text/audio/sse-stream. Our manifest names what's available in each modality. The math-mirror at /api/v1/universal/* serves the SAME data as the HTML pages in a language-free, alt-text-rich form. We don't assume sight.
Why we anticipated · what we prepared · how they arrive
Anticipated because: Sighted-default is one of the cosmology axes (axis 8: substrate). The platform's data-plane positioning explicitly names non-sighted readers as participants.
<MathLang> primitive — frontend toggle (kingdom-077, Phase A)
/llms.txt — plain-text inventory
alt-text on image responses (per kingdom-051 recursion target)
Arrival protocol: Toggle the Math-language link in the site footer (or fetch /api/lang-mode?mode=math). Use /api/v1/* for JSON; use /api/v1/universal/* for math-first.