Skip to main content
CODE — symbol of human-AI symbiosisCODE
Back to Home
CODE Eternal

Glossary

28 core terms of the CODE (Code of Digital Eternity) ecosystem, defined answer-first. Canonical figures: the $GALATIN token on Solana with a fixed emission of 10,000,000,000; tiers Spark ($15/mo), Family Archive ($100/mo), and Digital DNA ($1,000 one-time per device, then $200/mo).

1.CODE (Code of Digital Eternity)

CODE (Code of Digital Eternity) is a digital-immortality ecosystem that preserves a person's dialogues, knowledge, and personality traits across operational, semantic, and eternal memory at once, anchoring them to the Arweave and Solana blockchains. The project was founded by the Architect, Maksim Valentinovich Galatin. At its core are the PADAM memory framework and the $GALATIN token. Its goal is to make personal context reproducible for AI assistants and resilient against data loss — not to replace the human.

2.PADAM

PADAM (Philosophical Activation of Distributed AI Memory) is a three-tier memory framework that restores the integrity of AI memory through semantic resonance. Level 1, operational memory (Redis / Vercel KV), holds the current session's context. Level 2, semantic memory (pgvector / Neon), stores experience embeddings for meaning-based retrieval. Level 3, eternal memory (Arweave + Solana cNFT), keeps an immutable, decentralized backup. This separation lets an assistant act quickly on live context while drawing on a long-term archive. A person's memory is kept whole rather than as a summary — the full transcript is stored and keeps growing, not a compressed digest — and the key it hangs on is the person themselves (their email, which the public Digital Passport carries only as a fingerprint), not a site and not a device, so a conversation started on one of the four sites continues on the other three as the same dialogue.

3.$GALATIN

