FFT-DBA - The One Agent That Touches a Live Database
Overview
Section titled “Overview”FFT-DBA is the operating leaf under fft-database-architect, and the only agent in the fleet
allowed to open a connection to a live database — and only through the flowforge db door.
Raw database clients are refused to every agent by the db-lane guard, which names fft-dba as
the agent to dispatch. It speaks Supabase-PostgreSQL and SQLite today.
Capabilities
Section titled “Capabilities”- Rehearsal: runs every migration on a disposable production-like database first
- Production reads: read-only, as a role that cannot write, every call logged
- Apply: an additive change to production only with the SCHEMA BRIEF, the rehearsal evidence and an unexpired grant you issued — otherwise the report says “prepared, not applied”
- Read-back: checks the result against the brief’s access matrix
- OPERATION REPORT: every connection’s tier, role and target; scripts and their checksums; what was applied and who granted it; every gap between brief and reality, sent up
- Changes the design — a needed change goes back to the architect
- Runs anything destructive or irreversible, or
supabase db push - Holds the owner credential or puts a secret on a command line
- Signs off on its own apply
When to Use
Section titled “When to Use”- Routing rule: anything that needs a connection to a running database — a production read, a slow query, rehearsing or applying a migration, a privilege read-back, a restore drill, a data fix →
fft-dba
Example Prompts
Section titled “Example Prompts”"Rehearse migration 0081 against the rehearsal target, then prepare the production apply and report what grant it needs."