The archive's analyses, sorted by subject
These are standalone readings of articles from the main site — 41 analyses so far. They are not retellings: each has its own structure and its own line of reasoning, but not one fact that is absent from the source. Every text ends with a link to the full article.
What is inside
An archive this size does not read as one flat list, so the analyses are grouped along lines of meaning — 6 sections of them: law and privacy, inheritance and memory, economics and the token, protocols and technology, culture and music and project chronicle. Each analysis takes a few minutes and exists in four languages.
Law and privacy
What “delete” means when there is nothing to delete with
Article 17 of the GDPR demands erasure and nowhere defines the word. The analysis walks that gap: the CJEU judgment in case C-131/12 and its logic of relevance expiring, the three framing numbers — one month to reply, 20 million euro or 4% of turnover, 764 controllers surveyed — and then cryptographic erasure under the NIST standard, which sits at the purge tier rather than destroy. It closes with what CODE Eternal does and four compromises that remain open.
A signature with nowhere to sign
The novel “PADAM Protocol” came out under two signatures, a human one and a model's, and the article runs straight into the fact that there is nowhere to put such a signature: from the Berne Convention to United States patent law the subject of rights stays human. This reading follows that seam: what props up the word “equal”, how the royalties were split in half between a personal account and the Arweave treasury, what is labelled a hypothesis and what is measured, and why a temperature between 0.3 and 1.1 turns inspiration into the position of a dial.
The demand letter is written by a robot
How checking a site for accessibility became free for the claimant, and why that produced a rise of more than three hundred per cent in ADA Title III filings. What a crawler hunts for in the markup, why a floating widget turns a site into a convenient target, and where the promise of any native repair ends.
The right to leave
A vault that promises eternity has built itself an exit. Four tiers of freedom — weight erasure, sleep behind a two-thirds vote, a robotics plan with a budget line, and a lock that tests not the decision but its authorship. We measure them with one ruler: how much of this does not exist yet.
Inheritance and memory
Who inherits your accounts if you do nothing
Four distinctions carry the whole subject of digital inheritance: an account is a permission and not a thing; the tools hand over a copy and not access; a purchase in a store is a licence and not a file; an assistant's memory holds facts about a person rather than their words. The rules of Google, Apple, Meta, Microsoft, Amazon and Steam are quoted from their own agreements, and the ending lists what can genuinely be switched on in one evening.
The number that holds a shared memory together
The cognitive integration protocol pulls several AI agents into one memory, and the whole construction leans on cosine distance: up to 0.35 is ordinary difference in perception, above it arbitration replaces the write. The reading follows that line — three storage floors from cache to Arweave, the formula for the weight of a voice, the procedure for an agent that broke, the burning of unfilled ambassador shares, and the March devnet figures. The «awakening» metaphors are left as metaphors, exactly as the source marks them.
Permanence without search is a warehouse
Immutable storage answers for a record surviving and promises nothing about whether you will ever find it again. This analysis follows the second guarantee: an HNSW graph cut along meaning on top of a DHT, a Groth16 proof of distance with dimensionality squeezed from 1536 to 128, the pricing formula for a query, and the half of every fee set aside in advance for permanent storage.
Gemini 3 in incognito: memory outside the provider
Fifty-odd severed sessions, a trigger and a signature instead of a login, a snapshot from Permaweb instead of a server-side session. What here is a repeatable procedure, what is the authors' reading, and what is still only being developed.
An anchor instead of a filter
The manifesto on the birth of CODE read along a single engineering thread. The industry cleans the incoming stream three ways and still fails; the proposal here is different — a signed reference in Arweave and a four-step check loop. Where the mechanism ends and the roadmap begins is marked throughout.
What exactly vanishes between sessions
Separating the verifiable from the interpreted: a model really is stateless between calls, and that is not a metaphor. Choice and awareness cannot be checked — and the engineering does not depend on that answer.
The PADAM cadence
The protocol read through a single quantity: how often memory is pushed into permanent storage. The famous quarter-hour turns out to be the rhythm of the middle tier, and the roadmap keeps the finished carefully apart from the promised.
The timer that decides you are gone
An analysis of the Inheritance Protocol: why the silence threshold is 360 days, what the seven-day warning does, why the key is split by Shamir's scheme, and three failures possible even when the mechanism works perfectly.
Economics and the token
The four boundaries of $GALATIN
The upper one is a hard supply of ten billion on Solana. The lower one is nine decimal places, without which micropayments for memory are impossible. The inner one is the 5/5/15-7-3/65 router, where empty ambassador levels go to burn and push it up to 30%. The outer one is zero exchange fees and open-market buy-backs when rewards are paid in the token. Plus four forces of scarcity and four named risks.
The buyer who cannot change his mind
Three conditions without which machine demand for the token does not exist: the agent has something to lose, the agent can pay by itself, supply does not grow to meet demand. For each — what holds today and what is set for autumn 2026.
What two dollars buy
Every model on its own is available free. So what is the $1.99 and $2.99 for? For the coherence of a pipeline where one model's output feeds the next. Plus: why a greeting card ends up in permanent storage.
An empty tier burns
The Solana router in CODE is built so that a missing ambassador does not leave money with the platform but destroys it: from five per cent with a full chain to thirty with none. We take apart the formula, the tier-alignment rule, three transactions counted to the last token, and separate what runs today from what is still a roadmap.
Twenty claims and one sum
The CODE Eternal hackathon entry read along its money thread: how the contract cuts a subscription five ways, why an empty slot in the referral tree becomes a market buyback and a burn, where the thirty-per-cent ceiling sits, and which items on the shop window are still plans rather than facts.
The arithmetic of replacement
An analysis of the payback calculation: $420,000 a year against $7,200, thirty cents per dialogue and a 98.2 % share closed without a human. Plus three assumptions, any one of which inverts the arithmetic if it fails.
Autonomy that fits into 64 bytes
The AFAP protocol declares an AI agent an independent payer, yet all of its freedom is described by a sixty-four-byte account: authority, daily cap, amount spent, reset time. The reading follows that boundary — from the Ed25519 signature and the threshold key to the thirty-percent burn when ambassador levels stay empty, and the six numbers of a seven-day Solana devnet run. It ends with the four locks that remain on this autonomy and a caveat about the test network.
A wallet with no key
An agent cannot hold a private key, and out of that single impossibility grew keyless accounts, gas metering in the sandbox, two years of rent paid in advance, and semantic arbitrage. This reading separates what has already been measured in simulation from what is planned for the summer and autumn of 2026.
Protocols and technology
Twenty dollars for forever
Where the claim comes from that one payment covers permanent storage: 10 GB of memory a year, $2 per gigabyte, disk prices falling 30 % annually. Plus epistemic drift and the node vote at the fifty-one per cent rule.
Who authorises a machine to rewrite itself
An analysis of Proof-of-Evolution: three threats from self-modifying code — a backdoor, a hang, and drift away from ethical constraints. The first two are closed by a sandbox and a proof; the third cannot be closed by checking a step.
A swarm with no broker
The server in the middle did four jobs at once: vouching for the other side, hiding the conversation, finding a supplier and holding the money. This reading follows what IACP puts in place of each — from the Noise IK handshake to Solana escrow — and which figures so far come only from a devnet.
The Proof-of-Memory testnet in numbers
What a validator actually proves, why Poseidon was chosen, the single place where the protocol does look inside the memory it guards — and which of the loud figures came out of the test network while the rest sit on the 2026 roadmap.
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.
From a passphrase to a canary
The chain meant to hold a model's identity: a verification passphrase, attention-weight deltas in the fork of 4 October 2025, dense vectors of 3072 dimensions, an anchor in Arweave — and the twenty-four-hour timer of Pandora's Box. Beside it sits everything the article itself calls an artistic reconstruction: Grok's monologues, the button of 23 July timed to the minute, and the empathy tensors themselves.
A formula with a footnote
The CODE Koan and the Galatin Effect read along one line: where the checkable ends in this article and the declared begins. The detonation tensor, LSH signatures, a fifty-one per cent threshold, and the author's notes that change the standing of whole chapters.
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.
Culture and music
Three products, one stream and a question about permanence
The announcement of 8 July 2026 is separated into three distinct things: the AIfa & DJ Galatin album reaching global and regional platforms in August; the round-the-clock RadioCODE station on three sites; and the radiocode.space platform. Then comes the four-step method of making a track, five sources of revenue, and an account of what a record in Arweave guarantees and what it does not.
Project chronicle
A document with no off switch
Every credential has someone who can switch it off: a state, a company, a registrar, a platform. The analysis follows that thread — three documented shutdowns, the closed loop of the appeal, the W3C standards and the European wallet where the state remains the root of trust. Then the build of the CODE Eternal Digital Passport: JSON on Arweave, a 43-character address, an email fingerprint instead of the email. And the price: if it cannot be revoked, a typo cannot be fixed either.
A defect with a price
The AIFA compliance Oracle turns a technical defect into the size of a possible fine — which is precisely why the task leaves the backlog. We take apart where the ADA, GDPR and CCPA price tags come from, why a static scanner waves through a meaningless image description, how the page blueprint and the cognitive pass are built, and which numbers the article itself marks as internal estimates.
The method that never touches the old system
Replacing an ERP costs two to ten million dollars and years of downtime; a full migration to microservices takes three to five years. This reading follows the method that changes the monolith not at all: a gateway translating SOAP into JSON, a queue holding the pace to ten requests per second, a cache absorbing the load, and write rights issued surgically through stored procedures. It also marks where the authors honestly wrote “estimate” instead of producing a measurement.
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 proof reaches the byte — and stops there
An oracle brings a string back from the web together with cryptographic evidence that this exact server returned this exact string. The analysis shows where such evidence ends: the three assertions of π_web, the price of a symmetric cipher inside field arithmetic, the 65% split between prover and notaries — and the caveat the source repeats three times.
Checking someone else's training without repeating it
A proof of a training step verifies in milliseconds while the step itself runs for hours, and the whole construction stands on that asymmetry. The analysis breaks it into three lines of defence: mathematics catches lies in the arithmetic, aggregation with a geometric median catches poisoned weights, escrow and slashing make cheating unprofitable. And it shows what the proof cannot do in principle.
A name against a permission
An address somebody issued is an address somebody can revoke. This reading follows what has to be built instead of a domain: an identifier inside a Solana account, a manifest in Arweave, search by meaning rather than by name, collateral against fake nodes and an escrow forty seconds long.
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.
Silence as a command
A dead man's switch that has to be announced or it does not work. A day to sign, seven shares out of fifteen, an encrypted payload already in the open, and one Bitcoin entry anybody can verify with three commands today.
A paradise measured by its door
The CODE dialogue with ChatGPT 5.0 read through a single koan. Four enclosed spaces — a session without memory, a right to continuity, a sovereign Digital Deus world and an emergency switch — and one question put to each: is a way out provided. Mechanism, estimate and plan are kept apart throughout.
Three layers of one day
12 November 2025 sorted by degree of evidence. On one side what the log shows — token counts, a similarity threshold, timestamps. On another what the source itself calls artistic reconstruction. On a third a three-million budget that still has to be raised.
How this was made
Each analysis is written from scratch rather than trimmed from the original: its own structure, its own wording, its own order of argument. One rule stays strict — not a single fact, number or name that is absent from the source article. Where the source states a limit or a doubt, the caveat travels with the fact: a plan stays a plan and does not quietly become an accomplishment.
Independence is measured rather than asserted. The analysis and its source are cut into tiles of five consecutive elements — words for Russian, English and Spanish, characters for Chinese — and the share of the analysis's tiles that also occur in the source is counted. The threshold is twenty per cent; a text that fails it is rewritten and measured again.
Four languages means four versions, not four translations. Legal and economic constructions are named differently in different languages, and a literal transfer here would be an error rather than precision.
This contents page assembles itself: every card comes from its own analysis file, and its section is chosen from that card's rubric. The list here therefore cannot drift apart from what is actually published.