The ALLiw SystemThe System
What is this system?
What this system is, what its name means, and the standard it holds itself to. This is the record the system leaves behind.
Open module →What is this system?
What this system is, what its name means, and the standard it holds itself to. This is the record the system leaves behind.
Open module →What can it do?
What the system can do — measured by what people actually hold in their hands: deliveries on time, reliable power, messages no one can read in secret.
Open module →Where does it stand?
The Kardashev Scale ranks a civilization by the energy it harnesses. This is where humanity stands, and what changes at each step up.
Open module →What this system is, what its name means, and the standard it holds itself to. This is the record the system leaves behind.
Stands for all of us. Written in capitals because it comes first: humanity needs unity and a shared will before anything else.
Stands for the world, which includes you and me. Written in lowercase although it is the larger subject: the world grows only when ALL stands first, united.
The Earth is vast compared with us, yet tiny compared with the universe. What we must do is stand as ALL – United as One, so that we endure in a vast universe.
The essence of research is constant improvement and constant renewal, so that everything becomes better, more durable and — above all — more useful. Every upgrade has two possible outcomes: better or worse. Both are valuable.
At ALLiw, failure is a valuable asset on the path to future success. That is why the system never hides a defect. Every defect is recorded, fixed and retested, and becomes a new check so that it cannot return.
Every component of the system follows a single rule: be transcendent. The rule is divided into five pillars, each paired with the concrete practice the system follows to uphold it.
The system runs our own models and never hands user data to a third-party model provider, cloud store or analytics service; when extra capacity is needed, rented GPUs hold the content only in memory and keep nothing afterwards. Messages, images, files, voice messages and group calls are encrypted on the device before they leave it: the message server stores ciphertext only. Every secret in the system is derived from a single key rather than scattered across many places.
The build, the test environment and the version serving users must be identical down to the byte. Before and after every update, the system compares the hash of every file in all three places. A single differing byte stops the release.
One system for many tasks: an AI council with “🐉 God Dragon · Build & Protect” and “😇 God Angel · Analyse & Challenge”; private, group and community messaging; voice, video and group calls; images, files and voice messages; in-conversation search; desktop notifications.
Every update verifies the running version, takes a backup first, replaces files atomically and then test-loads them. If the new version fails to load, the system restores the previous one automatically. Processes are replaced one at a time, so any request a user has in progress runs to completion without interruption.
The system never deletes data on its own. Data is deleted only when explicitly named, and always after a backup. Because every secret is derived from one key, the system can be rebuilt bit for bit after an incident. Legacy is preserved, never traded for speed.
After every change, the system simulates real users walking through the entire structure and every function, checking that they are synchronized, consistent and coherent with one another. Any defect is fixed immediately and the full simulation is run again. The system stops only when it can confirm that the structure is free of defects and that every function is consistent with the rest. For messages, verification goes down to the bit: the text, images and files a recipient receives must match the sender’s bit for bit, and the server’s storage must contain no plaintext at all.
What the system can do — measured by what people actually hold in their hands: deliveries on time, reliable power, messages no one can read in secret.
The ALLiw ecosystem runs on its own models. No third-party model provider, no cloud store, no analytics. Extra capacity comes from rented GPUs that hold content only in memory while computing and keep nothing afterwards. Deployed in an organisation's own infrastructure, the data never leaves it. Every service below is in real-world operation across health, finance, energy, transport, education and telecommunications.
That is why most of what users receive comes from the quality of solvers and computational methods, not from energy alone. Every product below depends on good computational methods.
Behind each service below is an optimization solver that runs every day. Users never see the solver — only the result.
| Product or system | What is optimized | What end users receive | Verified figures |
|---|---|---|---|
| UPS ORION (United States, deployed 2012–2016) | Multi-stop delivery routes, each stop with its own time window | On-time deliveries with fewer wasted miles | The company reports about 100 million miles and 10 million gallons of fuel saved per year; a 2026 report cites about 9 million gallons per year [2] |
| Software installers dnf (Fedora, Red Hat), zypper (openSUSE), conda | Choosing versions of interdependent packages at every install and update | Installs and updates that never break the system | The libsolv solver; conda uses libmamba, built on libsolv [3] |
| AWS IAM Access Analyzer (Zelkova) | Reasoning over access policies: can anyone unintended read the data? | Alerts when cloud storage is exposed to the public | About one billion queries per day [4] |
| CPU and GPU chips from Intel, AMD, Apple and NVIDIA | Formal verification of digital circuits before manufacturing (Cadence Jasper, Synopsys VC Formal) | Chips that compute correctly from the day they ship | The Pentium FDIV division bug (1994) cost Intel a USD 475 million charge and accelerated the adoption of formal verification |
| The LLVM compilers (Clang, Swift, Rust) and GCC | Register allocation for program variables | Faster apps with lower battery use | Every iPhone app and most system software pass through this step |
| Day-ahead electricity markets (PJM, MISO, CAISO; national dispatch centers) | Selecting generating units and output levels for every hour | Lower electricity prices and fewer outages | Runs daily for regional and national grids (Gurobi, CPLEX, FICO Xpress) |
| Crew software from Jeppesen, Sabre and Lufthansa Systems | Crew pairing and aircraft assignment | Fewer cascading cancellations in bad weather | Used for seasonal schedules and daily rescheduling |
| Kidney exchange: the NHS national scheme (UK) and the National Kidney Registry (US) | Selecting exchange cycles and chains among donor–recipient pairs | More patients transplanted from the same pool of donors | Abraham, Blum, Sandholm (2007) [5] |
| AlphaFold DB | Predicting the folded structure of proteins | More than 200 million protein structures, free to search | 2024 Nobel Prize in Chemistry to Hassabis and Jumper (shared with Baker) |
| Games and puzzles: Sudoku, Candy Crush, Tetris, Minesweeper, newspaper puzzle pages | Puzzle setters check every puzzle with a solver before release | Puzzles that are playable, fair and have exactly one solution | Puzzles are machine-checked before they reach players |
| Optimization solvers: Gurobi, IBM CPLEX, FICO Xpress; Google OR-Tools, HiGHS, SCIP (open source) | The common engine behind the rows above | Small businesses gain access to enterprise-grade optimization | OR-Tools, HiGHS and SCIP are free and run on your own machines |
Directions from A to B on Google Maps or Apple Maps already have a fast and exact method. The part that needs a solver is ordering many stops for an entire fleet, as in route optimization services. Telling these two kinds of task apart shows where an optimization tool is worth the investment and where it is not.
Real life almost always comes with existing commitments: signed contracts, promised shifts, transmitters already built, satellites already in orbit. Planning from a blank sheet is easy. Replanning around things that must not be touched is far harder. A good product does this in seconds.
| Product or system | Commitments kept | What is rearranged | What end users receive |
|---|---|---|---|
| The FCC spectrum auction, 2016–2017 | Television stations that did not sell keep their coverage areas | New channels for the remaining stations so that none interferes with another; a solver from the University of British Columbia handled more than 95% of cases within the time limit | The 600 MHz band for 4G and 5G; USD 19.8 billion raised, of which USD 10.05 billion was paid to 175 stations [6] |
| Timefold Solver (formerly OptaPlanner) | Shifts and orders “pinned” because they were promised to customers or staff | Everything else, when someone is sick, a vehicle breaks down or an urgent order arrives | Shift and delivery schedules repaired in seconds instead of rebuilt from scratch |
| FET timetabling software (open source) | Locked periods: visiting teachers, laboratories | All other periods, with no time or room conflicts | Valid timetables for schools and universities |
| Enterprise Wi-Fi: Cisco RRM, dynamic channel selection | Access points with fixed channels | Channels for new access points that do not interfere with their neighbors | Reliable Wi-Fi in offices, airports and hospitals |
| Hospital nurse rostering software | Approved leave and registered shifts | Full staffing for every shift, in line with labor law | Adequate staffing with less overtime |
| Parallel memory design and circuit testing | Memory banks and pins already in use | Data placement so that concurrent accesses do not conflict | Faster memory access in computers and phones |
| Starlink satellites in low Earth orbit | Thousands of satellites already in flight | Orbits and avoidance maneuvers for each satellite | Uninterrupted satellite internet; nearly 50,000 collision-avoidance maneuvers in the six months from December 2023 to May 2024, and about 148,696 in the six months to November 30, 2025 [7] |
Modern public-key cryptography protects most everyday connections. A 256-bit key on a phone is as secure as a legacy 3,072-bit key, so it is faster and uses less battery. That is why it is found in nearly every pocket device.
| Product | What is protected | What end users receive |
|---|---|---|
| Chrome, Edge, Firefox, Safari (every HTTPS site) | Key exchange when a connection opens; by late 2025 about 52% of human web traffic through Cloudflare already included post-quantum key exchange [8] | Passwords and bank cards cannot be intercepted in transit |
| iPhone and iPad from iOS 26 | Every app’s connections use hybrid post-quantum key exchange by default [9] | Apps are protected without developers changing their code |
| Let's Encrypt certificates | Signatures that prove a website is genuine | The padlock icon; blocking of impostor sites |
| WhatsApp, Signal | End-to-end encryption; post-quantum layers added in 2023 and on October 2, 2025 [10] | Messages readable only at the two ends, even against future quantum computers |
| iMessage | Key exchange between Apple devices; the PQ3 post-quantum layer added in 2024 | End-to-end encrypted messages |
| Element, Matrix and ALLiw Chat | Messages, images, files, voice messages and group calls encrypted on the device itself | The server stores ciphertext only. Acceptance testing on October 17, 2026 on the ALLiw test build: the text, images and files recipients received matched the sender’s bit for bit; the server’s storage contained no plaintext |
| Passkeys (iCloud Keychain, Google Password Manager, Windows Hello); YubiKey security keys | Signatures that answer sign-in challenges; the private key never leaves the device | Passwordless sign-in that resists phishing |
| Apple Pay, Google Pay | Encryption of payment data sent to merchants | The real card number is never revealed to the store |
| AirTag and the Find My network | Rotating keys let nearby devices report a location without Apple knowing whose it is [9] | Finding lost items while preserving privacy |
| SIM cards and 5G networks | Subscriber identifier concealment under 3GPP TS 33.501 [11] | Fake base stations cannot capture subscriber identities |
| Bluetooth LE (earbuds, watches); Matter smart homes | Secure pairing; device certificates | People nearby cannot eavesdrop on or take over your devices |
| WireGuard VPN, OpenSSH, Tor | VPN handshakes; default SSH keys; .onion addresses | Secure remote connections for engineers and journalists |
| Cryptocurrency wallets (Ledger, Trezor, MetaMask) | A signature for every transaction | Only the key holder can spend the funds |
| ICAO 9303 e-passports and electronic ID cards; TPM 2.0 chips (required for Windows 11) | Protection against covert chip reading; safekeeping of the device’s keys | Documents that are hard to forge; encrypted drives bound to their own machine |
A sufficiently large quantum computer would break the public-key cryptography in use today. The world has already begun the transition, and most users are protected without having to do anything:
NIST published three post-quantum standards: FIPS 203, 204 and 205 [12].
Chrome, Edge, Firefox and iOS 26 use hybrid key exchange: the classical and post-quantum layers run side by side, so an attacker must break both. Signal added post-quantum layers in 2023 and 2025; Apple added one to iMessage in 2024.
The draft NIST IR 8547 (November 2024) proposes deprecating classical public-key cryptography after 2030 and disallowing it by 2035 [12].
Attackers can “harvest now, decrypt later”: copy data today and wait for a quantum computer to read it. Data that must stay confidential for many years (medical records, trade secrets, private messages) should use hybrid schemes now.
One and the same layer of tools — optimization solvers and public-key cryptography — stands behind very different services. The table below reads by sector: which problem is solved, what the person at the other end receives, and where that is on record.
| Sector | The problem solved | What the end user receives | On record |
|---|---|---|---|
| Healthcare | Nurse rostering; organ exchange over cycles and chains | Every shift fully staffed within labour law and with less overtime; more patients transplanted from the same donor pool | NHS Living Donor Kidney Sharing · National Kidney Registry · Abraham, Blum, Sandholm (ACM EC 2007) |
| Finance and banking | Key-based authentication in place of passwords; encryption of payment data sent to merchants | Phishing-resistant sign-in, because the signature is bound to the real domain; the true card number never reaches the store | W3C WebAuthn · FIDO2 · payment-network tokenisation |
| Energy and the grid | Unit commitment and dispatch for every hour of the day-ahead market | Lower electricity prices and fewer outages, at regional and national scale | PJM · MISO · CAISO and national dispatch centres (Gurobi · CPLEX · FICO Xpress) |
| Transport and logistics | Ordering many stops across a fleet; crew pairing and aircraft assignment | Deliveries inside the promised window; fewer cascading cancellations in bad weather | UPS ORION · Jeppesen · Sabre · Lufthansa Systems |
| Semiconductors and manufacturing | Formal verification of digital circuits before volume production | The chip in the user’s device computes correctly from the first production lot | Cadence Jasper · Synopsys VC Formal; the lesson of the 1994 Pentium FDIV bug (a USD 475 million charge) |
| Telecommunications | Dynamic channel assignment for access points; concealment of the subscriber identifier over the air | Reliable Wi-Fi in offices, airports and hospitals; fake base stations cannot capture subscriber identities | Cisco RRM · 3GPP TS 33.501 |
| The public sector | Repacking broadcast channels around the stations that did not sell, within the auction’s time limit | The 600 MHz band moved to 4G and 5G for the public; USD 19.8 billion raised and USD 10.05 billion paid to 175 stations | The FCC incentive auction, 2016–2017; the University of British Columbia solver handled over 95 % of cases |
| Education | Timetabling around locked periods: visiting teachers and laboratories | A valid timetable with no time or room clashes, rebuilt in seconds when something changes | FET (open source) · Timefold Solver |
| Life sciences | Predicting protein folding across an entire database | More than 200 million protein structures, free to search, for every laboratory in the world | AlphaFold DB · the 2024 Nobel Prize in Chemistry (Hassabis, Jumper, with Baker) |
The five questions an organisation asks before putting a system into real operation. Each is a property of the architecture, not a promise in a contract.
The system runs our own models: no third-party model provider, no cloud store, no analytics. On our public service, extra capacity comes from rented GPUs that hold content only in memory while computing and keep nothing afterwards; that transfer is disclosed on our Privacy and Sub-processors pages. Deployed in an organisation's own infrastructure, no data leaves it.
Messages, images, files, voice messages and group calls are encrypted on the device before they leave it; the message server stores ciphertext only. Group-call keys travel inside the encrypted room, not through the call server.
Every request carries a signed identity, and authorisation is checked IN CODE at the point the work is done, not by a line of instruction. One person’s space is never another’s.
Processes are replaced one at a time, so a request already in flight runs to completion. If the new version fails to load, the system restores the previous one by itself.
The system never deletes data on its own; it deletes only when explicitly named, and always after a backup. Because every secret derives from one key, the system can be rebuilt bit for bit after an incident.
Where a publicly reviewed open standard exists, the system does not invent a protocol of its own. Home-made cryptography is the fastest way to be wrong without anyone noticing.
| Area | Standard | Why it was chosen |
|---|---|---|
| Messaging and calls | Matrix · Olm/Megolm · LiveKit | An open protocol, the server running upstream, the interface written in-house on matrix-js-sdk (Apache-2.0) |
| Passwordless sign-in | W3C WebAuthn · FIDO2 · COSE ES256 / RS256 | The private key never leaves the device; the signature is bound to the domain, so an impostor site cannot replay it |
| Signatures and hashing | Ed25519 · SHA-256 · HMAC-SHA256 | Identities between the system’s own parts are signed; ledgers and checkpoints are sealed with a keyed hash chain |
| Password-based key derivation | scrypt · PBKDF2 | Memory-hard functions, built to slow bulk guessing down |
| Transport | TLS · Let's Encrypt and an internal CA | Name-based certificates for outside users, an internal CA for in-network addresses |
| Post-quantum | NIST FIPS 203 · 204 · 205 · IR 8547 (draft) | Tracking the Matrix specification for hybrid key exchange, to be enabled as soon as it lands — see §2.9 |
A claim is worth no more than the measurement behind it. The table below names the method, the result and the figure — so a reader can check rather than trust.
| What is assured | Method | Result | Figure |
|---|---|---|---|
| Messages correct to the bit | Four simulated users walk every chat function; plaintext and ciphertext are hashed at both ends and compared | The text, images, files and voice messages a recipient receives match the sender’s bit for bit | 58 / 58 |
| No plaintext on the server | The server’s database and file store are scanned for plaintext markers and file-format signatures | No plaintext anywhere in the database; the file store holds the sender’s ciphertext bit for bit | 0 plaintext |
| Build and production are identical | The full hash of every file is compared in three places: the build, the test tree, and the bytes the server actually serves | A single differing byte stops the release | 3 places |
| The gate that serves users | Routes are enumerated from the source and each is probed with a bare request, in both directions of the prompt | Every internal door is absent from the source; an unsigned request is refused | 35 / 35 |
| The whole user portal | An automated suite is re-run after every change, against the build that will ship | The portal’s behaviour is held steady across every upgrade | 276 checks |
Invest in the open-source solvers OR-Tools, HiGHS and SCIP. This is the only way to expand optimization capability faster than energy grows, and the way for small businesses, hospitals and schools to share in the benefits.
Move entirely to post-quantum cryptography ahead of NIST’s 2030–2035 milestones. Enable hybrid schemes now for data that must remain confidential for the long term.
Before buying or building an optimization tool, separate the tasks that already have a fast and exact method (such as A-to-B directions) from those that need a solver (ordering many stops, constrained shift scheduling).
Messages, files and calls are end-to-end encrypted and verified down to the bit. Next step: follow the Matrix specification for hybrid post-quantum key exchange and enable it as soon as it is available, including for group call keys.
Enable hybrid post-quantum key exchange for connections between the browser and the system as soon as the cryptographic libraries support it, so users are protected without having to do anything.
Council workloads are scheduled across machines of differing configurations using approximation methods with quality guarantees: fast for users and sparing of energy.
The Kardashev Scale ranks a civilization by the energy it harnesses. This is where humanity stands, and what changes at each step up.
| Level | Threshold energy | Character | Timeframe |
|---|---|---|---|
| K-0 | ~10¹⁶ W today ~1.88×10¹³ W |
Pre-planetary — the Earth is not yet fully harnessed | 2026 → 2080 |
| K-I | ~10¹⁷ W | Planetary — all the solar energy reaching the Earth | 2080 → 2200 |
| K-II | ~3,8×10²⁶ W | Stellar — enclosing the Sun (a Dyson swarm) | 2200 → 3500 |
| K-III | ~10³⁷ W | Galactic — harnessing the whole Milky Way | 3500 → 100,000 years later |
| K-Ω | → ∞ | Omega Point — beyond time, cosmic infinity | undetermined |
The timeframes are a navigation line, not a prophecy: each step says only how much energy it takes and how it is recognised. Every branch must be one we can walk and walk back from.
The first row is the present, backed by verified figures. The rows that follow are analyses based on each stage’s energy budget, not forecasts of timing. The calculations assume 2024-class hardware at about 1 picojoule per operation.
| Stage of civilization | Optimization: what users receive | Keeping commitments while scaling | User security |
|---|---|---|---|
| K 0.73 · 2024 Available now | Deliveries, flight schedules, power grids, chip verification and software installation all rely on optimization solvers. Trying every possibility would not be feasible even with a full year of the world’s energy. | Spectrum auctions, rescheduling around pinned shifts, satellite collision avoidance. | A 256-bit public key would withstand about 575,000 years against all of humanity’s energy. The entire Bitcoin network (about 16 GW, 0.09% of humanity’s energy) falls short of that level by a factor of about ten billion [13]. |
| K 0.8 – 0.9 In transition | Ten to a hundred times the energy, from hundreds of millions of distributed sources: rooftop solar, battery storage, electric vehicles. Grid dispatch must be decomposed and solved approximately in real time. | Placing new sources on a grid with fixed plants and lines; charging schedules for electric vehicle fleets. | Connections move to hybrid schemes with post-quantum standards; classical keys are retired before 2035. |
| K I · 10¹⁶ W Analysis | Coordination of energy, climate and logistics at planetary scale. About 530 times today’s energy. | Millions of satellites and stations in low Earth orbit: every new object must fit into free space without collision. | A 256-bit public key holds out for only about 1,000 years — and about 3 years if hardware approaches physical limits. No longer sufficient for long-term secrets. |
| K II · 10²⁶ W Analysis | Interplanetary logistics. Earth–Mars signals take 3–22 minutes, so every schedule must be solved locally. | Energy-collecting swarms of billions to trillions of panels around the Sun: the largest placement problem ever. | A classical 256-bit public key falls in about 3 seconds, without any quantum computer. Large-parameter post-quantum cryptography and 256-bit symmetric keys are required. |
| K III · 10³⁶ W Analysis | Coordination across 100,000 light-years. The quality of computational methods decides everything. | Trying every possibility remains impossible at galactic scale; only intelligent methods can do the arranging. | A 256-bit symmetric key (AES-256) remains secure against the entire energy of the galaxy for 10 billion years. |
First, more energy does not by itself make services better — the quality of solvers and methods is what scales. Each step on the Kardashev Scale is a technical milestone, not a promise about timing. Second, keeping commitments while the world changes is a core capability — from hospital rosters to orbiting satellites and energy swarms around the Sun. Third, today’s public-key cryptography is a technology of the pre–Type I era. Moving to post-quantum cryptography by 2030–2035 ensures that users’ secrets outlive civilization’s climb up the scale.