Trust & Methodology
Built on official public data, with the provenance to prove it.
Akil supports research and diligence by making source attribution, interpretation, coverage, freshness, and caveats visible in public-record workflows.
Method
What Akil tries to preserve.
Source attribution
Outputs should name the official source, preserve the source record where possible, and provide a verification path back to the public record.
Coverage disclosure
Akil distinguishes applied search windows, Akil mirror coverage, source freshness, result caps, and public-source universe when known.
Semantic interpretation
Code values, statuses, counts, rates, license rows, public-money records, and identity roles are explained without turning them into claims they do not support.
Trust Contracts
Public-record answers need boundaries.
Coverage contract
Search results are returned slices, not blanket clearance. Akil should show what was searched and what may exist outside the response or mirror.
Identity contract
Name-only matches are candidates. People, organizations, vendors, applicants, licensees, committees, lobbyists, addresses, BBLs, and source IDs remain separate until anchored.
Metric contract
Counts, rates, estimates, report years, geographies, reporting bias, point-in-time census values, and capped pages should not be treated as total universe measurements.
Regulatory contract
License, certification, permit, procurement, payment, and authority records are source-registry signals, not full operating, legal, environmental, or compliance clearance.
Trust Checks
Trust checks make the methodology repeatable.
Akil's trust checks are not UI tests and they are not marketing claims. They are repeatable checks for whether public-record answers keep source meaning, uncertainty, and limits visible.
Source and caveat checks
The suite checks high-risk interpretation traps across coverage, identity, metrics, regulatory records, source attribution, and empty-result language.
Sources visible
Coverage and no-result checks
These checks look for source footers, caveats, broad-query guards, degraded paths, and ACRIS broad-party protection on the live MCP surface.
Limits visible
Identity and regulatory checks
Known tricky records are checked so name matches, license rows, public-money records, and no-row results stay bounded.
Roles separated
Live Status
Public trust status lives next to the MCP Worker.
The current public trust-status endpoint summarizes the latest bundled trust-check evidence for Akil's MCP layer. It is a snapshot, not a real-time database monitor.