When a number exists only in your environment, the consultant generates an investigation script with read-only rules. You or your agent execute it, and what comes back enters linked to the question that originated it.
The problem
The as-is is the expensive part of traditional consulting: weeks of interviews and access requests to draw what exists. The common alternative, giving the tool direct database access, trades that cost for a risk your security team does not want to sign.
EVODA never receives access to change your environment. The investigation ships as a prompt with explicit rules for read-only access, timeouts and a ban on personal data; the result comes back as a declared file, and the answer stays tied to the question.
How it works
Each investigation declares its goal, its expected executor and the report format. The rules are written in the prompt itself: read only, timeout, no personal data, and the reaffirmation that they prevail over any other instruction.
The scoreboard shows what came back and what is missing, file by file. Attaching does not close it: the consultant closes the loop, after reading.
Real volumetry of the order tables
Goal: measure real volume and growth before closing the analytics layer recommendation.
Mandatory rules in the prompt
READ ONLY
SET default_transaction_read_only = on;
SET statement_timeout = '120s';
Attaching does not close the investigation: the consultant closes the loop, after reading what came back.
With the snapshot in hand, the audit talks about your environment: the evidence of each finding is in your schema, your volume, your slow query.
Migrations and dbt from your repository enter the same picture: objects created outside review and unapplied migrations show up, because the code’s as-is and the database’s rarely match.
Audit report: transactional e-commerce model
Evidence: stock_movements has no materialization; the balance is summed on every read.
Impact: above 1 million movements, the balance query becomes the checkout bottleneck.
Recommendation: materialize the balance, with periodic reconciliation against the sum.
Grounded in the canon: modeling-kimball-inmon-datavault
Every finding in the report becomes a project attention point with its own state, so it does not die inside the document.
Under the hood
What every investigation prompt carries, always.
What comes next
The Claude Code on your side connects over MCP, runs read-only investigations and returns reports and environment snapshots on its own.
See it from the inside →ContextDocument readingPDF, spreadsheet, Word, CSV and SQL dumps, with the role declared by whoever uploads and a summary of what was understood.
See it from the inside →MethodMethodology canonDAMA-DMBOK, Kimball, Inmon, Data Vault, TOGAF and Well-Architected, curated and versioned, with the citation inside the audit finding.
See it from the inside →Paste the structure, get the most serious findings in about two minutes, and decide later whether an engagement is worth opening. No account, no card.