Customer dashboard

Functional specifications for the Customer dashboard. The customer-facing dashboard (apps/dashboard). Each page is generated from a natural-language spec under qa/customer/specs/ and carries its latest replay-run status.

• Auth Gating — The customer dashboard is gated to authenticated customer-org members.
• Coldstart Empty — The onboarding flow’s two cold-start empty states render cleanly, never as errors:
• Dashboard Reads — The customer dashboard presents the deployed world model and its decisions.
• Decide Round Trip — POST /decide is the customer decision surface — the executable payoff of the whole loop.
• Domain Create — On the onboarding first-workspace step, the customer names a workspace and chooses a published world from the picker, then creates the workspace (`POST /orgs…
• Org Llm Config — An org admin configures their organization’s bring-your-own World-Agent LLM from the dashboard’s Organization model surface: an org-level (not domain…
• Portfolio — The All-workspaces portfolio is the customer’s landing at / when no domain is selected (gate semantics: memberships-without-a-selection land here, never fo…
• Signup — A brand-new customer (an authenticated GoTrue user with no organization yet) reaches the signup/onboarding surface at /auth/onboard — NOT the forbidden scr…
• States — Each customer dashboard read should communicate its loading, empty, and error states rather than rendering blank or broken.
• World Model Card — The Ruleset Card (design 03 surface F) is the version-scoped methodology disclosure of the ruleset governing a domain — the per-version, immutable record o…