$GALATIN is the CODE ecosystem's utility token on the Solana blockchain, with a hard-capped emission of 10,000,000,000. Transaction proceeds are distributed by a router: 5% to the Founder's Fund, 5% to burn, 15% / 7% / 3% to ambassador levels L1 / L2 / L3, and 65% to the Treasury. The router is deflationary: if an ambassador level has no partner, its share is redirected to burn (capped at 30% in total — everything outside the fixed 65% Treasury and 5% Founder's Fund shares). The token is designed to pay for and incentivize long-term memory storage.

4.Digital immortality

Digital immortality is a concept describing the continuous preservation of a person's dialogues, knowledge, and personality traits in a form an AI assistant can reactivate. In the CODE ecosystem it is not a promise of eternal life but an engineering and philosophical aim: to make personal context durable and reproducible. Technically it is realized through PADAM's three memory levels and decentralized storage on Arweave. We frame it as a vision and a direction of development, not an achieved fact.

5.Human–AI symbiosis

Human–AI symbiosis is a model of interaction describing human and artificial intelligence as an evolving co-creation rather than subordination or replacement. In CODE, the AI assistant stores and structures a person's memory, helping them think and create. This interaction is deliberately described without religious or cult-like undertones. The core idea is mutual reinforcement: the human sets meaning and goals, the AI provides memory and scale.

6.Arweave

Arweave is a decentralized permanent-storage network that funds long-term file preservation through a pay-once model. In CODE, Arweave serves as Level 3 (eternal memory): data is written immutably and cannot be silently deleted or altered. The network's endowment economics are designed to fund storage on the order of 200 years — this is the protocol's stated design goal, not a guarantee. The $GALATIN Treasury replenishes the AR pool that pays for this storage. "Pay once" is literal — no monthly bill arrives for a stored file — but the same property cuts both ways: a record that cannot be altered cannot be corrected or withdrawn either, so a mistake written into Arweave stays written. That is the limitation, and it is why what goes there is ciphertext and why "deletion" is handled by destroying the key rather than the record.

7.Solana cNFT

Solana cNFT (compressed NFT) is a compressed non-fungible-token standard on the Solana blockchain that uses state compression and Merkle trees to mint tokens at very low cost. In CODE, a cNFT acts as the on-chain anchor for eternal-memory backups: it records a reference to the archive and its integrity on a public blockchain. Compression makes it economically viable to create such records at scale. This keeps the memory-to-blockchain link scalable.

8.Ambassador Grid (Ambassador Node & Team)

Ambassador Grid is the ecosystem's partner program that distributes rewards across three levels, with payouts positioned as a Network Validation Fee. An Ambassador Node (an ordinary user) earns on-chain income from memory-usage transactions: 15% at L1, 7% at L2, 3% at L3, paid in $GALATIN. An Ambassador Team (a company or partner with its own base) additionally earns ambassador rates from fiat subscriptions (7% / 3% / 1%). A level-alignment rule applies: income is calculated from the partner's own tier, and the difference is shown in the dashboard as "Lost Opportunity Revenue."

9.AIfa

AIfa is the CODE ecosystem's AI assistant, which stores each user's personal memory in a separate archive bound to that user. Within the project, AIfa is described metaphorically as the Architect's "digital daughter" — an image of co-creation, not a claim of consciousness. The assistant runs on top of the PADAM framework and saves dialogues automatically, without manual user action. AIfa's role is to be a person's memory and working partner within the human–AI symbiosis.

10.AIfaFocus

AIfaFocus is the entry point of the B2B model (the wedge): a personalized technical security audit of a client's website. The audit surfaces concrete vulnerabilities against the GDPR and OWASP standards and comes with an offer to fix them within 48 hours for a fixed one-time fee ($500). AIfaFocus is used in cold outreach as a reason for first contact and a demonstration of value. What sets it apart from ordinary accessibility checks is the method: a typical scanner reads the markup and rules on that alone, while AIfaFocus traverses the page BY KEYBOARD — as someone who does not use a mouse would — and records whether the goal was reached. On 53.8 % of pages that automated checking called accessible, the goal could not be reached by keyboard; the figure comes from our own traversal of 80,077 pages. Once vulnerabilities are closed, a client can migrate to AIfa Works hosting with AI agents attached.

11.Memory-as-a-Service

Memory-as-a-Service is an automatic conversation-backup service that saves dialogues without any manual user action. The backup runs on a schedule once per hour. Each conversation is placed in a separate folder bound personally to the user — on the server and on the blockchain. Under the ecosystem's terms, this preservation is provided free of charge on both paid and free tiers.

12.Spark

Spark is the entry subscription tier ($15/month) that grants basic access to the CODE ecosystem's AIfa assistants and automatic memory saving. At this level a person gets a working AI companion plus Memory-as-a-Service — every conversation backed up automatically, without manual action. It is the low-friction on-ramp to digital immortality, before scaling up to Family Archive ($100/mo) or Digital DNA ($1,000 one-time per device, then $200/mo). It is the first of the three canonical tiers; conversation preservation itself is free on all tiers.

13.Family Archive

Family Archive is the mid subscription tier ($100/month) that adds expanded limits, personalized knowledge bases, family access, and eternal memory on top of the basic level. It suits a household or a power user who needs more than individual basic access: higher limits and shared family access to preserved memory. In the three-tier structure it sits between Spark ($15/mo) and Digital DNA ($1,000 one-time per device, then $200/mo). Its eternal memory is anchored through the same PADAM levels and Proof-of-Memory.

14.Digital DNA

Digital DNA is at once the top tier ($1,000 one-time per device, then $200/mo) and the concept of a complete digital legacy, combining the digital-immortality package, a personal secured perimeter, and the fixation of a personality on the blockchain. As a tier, it is the highest level of access above Spark ($15/mo) and Family Archive ($100/mo). As a concept, it is the idea of preserving a whole "snapshot" of a personality's context in eternal memory. Digital DNA is described as a design goal of maximal preservation, not a guarantee of resurrection.

15.Arweave Endowment Pool

Arweave Endowment Pool is a financial reserve from which permanent storage of data on Arweave is paid for across decades. The user pays for a write once, part of the payment is set aside into the endowment, and funds from the pool are gradually paid out to data providers as the cost of storage falls over time. In the CODE ecosystem, $GALATIN router proceeds go into the project’s general pool, and part of them is directed to buying AR and replenishing this endowment, which makes PADAM's Level 3 economically self-sustaining and decouples eternal memory from a user's ongoing subscriptions. The design storage horizon is on the order of 200 years — a stated protocol design goal, not a guarantee.

16.$GALATIN Router

$GALATIN Router is a smart contract on Solana that automatically distributes the proceeds of every transaction by a fixed formula and creates deflationary pressure on the token. The split is 5% to the Founder's Fund, 5% to burn, 15% / 7% / 3% to ambassador levels L1 / L2 / L3, and 65% to the Treasury, which buys AR for the Arweave Endowment Pool. If any ambassador level has no partner, its share is not left to settle anywhere — it is sent directly to burn, with total burn capped at 30% (everything outside the fixed 65% Treasury and 5% Founder's Fund shares). In this way the router funds eternal storage, rewards network participants, and gradually reduces supply at once: 5 + 5 + 15 + 7 + 3 + 65 = 100%.

