SlowCompass Studio

The operator foundation is merged and its security gates are proven. Setting up a workspace is built and works: an account, a few questions about how you work, and a workspace with its first place and a draft class. Joining one from an invitation link works too. Everything else above the foundation is still a shell — the console’s own screens are placeholders that each name the phase which builds them, and no operator surface does its job yet.

Closed and proven in the foundation

Workspace membership and role authorization, mirrored in row-level policies
Public reads through a published projection that excludes address, contact and payment state
Guest capability tokens — signed, purpose-scoped and short-lived — replacing order-ID QR access
Atomic capacity reservation, proven against two measurably overlapping sessions
Scheduler authorization that fails closed when unconfigured or weakly configured

Still gated, and gated deliberately

Real users and client data — an invited private test is running; accounts are created by invitation only, and no client data is loaded
Email delivery — security gate 5 is open until consent evidence, application configuration, delivery logging and retry exist
Payments — Stripe Connect is a later milestone; payment surfaces read existing structures only
Public demonstration — not approved; the deployed application is noindex and nobody can create an account on it

Occurrence sources recognised by the shared domain: studio · host_agenda · editorial_manual · external_link