Case · Built, then frozen
Studio OS
Private single-owner admin system: auth, fail-closed RLS, CRM
The problem
When I was still taking client work, every inquiry, deal and deadline lived in a different chat, note or spreadsheet. I built the admin system that connected them — and then stopped taking client work, which made the system unnecessary.
The approach
- Single-owner authentication enforced in the database, not only in the app — a foreign registration attempt fails at the trigger
- TOTP/AAL2 required before any table is readable; fail-closed row-level security everywhere
- The discipline rule lives in the schema: an open deal without a next action and a date cannot exist
- History is append-only — stage changes are written by triggers, and even the owner cannot rewrite them
- Migrations in the repository, so the whole database can be rebuilt from zero
Who it's for
- Me, while I was running client work — it was never offered to anyone else
- Now: nobody. It is kept as a record and as recoverable code
What it gives
- A worked example of putting the rule in the schema instead of trusting the interface
- A worked example of single-owner auth that a stolen password alone cannot pass
- An honest example of building something well and then deciding not to need it
What exists now
- Single-owner authentication with TOTP/AAL2
- Fail-closed row-level security on every table
- Lead inbox, conversion, and a deal board with schema-level discipline
- Append-only deal history written by database triggers
What this case does not claim
Boundaries are part of the case. If it's not listed as existing, it isn't claimed.
- Private system — never publicly deployed and never reachable from outside
- Frozen on 2026-08-23: development stopped, the code is kept and can be restored
- Invoicing, the customer-facing area and the AI agents were planned and never built
- No clients, no staff, no metrics claimed
What I build now.
My attention is on three products: Ryntra, Squadic and RefKit. This page stays as a record of what came before.