The Evrylife Constitution

Status: DRAFT v0.3. Built from the ECP's immutables, the governance machinery (zkr-POGO, EAIP, the nine treasury pools), and the architectural decisions established in the build record. To be refined and ratified via zkr-POGO governance before/at handoff. Unresolved items are marked (TBD).

Preamble

Evrylife is a public good: a community-owned, decentralized social protocol for exploring the social world. It belongs to no company and no founder. Its purpose is to let billions of people communicate, create, and self-govern on durable open protocols — free from extraction, surveillance, and capture. This Constitution sets out the principles that may never be sold out, the rights of members, how the community governs itself, and how the protocol may change.

Article I — Immutable Foundations can NEVER change

The anti-greed guarantees. Not amendable by any vote, founder, team, or future authority.

1. 24,000,000,000 EVRY hard cap — fixed, immutable, no minting beyond it ever (EVRYToken is immutable by design; no upgradeable proxy).
2. Zero founder, VC, or team allocation — none now, none ever. Distribution is contribution-based and prorated only.
3. Decentralization of control — no single entity (including the founder) may control the protocol, its data, its keys, its moderation, or the code users run. Authority rests with the community.
4. Public good, non-extractive — the protocol serves its community, never an owner's profit. The commons funds itself and spends only from existing balance.
5. Self-custody & sovereignty — members hold their own identity and keys; no central party can seize or lock them out.

Article II — Member Rights

• Verified-human participation with a fair voice (sybil resistance).
• Identity self-custody — wallet → did:key; you are not an entry in a company database.
• Data ownership & portability — your data lives on open protocols; you can export and leave anytime, taking it with you.
• Privacy by right — granular controls at content, account, and DAO levels (public / private / connections / some-connections / subscription tiers); private data is Lit-encrypted; review is identity-stripped and anonymized (cryptographic zero-knowledge via Semaphore is deferred).
• Bring-your-own infrastructure — members pair their own storage and AI providers and keys; their usage is theirs. The DAO subsidizes only a free tier; no member is forced onto a single provider.
• Freedom of expression within the community-governed Community Guidelines.
• Due process — transparent, decentralized moderation with graduated consequences and appeals.
• (TBD) full enumerated bill of rights + explicit anti-capture safeguards.

Article III — Data & Storage Sovereignty

1. Durable protocol primitives, never company products — built on IPFS, libp2p, EVM, Arweave, Filecoin; the database engine stays swappable behind dataService.
2. No centralized login for protocol storage — storage/identity is wallet-based; email-account services are not a dependency.
3. Privacy-matched storage — each item is stored only on a provider whose capabilities fit its privacy level. Permanent-public storage (Arweave) is for public data and code only; private / followers / subscription content must be encrypted and deletable, on the member's own provider.
4. Durability without a single point of failure — public protocol data is content-addressed and pinned/replicated across many independent providers and community nodes; no node's disk is the source of truth.

Article IV — Governance

• zkr-POGO consensus — moderation, development, and governance decisions are made by stake-weighted, reputation-bounded community consensus; never a central authority.
• EAIP proposals + zkr-POGO community voting evolve community-governed variables and policies; proposing requires min_proposal_stake.
• Nine treasury pools (tp01–tp09) are all community-directed.
• The change lifecycle is law: suggest → zkr-POGO consensus → build → review consensus → implement → record in the ECP. App and ECP must always match. (TBD) quorum/threshold per decision class.

Article V — Code & Protocol Evolution

1. The code itself is governed. The application evolves through the change lifecycle / zkr-POGO — it is not owned or pushed unilaterally.
2. Governed, updatable deployment — evrylife.eth is the community's address. Each approved release is an immutable IPFS/Arweave artifact (a permanent, verifiable version history); the ENS contenthash is the mutable pointer that advances only by a passing vote, executed by the DAO multisig.
3. Reproducible builds — anyone can rebuild the governance-approved source and verify the live artifact matches it; no unapproved code can reach members.
4. Decentralized source hosting — the canonical source lives on peer-to-peer git (Radicle), not a company product; GitHub is a temporary bootstrap mirror, sunset to optional mirror at handoff so no single company can censor or delete the protocol's code. Permanent archives via Arweave.
5. Gated, honest rollout — the public domain may show a gated preview (waitlist + sandbox) while the app matures; sandbox activity that counts toward the airdrop must be durably and verifiably stored on the protocol, never only in a single browser, so the airdrop is fair and auditable.

