What this page does
The Sovereignty Stack
The Sovereignty Stack is the technical answer to a political problem: people will not trust a Cyber-Republic if it feels like a surveillance upgrade.
This page explains why local-first, privacy-by-design systems matter before democracy gets more digital, and why public assets need public memory.
Fractal governance
L0 individual/home vaultsYour Aura, living memoir, home data, sensor data and civic preferences stay local-first, encrypted, revocable and under your control inside the private node.
L1 neighbourhood meshPeople can share narrow, consented signals with nearby peers: blocked drains, heat stress, soil moisture, food surplus, disaster needs.
L2 public-asset layerRegions can track roads, energy, water, minerals, ports, insurance pools and community wealth funds without exposing private household data.
L3 national sensorium
Public insight without public exposure.
The national layer should not be a giant database of everyone. It should be a privacy-preserving simulation layer: aggregated civic signals, legal constraints, infrastructure models and climate-risk maps that help Australia plan without turning citizens into raw material.
DIDs and verifiable credentialsPeople prove a condition is true, such as membership, residency or contribution, without handing over every underlying detail.
CRDT resilienceLocal nodes can keep working offline during disaster, then merge updates later without needing one fragile central server.
Federated learningModels can learn from patterns across many nodes while private source data remains local wherever possible.
Human checkpointsAI agents wait for accountable human approval before sensitive civic actions, simulations or data releases move forward.
Adaptive sovereignty
I own my personal data. We govern our collective data. That is the privacy principle underneath the stack. Self-sovereign identity protects the individual at L0. Indigenous Data Sovereignty protects collective cultural, land, health and heritage data at L2/L3. An individual node should not be able to leak data marked collective without a verifiable approval from the relevant Nation or governance body.
Public asset memory
The first national use case is not futuristic. It is boring on purpose: a public register of long leases, toll roads, public-private contracts, asset sales, renegotiation windows and community benefit tests. Australia should know when a public asset is serving the public, when a deal has outlived its purpose, and what lawful options exist before the next generation is locked in.
Local government use case
For councils, the stack turns static asset registers into living, consent-based digital twins. Residents can report conditions and contribute useful local knowledge; councils receive trustworthy summaries for roads, drains, parks, libraries, heat risk, disaster kiosks and community services; privacy guardrails stop civic participation becoming surveillance.
Musicverse consent layer
A Protopian Gambit belongs here as a consent signal, not a slogan: no body as barcode, no citizen as feedstock, no digital twin without permission, context and an off switch.
Privacy compass
Every civic data question should pass four tests: what stays with the person, what can be shared locally, what must be governed collectively, and what the national simulator is never allowed to know.
Connected project: Aura Direct Hardware
A project exploring local compute and digital sovereignty, connected with community control of infrastructure.
Australian hosting is only one question
Ask who operates the service, which jurisdictions apply, who controls encryption keys, what purpose is allowed, how long data and backups remain, which subcontractors can access them, and how deletion, export and exit work. OAIC’s APP 8 guidance describes cross-border obligations and exceptions; geography alone does not answer them.
Keep sensitive work on-deviceReduce external disclosure, with limits on capacity and a need for safe backups and recovery.
Use a community or institutional nodeShare serious capability and local skills, while funding administration, access control and independent oversight.
Choose an accountable external serviceGain scale and specialist operations, with enforceable purpose limits, subcontractor visibility and a tested exit plan.
First Nations collective authority must be addressed alongside individual privacy. NIAA’s Framework for Governance of Indigenous Data and Ready S.E.T.’s separate permission operations offer practical questions for a local agreement. Ask a school, council or health provider to publish a plain-language custody and exit sheet; do not put private records in a public submission.
