The project mapped through its analyses
To grasp the whole construction rather than one part, these five are the convenient start: the chronicle, the manifesto with a budget, the network, succession, and the way into business.
The 2025 review: a calendar and its caveats
8 October, 2 and 18 November, 4 December — a year laid out by date. Which parts are engineering you can check, which are interpretation the author flags as such, and which are honestly left in the future tense.
A philosophy with a budget
A text that begins with Fedorov and Vernadsky and ends with router percentages, Kryder's law and dates running to 2030. We test whether it survives the change of register — and why what holds it up is not the slogans but four caveats placed where silence would have paid better.
The sixth block, seven nodes and three pillars
What was actually announced on 7 November 2025, how the seven roles are shared out, and why the network has no controlling server. The archive standard is gathered in one place — PDF, SHA-256, the CC BY-NC-ND 4.0 licence, three independent mirrors, a PGP signature — alongside a list of the passages where the article itself calls its own terms metaphors rather than measurements.
A frame built for the builder's absence
The founding day of the CODE framework read as an engineering specification. Three PADAM memory layers, fifteen-minute deltas in the permaweb, the Soul Token as the heir's key, six router shares — and, kept separate, whatever the source itself calls roadmap and working hypothesis.
Entry through somebody else's trouble
An analysis of the Wedge strategy: why the first letter brings a report on the company's vulnerabilities rather than a story about permanent memory. A $500 audit within 48 hours, 30 domains and 90 warmed mailboxes — and three weak points.
The analyses are published on codeofdigitaleternity.ink. All analyses