The network view
A county funds a programme to reach businesses and residents it is not otherwise reaching. Two years later, proving it worked means asking people to remember. This records it when it happens instead — once, permanently, visible to both sides.
What a county uses it for
A small business is brought into county procurement by a chamber, a CDC or a district office. That introduction is recorded once. Three years and four contracts later the record still says who opened the door — which is how a county proves its supplier-diversity programme reached the businesses it was funded to reach.
Who opened the door stays on the record.
A resident completes a county-funded programme and is placed. The placement, the provider and the outcome are one attributed chain. 'Did this work' is answered from records, not from a survey of people who are hard to reach a year later.
Outcomes stay attached to the programme that produced them.
A permit issued by a G-code lands in the resident's own wallet as a credential they hold. They prove it to a bank, an insurer or an inspector without the county being asked each time, and without surrendering the rest of their record.
The resident holds the credential, not a copy of it.
Every disbursement emits a receipt into a chain anyone can replay. An Open Checkbook stops being a quarterly PDF and becomes a thing a journalist, a commissioner or a resident can verify at any hour without asking permission.
The checkbook is verifiable, not published.
Who is on the network
Holds their own identifier, their credentials and the receipts of every interaction. Grants access deliberately and temporarily. Private keys stay on the device — there is no escrow for anyone to compel.
Evaluates eligibility against its own published rules, issues the credential, emits the receipt. Authoritative for the service it represents and for nothing else, so a compromise of one is not a compromise of the county.
A chamber, a CDC, a district office or a community organisation that brought a business or a resident into a programme. Recorded once, permanently, visible to both sides. Whether any payment attaches is a question the county answers in its own procurement terms.
Replays the chain and checks that the arithmetic holds. Needs no login and no relationship with the county to do it — the only version of transparency that survives a change of administration.
Worked example
Invented parties. Each step names the receipt event the sandbox actually writes — run it yourself on /app.
| Step | What happens | Receipt written |
|---|---|---|
| 01 Introduction recorded | A district office brings a contractor into the vendor programme. Written when it happens, not when someone disputes it later. | network.attribution.recorded |
| 02 Credential issued | The procurement G-code issues a vendor credential into the contractor's own wallet. Non-transferable, anchored to their identifier. | credential.issued |
| 03 Fact presented | A bank asks whether the credential is active. The contractor signs the bank's nonce; the bank learns that one fact and nothing else. | credential.presented |
| 04 Disbursement settles | A contract is awarded and paid. The receipt commits to the one before it, so the record cannot be edited, reordered or quietly removed. | credential.issued (payee) |
| 05 Years later, still attributed | The same contractor wins a fourth award under a different department. The ledger still knows who opened the door, because nobody had to remember. | network.attribution.recorded |
Check it yourself
What those links are, exactly. The first is this sandbox. The other two are the live commercial engine, running today, holding no county data. They are here so the mechanism can be checked before anyone is asked to believe a description of it.