Four tiers, not nine silos
The nine systems are arranged in four tiers. Intake and sensing gather signal. Understanding turns signal into assessment. Action commits resources against that assessment. Assurance — security, accountability and integration — applies across all three rather than following them.
This matters for procurement as much as engineering: an agency can adopt the platform tier by tier, starting with intake and understanding while continuing to run its existing allocation processes.
Data and proof are kept apart
Personal, clinical and household data lives in governed storage subject to residency, retention and access controls. What goes to the distributed ledger is verification material: hashes, custody events, consent transitions and access anchors.
The separation is not a technical convenience. Writing a vulnerable person's circumstances to an immutable shared ledger would create a permanent record that no consent withdrawal could ever undo.
Names, identifiers, clinical detail, household composition, location history. The ledger proves a record has not been altered; it is not a copy of the record.
Technology stack
| Layer | Approach |
|---|---|
| Blockchain platform | Selected per deployment from Ethereum, Hyperledger Fabric or Corda according to scalability, consensus and governance requirements. |
| Smart contracts | Automate and enforce consent management, access control and transaction validation. |
| Decentralised storage | IPFS or Storj for large-volume data requiring redundancy and integrity without central dependency. |
| Ledger interface | Web3.js for JavaScript services and Web3.py for Python services. |
| Frontend | React.js or Angular.js, built for responsive use across desktop, tablet and low-cost field devices. |
| Backend | Node.js, Django or Flask handling application logic, data management and ledger interaction. |
| Database | PostgreSQL, MongoDB or CouchDB for non-ledger data, complex query and analytics. |
| APIs and microservices | Service architecture with published interfaces enabling exchange with EHRs, LIS and emergency response systems. |
| Cloud infrastructure | AWS, Azure or GCP, with data residency configured per jurisdiction. |
| Security | Encryption, authentication, access control and audit applied at every layer rather than at the perimeter. |
Read the interoperability approach
Adoption depends on fitting into estates that agencies already run. That is an architecture question before it is a commercial one.