Article VI — Artificial Intelligence

1. AI is advisory and subordinate — the DAO's AI agents may assist, classify, and recommend, but never unilaterally act; zkr-POGO consensus decides.
2. Agents are governed + toggleable — each agent is gated by an ai_toggle the DAO controls and bounded by confidence thresholds the community sets.
3. The knowledgebases train the agents. The ECP knowledgebases are the DAO's codified knowledge and double as the agents' operating instructions. Ratifying or amending a knowledgebase therefore is training/re-aligning the responsible agent — keeping AI behaviour transparent, versioned, and under community control.
4. Member AI is BYO — members use their own AI keys/usage for their own content; the DAO's agents use decentralized AI only for DAO-level tasks.

Article VII — Economics of the Commons

• EVRY tokenomics fund a self-sustaining commons: fees, slashing, donations, and zkr-POGO-as-a-service revenue flow to community-directed treasuries.
• Prepaid-escrow invariant — operating costs are paid only from existing approved balance; no unaffordable or outstanding bills, ever.
• (TBD) canonical fee / slashing / revenue flow summary.

Article VIII — Conduct & Moderation

• The Community Guidelines define acceptable content and conduct, are community-governed (amendable via EAIP), and are subordinate to this Constitution.
• Moderation is decentralized, transparent, proportional, good-faith — graduated consequences, on-record outcomes, anonymous review; appeals via governance.

Article IX — Language & Linguistic Diversity

Language is part of the commons. The protocol protects linguistic diversity with the same seriousness as Article I protects the token economics.

1. Every supported language is a first-class citizen. Base translations of the platform (UI labels, help tips) and of the shared vocabulary (Web3 Meta Tree) are versioned, committed artifacts — durable community property recorded in the ECP/git, never ephemeral AI output. A language, once adopted, cannot be silently dropped or degraded.
2. Three layers, three rules. Platform text: translated once at base by the DAO, corrected forever after through zkr-POGO consensus — never translated on the fly at runtime. Web3 Meta Tree: one canonical label per node per language, batch-translated once after the tree is confirmed, then community-corrected. User content: translated on demand only on the requesting member's own BYO AI key, cached on their device; authors may attach their own translations to make them free for all readers.
3. No DAO funds on per-reader translation. Recurring, per-reader translation cost is borne by the reader (or the author, voluntarily) — never by the treasuries.
4. Community correction is the source of truth. Machine output is a draft; a zkr-POGO-consensus edit always supersedes it. Native speakers govern their own language.
5. The DAO's AI agents obey this architecture — every agent touching text must route user-content translation through the member's own keys.

Article X — Amendment & Hierarchy

• Article I is never amendable. Any proposal that weakens the 24B cap, introduces founder/VC/team allocation, or centralizes control is void by construction.
• All other Articles and subordinate documents change only through zkr-POGO governance / EAIP / zkr-POGO community vote, recorded via git in the ECP. (TBD) supermajority + ratification thresholds.
• Bootstrap exception — during bootstrap the owner may bypass the consensus vote to move fast, but never the ECP recording and never Article I; all bootstrap changes are transparent and reversible and hand off to full community governance at TGE/handoff.
• Hierarchy — this Constitution is supreme; Article I prevails over everything. Subordinate community-governed documents: Community Guidelines, Terms, Privacy, EAIP Guidelines, and the other knowledgebases.

Working notes

Published as-is — these are the open items to resolve before ratification.

• Define governance thresholds (quorum, constitutional supermajority, ratification mechanism and timing).
• Complete the member bill of rights and anti-capture safeguards (Article II).
• Build the per-agent knowledgebase → function mapping table (Article VI.3).
• Confirm canonical economic flows (Article VII).
• Align the Community Guidelines wording with the public site; add any missing prohibited categories explicitly.