DiligenceOS
The due-diligence agent you call before a transaction, a hire or a contract. It takes a subject and a transaction and returns one verdict: proceed, hold or red flag.
Status: pre-alpha. It runs on a bundled sample dataset, not on real registries or sanctions data, and it is not for real compliance decisions.
Watch a verdict get made.
A short tour: a supplier and a contract, four checks, a held payment that is released once the contract is fixed, a sanctions match, and what happens when someone tampers with a receipt. The names and the data are fictional.
Prototype running on a bundled sample dataset. The names, the sanctions list and the registry are fictional. The verdicts, trust scores, receipts and checks shown are real outputs of the current code. The release gate is the project’s demo gate, not a real payment rail.
Read the steps as text
- Before you pay or sign, ask. All names here are fictional.
- One verdict: HOLD. The payment stays held.
- Add the missing clause: PROCEED, and the payment is released.
- A sanctions match is always a red flag.
- Edit a signed receipt and the check catches it.
Check before you act.
A person doing diligence by hand and an agent about to make a payment, sign something or send an offer need the same thing: an answer built from evidence they can check, not from what the other party says about itself.
DiligenceOS is meant to be called both ways. An agent can gate its own next action on the verdict.
One verdict
Proceed, hold or red flag. A sanctions match always comes back as a red flag. Any other flag is a hold.
Four checks
Sanctions and watchlist screening, identity and registry lookup, a counterparty’s delivery record, and a scan of contract text for required clauses. The scan checks that the wording is present, not whether the clauses are good.
Evidence you can check
Results are signed and go into an append-only log, and an independent witness can detect if history is rewritten. The service describes itself in a signed manifest, so a caller can verify it without trusting the server.
Authority that only narrows
An agent acts under a credential that can be passed on but only made narrower: a smaller amount, fewer permissions.
Pre-alpha. Not for real decisions yet.
- Built
- A first working loop: the four checks, verdict assembly, a command line and a local web front end, signed receipts, narrowing delegation and a witnessed log.
- Data
- A bundled sample dataset. Not real registries or sanctions data.
- Not ready
- Nothing here is production-ready or licensed for real compliance decisions.
- As of
- 2026-10-09, from the project’s own documents