evening a table that was built crooked

a consultation operating system for the side that had one part-time coordinator against a full regulatory department

Two parties sit down for a regulatory consultation. One brings a legal team, regulatory affairs staff, and purpose-built tracking software. The other brings a part-time coordinator managing a dozen files at once, a two-thousand-page impact statement nobody has time to read, and a record of past promises kept in a notebook and an email chain.

Built the system for the side that never had one.

what it does

It watches the official project registries around the clock. The moment a new filing touches the client’s area of interest, an alert goes out by text and email, while the comment window is still open and there is still time to respond.

Then it reads. AI agents deconstruct each filing the way a team of analysts would, pulling out every commitment, mitigation, deadline, and threshold the proponent put on paper. Each extracted fact carries its exact source: the document, the page, the quote itself. A plain-language brief comes out the other end, built for the people who have to govern the decision.

the accountability ledger

This is the part that makes the rest matter. Every promise a proponent makes goes into a tamper-proof ledger, with the source document, the page, the exact quote, and the moment it was extracted. Each commitment moves through a lifecycle: extracted, confirmed, monitored, evidenced, then verified or breached. Every entry is chained to the one before it, so the record cannot be quietly edited after the fact.

A promise made in a consultation room used to evaporate the moment the room emptied. Now it has a deadline and a paper trail.

why you can trust it

The system splits pulling facts out from interpreting them. The factual extraction gets reviewed on its own, before any narrative sits on top of it, so an error in reading cannot smuggle itself into the analysis. My client reviews and corrects every extracted fact before it counts as authoritative.

At any point the system produces a complete bundle: the structured data, the source PDFs, the verification trail, a timeline of every event. A third party can check the whole thing without trusting the server. That is the record that goes to legal counsel or a regulator.

It organizes and it explains. The people make the call. It never makes the call for them.

who owns it

The client owns everything the system produces. Their instance runs on infrastructure they control, isolated from everyone else’s, with its own keys and its own backups. There is no administrative backdoor. The only thing that ever crosses their walls is the public filing the model reads. Their boundaries, their records, their decisions stay home.

why it matters

The asymmetry was never about intelligence or effort. It was about infrastructure. One side had departments and software; the other had goodwill and a shared drive. Give the under-resourced side the same analytical capacity and the table levels itself.

Wherever a smaller party has to hold a larger, better-resourced one to its word, the same engine catches the promises, keeps them, and proves what was said.