Check the caller, take the payment, keep the proof.
District Assurance is an open-source engine from Distronode for the teams who build automated phone lines that handle sensitive work.
It checks who is calling against your records, files what the caller confirms, texts a payment link to the number on file, and keeps an audit ledger where any change shows, with signed receipts. It can also let a verified caller in through a door.
Pre-alpha: read the code and try the demo, but do not put it in front of real callers.
One call, four steps
Verify
Keypad answers match your records, and the phone company's records for that number agree. Level 2.
File
A repair request, read back and confirmed.
Pay
A $150.00 deposit, paid by a texted link.
Prove
A signed receipt, chained into the ledger.
A signed receipt
- Verified
- Level 2, keypad answers and a phone company match
- Record
- Repair request, with its fingerprint
- Payment
- Paid
- Consent
- Repair texts: yes
- Ledger
- Its entry and hash
- Signature
- Valid
The model proposes, code decides
Only your code says yes
The AI on the call cannot pass a check or allow an action, and caller ID never counts as proof. Your own code calls the engine, and nothing protected happens until that code has verified the caller.
Compared, then thrown away
PINs and the answers on file are stored only as one-way fingerprints made with your own secret key. What the caller keys in is compared, then thrown away, and the ledger says what happened, never a value.
Never asks for a card number
Payment is by a hosted link texted to the number on file, and the engine refuses to file or log a card number. If a caller reads one out anyway, it spots the number so your code can stop the caller and remove it from the transcript.
Turn on only the parts you need
Each business turns on its own set. The ledger is always on.
| Part | What it does | Where it stands |
|---|---|---|
| Badge (verify) | Checks who is calling, more strictly for riskier tasks. It uses a mix of: a PIN, keypad answers checked against your records, spoken answers, a texted code, a callback to the number on file, a check with the phone company on that number, or a photo ID and selfie by texted link. | Built and tested with simulated services. Lockouts carry across calls. |
| Dossier (file) | Forms your business defines. The caller hears what will be filed and confirms it first. A sensitive value is never read aloud, and it is stored encrypted under your own key. | Built. |
| Paylink (pay) | A payment link texted to the number on file, for an amount your code sets and the caller hears and confirms, paid into the business's own Stripe account or into yours, as the platform. The engine never handles card numbers. | Built. Its Stripe Checkout adapter, in the example server, is proven in Stripe's test mode. Charging a saved card is not included. |
| Trace (prove) | A hash-chained audit ledger, always on, so any change to it shows. Optional signed receipts that the person holding one can check against your published keys, and consent records that keep the exact wording. | Built. The ledger keeps its entries in memory; durable storage is up to your own systems. |
| Gate (entry) | After verification, a signed permission to open a door, valid for a short time and sent once, or a one-time access code texted to the number on file. | Built, with adapters for Seam, Kisi and Verkada, tested against simulated servers, not yet against the vendors' own services. |
Where it stands
District Assurance is pre-alpha, and its API will change without notice. Each change is listed in its change log on GitHub.
No third party has certified or audited it. It has no PCI DSS attestation: whether a setup is in scope depends on its whole call path. It checks a caller against your own records, which is not regulated identity proofing.
Read it, try it and review it, but do not put it in front of real callers yet.
It does not answer calls, speak or host anything. Your voice agent and web backend do that, and call the engine from their own code.
Open, and tested in public
Apache-2.0
The whole engine is published under the Apache License 2.0, so you can read it, run it and build on it. The District Assurance and Distronode names are not part of the licence.
OpenSSF Best Practices
The project holds the OpenSSF Best Practices passing badge, and its documents set out the design, the threats and the decisions.
Tested on every change
Every pull request runs the full suite at 100% coverage of every engine source file, on Linux, macOS and Windows.
Try it on your machine
A scripted demo runs four calls end to end with simulated services, in a terminal or a browser, and nothing goes out from your machine.
A Distronode project of its own
District Assurance is an open-source engine from Distronode, built as a project of its own, with its own code, roadmap and documents.
The code, the specification, the security model and the decisions behind it are on GitHub, for anyone to read and question.
Stripe, Seam, Kisi and Verkada are named only to say what the code works with; Distronode is not affiliated with them.

