Compliance Ledger
in buildA data layer for compliance numbers that defend themselves. Every value links to its source URL, verbatim quote, and the human who signed it.
Try the live tool
The demo lives at its own home now: compliance.kelmen.space. Pick which side of a money exchange you're on, your relationship, your state — see exactly which taxes apply and what to do about them at tax day, every number traceable to a public source.
The thesis
Compliance software treats numbers as outputs. The Compliance Ledger treats them as witnesses. Every value rendered carries a chain back to a verified source — URL, verbatim quote, SHA-256 hash, signed by a named human, anchored daily in an offline-verifiable merkle root.
The result: an auditor opening a six-month-old filing can verify any line item without contacting anyone. The same data is also queryable as a public read API — so any tool, agent, or human can consume it without trusting the rendering layer.
Who it's for
Anyone whose work depends on a number being correct months after the fact.
- Freelancers, contractors, and household employers who want decision-quality tax math before they spend a check or sit down with a CPA.
- Auditors and accountants who want every line item to come with its source, without phone calls or PDF hunts.
- Compliance teams shipping products into regulated industries who need a paper trail per claim.
How the proof works
The ledger refuses to render a number unless every input fact has a live source URL, a hash that still matches what was on the page when a person verified it, and a signature on file. The "verification ritual" is intentional friction — typing the first five words of a quote, by hand, by an authorized human. The system never silently elevates an unverified claim. When a source page changes, every fact that cited it pauses until someone re-verifies.
What's verified today
One state, one relationship: Illinois household-employee state withholding. End-to-end verified — sourced from the Illinois Department of Revenue, byte-hashed, signed. The live tool labels every other line as "blueprint" until its source has been ritualized; the math is right, the citation URL is real, but the verbatim quote isn't claimed yet. Each will flip to verified as the ritual is run on its source.
Architecture
Postgres on Supabase. Period-lock triggers and row-level security. SHA-256 source hashing. secp256k1 signatures per verifier. Daily merkle anchor for offline auditability. Cron-driven drift detection. Public REST API via PostgREST. Static frontend on Cloudflare Pages.
Read it programmatically
Every endpoint behind the demo is publicly callable. See the API reference — curl examples for listing calculations, walking lineage chains, and verifying a fact's source hash yourself.