Run the test suites yourself
Every shipped property carries its own suite. You clone, you install, you run. Counts and coverage are whatever your terminal says — not what this site says.
Diligence
Examine everything.
This page is written for the person whose job is to find the weakness: an acquirer's technical diligence lead, an enterprise buyer's security team, an underwriter. Here is the honest state of every property — and how to check it without trusting us.
The maturity ledger
Every property, its real status.
Live means serving production traffic. Shipped means built and tested, in internal use. Dry-run and prototype mean exactly that. We'd rather you find this table boring than find it wrong.
Exhibit CMaturity Ledger · 15 properties, folio 01–15
| No. | Property | Layer | Status | Evidence on request |
|---|---|---|---|---|
| 01 | pandect api | Rules | Live | 679 rules in production at pandectai.com; per-rule citations and trails |
| 02 | aletheia | Outcomes | Live | Hash-chain verifier output; live at aletheia-ledger.vercel.app |
| 03 | rule-assurance | Rules | Shipped | Audit pipeline v1.1.3; 88 tests; 418-rule wave with committed trails |
| 04 | rulecore engine | Decisions | Shipped | Deterministic core; typed AI boundary; golden replay pins |
| 05 | rulecore verticals ×7 | Decisions | Dry-run | Full pipelines on draft packs; no live effects until attestation |
| 06 | touchstone | Claims | Shipped | claim-batch@0 open spec; conformance suite; sealed-evidence runner |
| 07 | groundwork | Claims | Shipped | Zero-dependency grounding library; deterministic, no LLM in loop |
| 08 | claimcheck | Claims | Shipped · MIT | Docs-vs-code drift scanner; dogfoods itself |
| 09 | agent-exchange | Attestation | Shipped | 12 packages; Merkle transparency log; TS↔Python signature parity tests |
| 10 | proof-layer | Attestation | Prototype | Signed media manifests; gaps (identity binding, trusted time) self-documented |
| 11 | wherefore | Intent | Shipped | Global CLI in daily use; git-native trailers + notes; fleet search |
| 12 | countersign | Applications | In validation | Attorney-countersigned drafting rails; gated on partner attorneys signed, on the record |
| 13 | gatepass | Applications | In validation | Evidence layer for insurer/conformity gates; gated on written signal from a named underwriter, 30 days |
| 14 | rule-pack foundry | Applications | In validation | Attested rule packs as OEM substrate; gated on signed LOI per vertical, 60 days |
| 15 | proving ground | Applications | Instrumenting now | Public falsifiable self-ledger; built on aletheia + touchstone receipts |
Repositories are private. Under NDA, diligence gets read access to source, test suites, audit trails, and live systems — not a slide deck about them.
The protocol
How to verify us without trusting us.
A diligence process on a verification company should itself be verifiable. Here is the four-step protocol we hand every serious counterparty.
step 1
step 2
Verify a ledger offline
Take an aletheia export or an agent-exchange receipt and check it on your own machine: hash chain, signatures, Merkle paths. No API access to us required.
step 3
Replay a decision
Pick any RuleCore decision from the audit trail and rerun it from its pinned rule version and inputs. Determinism means you get the identical output, byte for byte — or you've found a bug we want to know about.
step 4
Spot-check the rule corpus
Sample rules from the Pandect corpus and check the quoted text against the controlling source yourself. The verbatim anchors make this a mechanical comparison, not a judgment call.
"If any step above fails, we want the failure in writing. A verification portfolio that fears verification is a contradiction."
Known limits
What we will tell you before you find it.
The machine ceiling is real
Automated rule audit ends at "needs review." Rules requiring attorney attestation are gated on exactly that, and the corpus displays the difference. We don't count attested rules we don't have.
Dry-run means not live
The seven RuleCore verticals execute full pipelines against draft rule packs. Revenue-bearing, live-effect deployment is gated behind pack attestation and named-counterparty commitments.
Prototype means prototype
proof-layer's current gaps — identity binding and trusted timestamps — are documented in its own repository. The remedies exist in agent-exchange; the integration is roadmap, not reality.
Engagements
Working with Isonomai.
Three shapes, one constant: you examine the evidence before anything is proposed.
- Integration. The stack — or a single layer — wired into your systems: rule corpora behind your product, decision engines under your workflow, ledgers under your claims.
- Licensing. Attested rule packs and verification instruments as OEM substrate inside your platform, under your brand.
- Acquisition diligence. Full-portfolio or per-property examination, structured as read access plus working sessions — the maturity ledger above is the table of contents.
Terms, stated plainly
Retained engagements begin at $50,000 per month. The dossier and a working session come first — no engagement is proposed until you've examined the evidence and we've examined the fit.
Response within two business days. If we're not the right instrument, we'll say so and point you at what is.
Contact
Request the dossier.
One email. Tell us who you are and what you're evaluating — integration, licensing, or acquisition — and the dossier comes back with the receipts attached.
NDA available on request · repositories open to diligence under NDA