Skip to content
proc 01 · Trust readout

Security

Not a badge wall. A readout.

Six controls, each with its enforcement point. The same honesty the product practices: claims grounded in how the system is actually constructed — never invention.

C-01enforcing

Owner-scoped by construction

Every company, build, dossier, and prediction row carries its owner. Row-level security is enabled on every table — isolation is the schema's default, not a filter someone remembered to add.

database · RLS on all tables

C-02enforcing

Keys never reach the browser

AI provider keys and service credentials live server-side only. Diagnostics report counts and routing — never key material.

server · key resolution layer

C-03enforcing

Every decision on the record

Builds keep an append-only flight record — decisions, alternatives, scores. Founders audit any choice with a question; the organization answers from the record or says it can't.

pipeline · flight recorder

C-04enforcing

Approval before consequence

Blueprints wait at a founder gate before engineering. Spend is quoted in money and time before any run. Nothing irreversible happens silently.

workflow · approval gates

C-05enforcing

Bounded autonomy

Autonomous work runs inside budgets, leases, and per-stage checkpoints. A runaway process hits a wall, not your bill.

runtime · budgets & leases

C-06enforcing

Yours to take

Code, brand, content, and data are exportable. Leaving is a download, not a negotiation.

platform · export

Enterprise deployments add private cloud, private models, and your governance on top — see Enterprise.

commission · ready

Build on a system that shows its work.

Every decision on the record. Every boundary enforced by construction.