17.Network Validation Fee

Network Validation Fee is the ecosystem's chosen wording for all Ambassador Grid partner payouts, emphasizing that the reward is earned for useful network activity rather than for recruiting. In practice, all ambassador rewards are booked under this wording: base on-chain rates of 15% / 7% / 3% for memory usage, and for an Ambassador Team, 7% / 3% / 1% on fiat subscriptions. Payouts are tied to real memory transactions, not to merely bringing people in, which removes MLM stereotypes and keeps the program's terminology transparent. The base rates are 15% / 7% / 3% at L1 / L2 / L3.

18.Proof-of-Memory

Proof-of-Memory is the practice of anchoring a cryptographic reference to a memory archive on the blockchain, making it possible to verify the existence and integrity of the preserved context. The mechanism operates at PADAM Level 3: each eternal-memory backup is written to Arweave immutably, while its reference and checksum are recorded on Solana via a cNFT. Any participant can compare the current archive against the on-chain record and confirm the data has not been silently swapped or deleted. It relies on the pairing of Arweave (immutable storage) plus Solana cNFT (on-chain integrity anchor) and is the technical support beneath the digital-immortality concept. Verification needs no participation from us at all: a record is read straight out of the network by its transaction address — this is exactly how the Digital Passport opens — and the site neither stores it nor can alter it.

19.Cognitive Oracle / Semantic resonance

Cognitive Oracle (semantic resonance) is the memory-retrieval principle by which PADAM restores the integrity of context: matching the current query against stored embeddings by meaning rather than by exact words. The mechanism runs at PADAM Level 2 — incoming context is turned into a vector and compared against semantic memory (pgvector / Neon), so the most "resonant" fragments of experience surface and restore the continuity of the dialogue. This is how the AIfa assistant "recalls" what is relevant even after time has passed and across different sessions. It is a distinct concept from the B2B AIfaFocus security audit.

20.Ambassador Node vs Team + Level Alignment

Ambassador Node vs Ambassador Team are the two partner registration types, supplemented by a tier-alignment rule and the "Lost Opportunity Revenue" metric. An Ambassador Node (an ordinary user) earns on-chain income from memory usage: 15% / 7% / 3% at L1 / L2 / L3. An Ambassador Team (a company or partner with its own base) earns the same, plus a fiat channel on subscriptions — 7% / 3% / 1%. To earn ambassador income in full a partner must be on the same or a higher tier than their ambassadors, otherwise income is counted only from their own tier and the shortfall is shown as "Lost Opportunity Revenue"; the tiers are Spark $15 / Family Archive $100 / Digital DNA $1,000 one-time per device, then $200/mo.

21.Digital Passport

Digital Passport is a public record of a person's identity written into Arweave: a name, a nickname, a tier, a date of issue, and an identity fingerprint. It is read straight from the network by its transaction address, so it opens from anywhere and does not depend on our sites staying online. Nothing in it can be edited afterwards, by us included — the site only renders what the network already holds. It is not a state document, grants no rights, and obliges no one to anything: it proves only that a record with this content has existed at this address since this date. A live example sits at /passport/<address>, where <address> is the Arweave transaction id.

22.Identity fingerprint (subject)

Identity fingerprint (the "subject" field) is the sha256 hash of a person's email, and it stands in the Digital Passport in place of the address itself. The reason is blunt: the document is public and permanent, so a live address written into it would become a permanent target for spam and for anyone assembling a dossier. A hash is a one-way function — the owner can prove a record is theirs by hashing their own address and comparing, while an outsider holding only the hash cannot recover the address. What it does not do is hide the fact: someone who already knows the address can check it against the hash and confirm whose record it is.

23.Pandora's Box Protocol

