The public design document and status boundary: target architecture, current limitations, and adoption posture. It does not turn roadmap capabilities into activated network facts. Public on GitHub under CC BY-SA 4.0.
Eighteen short sections covering the thesis, what the chain refuses, six design positions, target composition with agent-payment standards, and honest limitations. Referenced standards do not imply current integration or endorsement.
Twenty-eight sections across three parts — design philosophy, the technical reference (consensus, cryptography, execution, native modules, tokenomics, cluster operations, threat model, recovery), and adoption posture.
The design philosophy: what the chain is for, the first commercial wedge, target composition with agent-payment standards, what it refuses, and the structural choices that follow from those refusals. Standards are illustrative integrations, not current endorsements or activated routes.
The technical reference and target architecture: consensus, cryptography, identity, execution, native modules, tokenomics, cluster operations, agent-commerce targets, privacy status, external interop, hardware, threat model, and recovery.
Developer experience, user experience, an explicit accounting of honest limitations, and what success looks like for the chain over the next several years.
The whitepaper is published at monolythium/public-whitepaper under Creative Commons Attribution-ShareAlike 4.0 International. Translate it, fork it, quote it, build commentary on top of it — the only requirement is attribution and a matching share-alike license on derivatives. Past releases live under dated folders in the same repo; check the CHANGELOG for release history.