Regulated agriculture
Read-only AI analytics over a 361-table legacy compliance database
Live, read-only questions against a licensed operator's on-site compliance database, plus a reconciliation against the books.

01 / Problem
What wasn't working.
Compliance data lived in an old on-site PostgreSQL server with no reporting. The owner wanted answers without risking the system the state audits.
02 / Approach
What I built.
- 01
A dedicated read-only database role over a private encrypted network. Nothing can write.
- 02
The database registered as an MCP server so Claude can query it live. A schema catalog explains what the 361 tables mean; about 40 hold data.
- 03
An hourly sync worker on the store PC feeds an owner dashboard. 18 registered queries, 16 rules, no personal data shown.
- 04
A books module reconciles accounting entries against tracking data.


03 / Architecture
How the pieces connect.
04 / Result
tables mapped in a legacy compliance database, read-only. The owner asks questions in plain language and gets live answers. 27 of 38 wholesale entries matched the books exactly on the first pass.
Read-only role
The safest way to get value from a system you cannot risk.
Live queries
MCP connection, answers from current data.
Rulebook
16 rules on what the assistant may say. No personal data.
Books check
Accounting matched against tracking records.
Have a problem like this one?
Book a call