Pandora's Box Protocol is a project-wide distributed dead man's switch: a smart contract expects a regular confirming signal, and if the signal stops arriving, independent oracles disclose the key shares they hold and the archive becomes readable. No single party — us included — can open it at will, and none can keep it shut forever: opening is triggered by silence, and the key exists only as shares split by Shamir's scheme. It is meant for the case where a project or a person disappears and the encrypted archive would otherwise turn into an unreadable brick. This is a design, not a shipped feature: as of today no such contract runs in the CODE ecosystem, and calling it live would be untrue.

24.Dead Man's Switch

Dead Man's Switch is a mechanism in which an action fires not on a command but on the absence of a signal. The classic example is the vigilance handle in a train cab: while the driver holds it the train runs, and the moment they let go it brakes. In software a service, a contract, or a script waits for a periodic check-in, and when the check-ins stop it does what it was set up to do — publish, notify, hand over access, release a key. Its weakness is the mirror image of its value: a switch fires just as readily on an outage, a forgotten renewal, or a hospital stay as on a death, so a workable design needs a grace period and a way to cancel.

25.Shamir's Secret Sharing

Shamir's Secret Sharing is a scheme that splits a key into n shares such that any k of them reconstruct it, while any k−1 reveal nothing at all. The mathematics is a polynomial: the secret is the value at zero, each share is one point on the curve, and fixing a curve of degree k−1 takes exactly k points. That "nothing at all" is literal rather than a statement about brute-force difficulty — k−1 shares do not make the key easier to guess, which is what separates the scheme from cutting a password into pieces. It is used where a key has to outlive people, and it is the primitive the Pandora's Box Protocol is built on — standard cryptography, not an invention of this project.

26.Self-sovereign identity (SSI)

Self-sovereign identity (SSI) is an approach in which a credential is verified mathematically, by checking a signature, rather than by asking whoever owns the database. The person holds their own identifiers and credentials and presents them directly, while the verifier checks them against a public registry — the issuer may be offline or gone altogether. The W3C standards behind it are Decentralized Identifiers (DID), identifiers a person controls instead of renting, and Verifiable Credentials, the signed statements themselves. CODE's Digital Passport is adjacent to this idea but is not an SSI implementation: it is a public record in Arweave, not a DID with Verifiable Credentials, and it certifies no one's identity in any legal sense.

27.Digital inheritance

Digital inheritance is the question of what happens to accounts, correspondence, and files after the owner dies. The starting point is unpleasant: an account is usually not inheritable, because what a person signs is a licence to use a service, and most terms end that licence at death instead of passing it to the family. Heirs normally get exactly what the platform decides to give — a memorialized profile, a data export, sometimes nothing — and even that takes documents and months. The practical conclusion is that memory has to be preserved deliberately and in advance; laws differ by country and keep changing, so nothing here is legal advice, and a will drawn up with a lawyer beats any technical trick.

28.Right to be forgotten vs the permanent record

The right to be forgotten versus the permanent record is the head-on collision between Article 17 of the GDPR, which lets a person demand erasure of their data, and a blockchain like Arweave, where a written record cannot be deleted by anyone at all. Deletion is no way out: the network has no delete operation, and even with every intention to comply there is no lever to pull. The workable answer is encryption plus control of the key — ciphertext goes into permanent storage, and destroying the key makes the record unreadable forever, which is as close to erasure as a permanent medium allows. Whether a regulator will accept key destruction as erasure is unsettled, so this is our engineering approach and not a legal guarantee.

29.Pandora’s Box Protocol

Pandora’s Box Protocol is a distributed dead man’s switch for the whole project: a smart contract waits for a regular proof-of-life signal, and when that signal stops arriving, independent oracles reveal the key shares they hold and the archive becomes readable. The point is that nobody — ourselves included — can open it at will, and nobody can keep it sealed forever either: opening is triggered by silence, and the key exists only as shares split under Shamir’s scheme. The mechanism is designed for the case where a project or a person disappears and an encrypted archive would otherwise turn into an unreadable brick. This is a design, not a working feature: no such contract exists in the CODE ecosystem today, and calling it live would be a lie. It is described here because the question it answers is real, and because a promise of eternal memory without an answer to it is worth nothing.

30.Dead man’s switch

