A sovereign mobile operating system. Every interaction is a record. Every record has two sides. Every record must balance. Built on AOSP, governed by Outstack, secured by Telux, encoded by BitPads — ZAKO is sovereignty as an engineering discipline, not a marketing claim.
A payment, a task, a blood pressure reading, a capability grant, a power mode transition, a journal entry — each is a BitPads frame, signed by the Island Sovereign, chain-hashed against the record before it. Records are never deleted. They are amended.
ledger · append-only · chain-hashedEvery record involving a quantity — money, energy, data, time — is a BitLedger record. The conservation invariant is enforced at encoding. A batch that does not balance cannot be correctly formed. Not a rule. A structural property.
BitLedger · invariant · structuralYour records are not stored on external servers. Your identity is not issued by a third party. Your data does not leave your device without an explicit sovereign action. ed25519 keys in TrustZone. W3C DIDs. Island containers. Capability grants.
Telux · DIDs · Islands · sovereignZAKO functions fully without network connectivity. Records are created locally, stored locally, transmitted when the Sovereign chooses. SMS, QR code, Bluetooth LE, IP. No service requires a network connection to create or read records.
SMS · QR · BLE · no network requiredA device that cannot control its own power consumption cannot guarantee its own availability. Power events are records. Power mode transitions are records. The power budget is a ledger. Outstack governs everything through power.
Outstack · 5 modes · RTG disciplineGMS removal is not a compromise. It is the founding design decision. Push via UnifiedPush. Apps via F-Droid. Maps via OpenStreetMap. Auth via Telux DID. Every replacement must be more sovereign, not merely different.
no GMS · F-Droid · UnifiedPushThe standard is normative. The protocols are open. The reference hardware is a $99 flip phone. The architecture runs from Lusaka to Mars.