Full Circle The Outcomes Ledger

One page, for the people who will build the vault

Print this and take it to the meeting. It states the requirement in the vocabulary an encryption team already uses, so the conversation starts on the same page.

Ally — here for you

Which state spends the most on education?GeorgiaCompare Texas and CaliforniaHighest federal shareChild welfare in OhioBills in WyomingLowest money out

What we are building

An audit of the child-welfare system that follows real children's outcomes across every state and every agency, for their whole lives, while making it cryptographically impossible for auditors, researchers or the public to identify any child.

Core requirement — one person, one permanent token, everywhere; never reversible by the people using the data.

RequirementSpecification
TokenisationDeterministic, keyed — HMAC-SHA-256 or format-preserving encryption (NIST FF3-1). Keys live only in HSMs (FIPS 140-3 Level 3). Same person → same token, in every state and dataset.
Cross-dataset matchingPrivacy-preserving record linkage (Bloom-filter encoding / secure multiparty computation) so messy records match without names in the clear.
The vaultThe identity↔token crosswalk, encrypted at rest, isolated from the audit environment, processed only inside confidential-computing enclaves, append-only.
Threshold accessVault key split via Shamir's Secret Sharing; a quorum (e.g. 4 of 7 independent holders) required to open. No individual can re-identify. Routine auditing never opens the vault.
Break-glassRe-identification only via trusted broker + quorum + documented legal cause + permanent logging. Sole purpose: protecting a child in present danger.
Audit logAppend-only, tamper-evident (hash chain / Merkle tree on WORM storage), independently anchored so history cannot be rewritten. Every touch recorded, permanently. Explicitly stronger than mutable medical-record systems.
On demandThe engine tokenises new and updated cases continuously as they arrive.

The design test to hold us to

If evidence enters this system, it must be impossible for anyone — including the operators — to make it quietly disappear.

A working demonstration of all three mechanisms is on this site → Ask the team to break it.

Programs to build on and cite

These are established, verifiable programs. Citing and extending them frames this as reform of things that already exist, not a leap into the unknown.