________________________________________________________________________
You are welcome to refer to our Open Source Repository at
“https://bitbucket.org/itotcca/the-situation”
Tx-Rails is a General-Purpose, Ultra-Secure Backend, protecting Databases with sophisticated Middleware, being developed with GO, Kubernetes (Juju / Charmed Kubernetes, with LXD for the audit tiers), and Bash scripting, on Ubuntu Linux 24.04. We add the Kademlia DHT Network with Absence of DNS (ADNS), full end-to-end IN-TRANSIT encryption (TLS 1.3, measured on the live gateways), and client-side AT-REST encryption that is built but switched on nowhere — no field is sealed in any running deployment today. The Middleware has been designed to provide for the highest level of Security, as demanded by Financial Institutions, Medical Services Providers and now, generally. The repository demonstrates that, rather than merely claiming it, designed for three (but unlimited in reality) very different member networks running on the same code. You need Data Security in these times of modern-day Storms that are always brewing, like intense low pressure systems; the Minder is brewing in a parallel but opposing way, like calming high pressure systems.
Where this stands today, stated here rather than left to be discovered. Four connection modes exist and all four commit in our own development estate. Mode A — a hash per transaction, with no content reaching us — is the only mode we offer for onboarding, and no customer has been onboarded through any mode. Modes B, C and D are reference implementations. Nothing below is a claim about a production deployment, because there is not one.
| Level | What it is | What it means in national health / a banking jurisdiction / a social housing federation |
|---|---|---|
| 5 — the edge | Stateless. Authorises locally against a signed envelope and reconciles afterwards. | A ward scanner, a theatre, a loading dock, an ambulance; branches, agencies, ATMs, kiosks, point-of-sale, employees. Disconnected operation is normal in regional operations, not exceptional. A terminal forges a CLAIM, never a FACT. |
| 4 — the Executive mesh | MEMBER-OWNED. A consensus tier in its own right: own validators, own quorum, own paired auditor. | A banking jurisdiction can run one, and a health district plausibly runs one — with the district itself, facility, service line and campus as tenancy SCOPES CARRIED BY that mesh. A social housing network could run one. A single rural pharmacy, or a local joinery, never will. |
| 3 — the member’s own node | MEMBER-OWNED. The member’s own validators, run by the member. | Member capability varies enormously — in EVERY domain, not only in health. A health district runs a real cluster; a community pharmacy or single-handed practice runs nothing and reaches the network through a shared gateway. A large social housing provider runs a real cluster; a one-person joinery does not. In both cases the two ends are members of the same sector. Levels 3, 4 and 5 shrinking to nothing for a small member without excluding it is a property of the level model, not a finding about health. |
| 2 — gov-reg and gov-comm | SHARED. What may cross BETWEEN SECTORS, under which regime, and the record that it did. Belongs to NEITHER side of a trade. | Not usable yet — deployed and committing, but its gates are unarmed and no regime rules are defined. Biomedical, cold-chain, sterile-processing. Crossing into health from a manufacturer, a logistics operator or a supplier lives here. The regime rules it is waiting on are an agreement between the two SECTORS that trade and their regulators — not between States and Territories. Movement between health districts does NOT — re-keyed 30 September 2026: a district is a tenancy inside national health, so an inter-district transfer or a statewide recall is an ordinary level 3/4 transaction, and Mode A covers it. |
| 1 — the registry | SHARED. Who is a member, in which federation, with what standing. Keyed by whatever makes members LIKE one another — a banking jurisdiction, a trade or profession, or the national health sector. | The least foreign part of the model, because the register already exists and already has an owner: a banking supervisor, a trade or professional body, and in health the national bodies — AHPRA for practitioner registration, the TGA for therapeutic goods and device recall, the ACSQHC for facility standards. Those owners being national is why health keys this level nationally rather than by district. And this level is deployed: the national registry runs at n=4 and is committing blocks. |
| 0 — cross-border | SHARED. A protocol plane, not a deployment. No nodes run here. | Imported devices and consumables — a real and regulated path, and the least pressing of the three shared levels. Designed rather than built. |
What changed on 30 September 2026, and why it is here rather than in a footnote. Health used to key Level 1 by DISTRICT. That made every inter-district referral, transfer, consignment movement and recall a CROSS-FEDERATION transaction — which needs Level 2, which is deployed but not usable — so the routine case became the case the platform could not serve. It also contradicted its own justification: the registers cited to show Level 1 was easy in health are national ones. National health is now the federation and a district is a tenancy inside it. The cost is real and is not hidden: one national membership register means a State no longer admits members in its own district unilaterally, which is a political question rather than a technical one. It does not, however, gate a sale. Nothing we price touches level 1 or level 2 — what is sold is levels 3, 4 and 5, and one member buys and runs those alone, waiting on no federation forming and no agreement between jurisdictions. Nor does level 1 ask for a NEW agreement when it does come: it keys on registers that already exist and already have one national owner — AHPRA, the TGA, the ACSQHC in health; a supervisor or a trade body elsewhere. We do not operate a new register that a State must admit members into.
The numbering says where a level SITS, not what depends on what. Levels 3, 4 and 5 do not rest on 0, 1 and 2.
Levels 0, 1 and 2 are shared and operated by no single member — but they are NOT equally unbuilt, and saying “not yet built out” of all three understated what runs. Level 1 is deployed — the national registry, n=4, committing blocks. Level 2 is NOT USABLE YET — deployed and committing, but its gates are unarmed and no regime rules are defined. Level 0 is designed rather than built. A statement about delivery, never about importance.
Tx-Rails — Built by IT/OT Chain & Cloud Australia (ITOTCCA). Sydney · London.