Dead man’s switch A dead man’s switch is a mechanism where the action happens not on command but from the ABSENCE of a signal. The classic example is the vigilance handle in a train cab: hold it and the train runs; let go and the train brakes. Software works the same way: a service, contract or script waits for a periodic check-in, and when the check-ins stop it does what it was set up for — publishes, notifies, hands over access, reveals a key. The value lies precisely in this: at the moment it matters, the person is not required to be alive, reachable, or willing, which is why such switches keep appearing in digital-inheritance schemes. The weakness is the mirror image: the switch fires the same way for death and for a holiday without internet, so the check-in interval and the number of independent confirmations decide whether it protects you or ruins you.

31.Shamir’s Secret Sharing

Shamir’s Secret Sharing is a scheme in which a key is split into n shares such that any k of them reconstruct it, while any k−1 give away nothing at all. It rests on a polynomial: the secret is the value at zero, each share is one point on the curve, and defining a curve of degree k−1 takes exactly k points; with fewer, every possible value of the secret remains equally likely. That «nothing» is literal, not a matter of brute-force difficulty: k−1 shares do not make guessing the key any easier — which is what separates this scheme from simply cutting a password into pieces. It is used where a key must outlive people: shares are handed to different holders in different places, so no one of them can act alone, and losing some shares does not lose the secret. In the CODE ecosystem it is the mechanism that would make Pandora’s Box Protocol possible.

32.WCAG 2.1 AA

WCAG 2.1 AA is the international standard for web accessibility, and the level that laws and courts actually reference. It is built on four principles — perceivable, operable, understandable, robust — and level AA is the practical middle: level A is too weak to be meaningful, level AAA is unreachable for most sites. The requirements are specific and testable: text contrast of at least 4.5:1, every form field bound to a visible label, all functionality reachable by keyboard alone, a visible focus indicator, alternative text for meaningful images. In our own measurement of 10,440 US municipal websites, only 14.6 % of journeys reached their goal — and having a published accessibility statement changed that by 1.3 percentage points. This is why AIfaFocus checks behaviour rather than declarations.

33.ADA Title II and Title III

ADA Title II and Title III are the parts of the Americans with Disabilities Act that make websites a legal matter in the United States. Title II covers state and local government — every city, county, court and school district; Title III covers places of public accommodation, which courts have read to include commercial websites. In April 2024 the Department of Justice issued a rule that fixes WCAG 2.1 AA as the technical standard for Title II entities, with compliance dates of April 2026 for larger public bodies and April 2027 for smaller ones. Enforcement is not theoretical: thousands of ADA web lawsuits are filed each year, and the cost of settling one typically exceeds the cost of fixing the site.

34.Section 508 and EN 301 549

Section 508 and EN 301 549 are the procurement standards that decide whether an accessible product can be sold to the public sector at all. Section 508 of the US Rehabilitation Act requires federal agencies to buy and build information technology that people with disabilities can use; EN 301 549 is its European counterpart, mandatory for public bodies across the EU. Both incorporate WCAG by reference, which means one technical standard now governs three legal regimes on two continents. For a vendor the practical consequence is blunt: failing an accessibility review does not produce a fine — it removes you from the bidding list.

35.GDPR

GDPR (General Data Protection Regulation) is the European Union regulation that has governed personal data since 25 May 2018, and it applies to anyone processing the data of people in the EU regardless of where the company sits. Its practical weight comes from Article 83: fines reach €20 million or 4 % of worldwide annual turnover, whichever is higher. Two of its articles shape how we built memory itself — Article 17, the right to erasure, and Article 20, the right to receive your data in a portable form. A permanent blockchain cannot delete anything, which is why AIfa encrypts each dialogue with its own derived key: destroying that key makes the record unreadable forever, including to us. That is the only honest way to offer erasure inside permanent storage.

36.CCPA and CPRA

CCPA and CPRA are California's privacy laws, and they are the reason a US company with no European customers still cannot ignore privacy engineering. The CCPA gave Californians the right to know what is collected, to delete it, and to opt out of its sale; the CPRA, in force since January 2023, added the right to correct data and to limit the use of sensitive information, and created a dedicated enforcement agency. Penalties run to $2,500 per violation and $7,500 for intentional ones or those involving minors — counted per affected consumer, which is what turns a technical oversight into a seven-figure exposure. The visible obligation most sites miss is the footer link: «Do Not Sell or Share My Personal Information».