Security
Discretion here is not a policy commitment. It is how the system is built.
6.1
Approval is a property of the database. The content state machine is a single guarded function; a decision requires the exact latest draft, the right person, the right role. Illegal transitions don’t get logged and forgiven — they raise errors. The AI side can propose; it cannot decide, and it cannot publish.
FIG. 02 — APPROVAL IS A PROPERTY OF THE DATABASE.
6.2
Your drafts are visible to you alone, enforced at the row level of the database.
FIG. 06 — YOUR VOICE PROFILE CONDITIONS YOUR DRAFTS AND NOTHING ELSE.
6.3
Every action is on the record: an append-only, hash-chained audit log of every transition and every decision, by authenticated actor.
FIG. 07 — EVERY ACTION IS ON THE RECORD.
6.4
Your data leaves whole or not at all. Full export — a deterministic archive with cryptographic evidence — and full deletion, with erasure certificates, are built machinery, not promises. GDPR as working parts.
6.5
Your voice profile is yours alone: it conditions your drafts and nothing else, is never pooled, and is deleted with you.
6.6
We run our own infrastructure. Isolated database stack, own worker fleet, private research systems, independent monitoring. Your data does not live inside someone else’s multi-tenant product.
6.7
This site installs zero third-party trackers. Not minimized — zero. First-party only.
FIG. 12 — THIS CHART IS COMPLETE.
6.8
We publish our control architecture here in place of badges we have not yet earned. When third-party certification completes, this sentence will change — and not before.