Evrylife Foundation

Protocol changes

What’s changing

Every change to the Evrylife protocol — adopted proposals, confirmed problem reports, and verified builds — pulled from the community relay and the build history. Last refreshed 2026-10-23T21:10:22Z, control plane ECP v7.7.338.

143proposals adopted
436problem reports confirmed
460builds verified
1,557review opinions recorded

Counted from the community relay. Bootstrap figures: reviews are decided by the bootstrap reviewer until the community reaches its hand-off milestones, and all pre-launch points reset at launch.

Recent changes

Adopted proposal Confirmed report Release Build

2026-10-22

  • Confirmed report ai auditor qualification quiz (F0352) [/onboarding/ai-auditor-qualification]: Every quiz-review card tells the reviewer to decide against "community guidelines & content policy", whichever knowledgeba
  • Release Fix existing tests for the verified-order view
  • Build Fix existing tests for the verified-order view
  • Build A build order counts only when signed by an authorised identity

2026-10-21

  • Confirmed report dashboard home (F0382) [/dashboard?section=Governance%20Tasks]: The AI auditor qualification quiz is a fixed hand-written question list, so the adopted reporting standard never reaches the quiz review
  • Confirmed report dashboard home (F0375) [/dashboard?section=Governance%20Tasks]: A regenerated knowledgebase quiz need not test the part that changed, so a rule added to a long document is quizzed only by chance; KB01
  • Confirmed report dashboard home (F0352) [/dashboard?section=Governance%20Tasks]: Every governance vote card says the pass mark is "not stamped on this proposal", even when it is, because the proposal list the card rea
  • Release The pinned kb-quiz artifact shape carries the quiz focus and count
  • Build The pinned kb-quiz artifact shape carries the quiz focus and count
  • Release Badge knowledge freshness: holders are notified when a quiz changes; a material change needs a re-take
  • Build Badge knowledge freshness: holders are notified when a quiz changes; a material change needs a re-take
  • Release A quiz review is decided against the document whose quiz is under review
  • Build A quiz review is decided against the document whose quiz is under review
  • Release The KB013 qualification quiz tests the reporting standard
  • Build The KB013 qualification quiz tests the reporting standard
  • Release The vote card shows the stamped pass mark
  • Build The vote card shows the stamped pass mark

2026-10-17

  • Adopted proposal Badge knowledge freshness: KB/quiz updates notify existing badge holders, governed re-certification
  • Adopted proposal A build order counts only when the signer of the decision that made it wrote it: no member can create, close or overwrite build orders

2026-10-16

  • Confirmed report dashboard home (F0375) [/dashboard?section=Dev%20Tasks]: A knowledgebase change never reaches its quiz while an old quiz review for it is open, and lanes never serve reviews that old, so KB013, KB040
  • Release An archived quiz review never holds a knowledgebase change
  • Build An archived quiz review never holds a knowledgebase change

2026-10-15

  • Confirmed report dashboard home (F0295) [/dashboard?section=Dev%20Tasks]: The sweep that gives every passed proposal a build order trusts any member-written task: a fake earlier order closes the real one, and a fake d
  • Confirmed report dashboard home (F0295) [/dashboard?section=Dev%20Tasks]: After a proposal's build is rejected, a second build order is created for it, because the sweep that gives every passed proposal an order does
  • Confirmed report dashboard home (F0295) [/dashboard?section=Dev%20Tasks]: A retry build order created after a rejection can never pass the origin gate, because the gate does not follow the retry back to its original o
  • Confirmed report dashboard home (F0293) [/dashboard?section=Dev%20Tasks]: Vote counting never checks whether a voter is eligible, so with a consensus size of one a single counted vote decides every outcome except a co
  • Confirmed report dashboard home (F0295) [/dashboard?section=Dev%20Tasks]: The order stages are listed separately in several places, so a new stage can be accepted in one and refused in another; this stopped every rele
  • Release A passed proposal's build order is keyed by the proposal; stalled adopted proposals show on the Heartbeat
  • Build A passed proposal's build order is keyed by the proposal; stalled adopted proposals show on the Heartbeat
  • Release A passed proposal keeps one build order line after a rejection
  • Build A passed proposal keeps one build order line after a rejection
  • Release Remove the "Already delivered" verdict; an overtaken proposal's order is closed with evidence
  • Build Platform-suspended DoD items, governed N/A reasons, the gate's English-only note and risk-based scoping on the review card
  • Build Remove the "Already delivered" verdict; an overtaken proposal's order is closed with evidence
  • Release The origin gate resolves a retry order to the order it retries
  • Build The origin gate resolves a retry order to the order it retries
  • Build Battle-test zkr-POGO: the test agent files planted items and known-answer cards; they never take effect; results are published
  • Release Every count applies the bootstrap reviewer list: the app's task tallies and both governance counts
  • Build Every count applies the bootstrap reviewer list: the app's task tallies and both governance counts

2026-10-14

  • Confirmed report dashboard home (F0295) [/dashboard?section=Dev%20Tasks]: Every approved builder-agent build is now refused at release: the release step does not accept an order that is awaiting release. — OBSERVED 20
  • Build The order stages are defined once and used by the app, the relay and the origin gate
  • Release An order awaiting release is still the build order: the release step and the origin gate accept it
  • Build An order awaiting release is still the build order: the release step and the origin gate accept it
  • Build The snapshot's master lists come from the individual files, and the gate fails on drift
  • Build The alignment gate checks every sitemap row's parent, not only in-page views
  • Build The alignment gate refuses a variable key with whitespace and a key-list entry with no row
  • Build Delivered only after release: approval closes the order as awaiting release
  • Build A verified commit that is no longer on its order branch is returned to the builder instead of stranded

2026-10-12

  • Confirmed report dashboard home (F0295) [/dashboard?section=Dev%20Tasks]: Rejecting a build leaves two open build orders for the same work, and whichever one gets delivered, the other stays pending forever. — Feature:
  • Confirmed report dashboard home (F0295) [/dashboard?section=Dev%20Tasks]: Approving any task that carries a feature id can create a fix order, even when the task is not a report review — a governance withdrawal reques
  • Confirmed report dashboard home (F0122) [/dashboard?section=Dev%20Tasks]: A governed variable's key has a sentence of description text appended to it, so the variable cannot be read by its name. — Feature: F0122 commu
  • Confirmed report dashboard home (F0295) [/dashboard?section=Dev%20Tasks]: When the release step finds the verified commit is no longer on its branch it refuses the build but does not return it to the builder, so the b
  • Confirmed report dashboard home (F0295) [/dashboard?section=Dev%20Tasks]: A build order is marked delivered the moment its verification passes, before the release, so a refused release leaves a 'delivered' order whose
  • Confirmed report dashboard home (F0314) [/dashboard?section=Dev%20Tasks]: Seven sitemap rows name a parent page that is not a sitemap row, so their place in the map cannot be resolved. — Feature: F0314 architecture re
  • Confirmed report dashboard home (F0314) [/dashboard?section=Dev%20Tasks]: The shipped master lists come from an aggregate file that drifts from the individual list files the control plane is edited in. — Feature: F031
  • Confirmed report dashboard home (F0002) [/dashboard?section=Dev%20Tasks]: The VR Mode page is live and linked from the phone menu although the control plane says VR mode is only a proposal that was never adopted. — Th
  • Confirmed report dashboard home (F0115) [/dashboard?section=Dev%20Tasks]: A subscription revenue test fails on every build since 2026-10-11 evening because its fixture carries a fixed expiry date that has now passed.
  • Release Only an approved report review can create a fix order; stray orders minted from anything else are closed as created in error
  • Build One rejection leaves one open order: the retry replaces the original, and rule R8 closes rejection chains minted before
  • Build Only an approved report review can create a fix order; stray orders minted from anything else are closed as created in error
  • Release Local-files test: scoped to the report's files — cache/compile-cache.json has been tracked since v7.7.28 and is outside it
  • Build Local-files test: scoped to the report's files — cache/compile-cache.json has been tracked since v7.7.28 and is outside it
  • Release Handle-dispute dialog: the import comment no longer names the banned package, so the pin test reads the code, not the prose
  • Build Handle-dispute dialog: the import comment no longer names the banned package, so the pin test reads the code, not the prose

2026-10-11

  • Confirmed report dashboard home (F0314) [/dashboard?section=Dev%20Tasks]: Three local tooling files were committed into the released app line by a control-plane snapshot build and are now tracked in main. — Feature: F
  • Confirmed report dashboard home (F0367) [/dashboard?section=Dev%20Tasks]: The handle dispute dialog shows translation key names (common.handleDispute.title …) instead of words. — Feature: handle dispute dialog (src/co
  • Build Heartbeat figures: a status family is matched by its leading word, so 'proposed (EAIP — community vote)' rows are never counted as present
  • Build Guardian: the known missing-sheet read for the Heartbeat is gone, so its allow-list entry shrinks away
  • Release Subscription revenue test: the fixture's term is relative to the clock, so the suite stays green on every date
  • Build Subscription revenue test: the fixture's term is relative to the clock, so the suite stays green on every date

2026-10-10

  • Confirmed report dashboard home (F0375) [/dashboard?section=Dev%20Tasks]: The regenerated knowledgebase quizzes keep offering statements a member cannot judge: sentences that point back at text they cannot see ('So th
  • Confirmed report dashboard home (F0295) [/dashboard?section=Dev%20Tasks]: A build the community approved can be stranded forever: when the release step refuses it on the origin gate, it retries the same commit on ever
  • Confirmed report dashboard home (F0124) [/dashboard]: A browser that already holds the shared state never receives a channel another member just created: its page says the channel could not be loaded within the read b

2026-10-09

  • Adopted proposal A node never starts with an accidental identity: the relay refuses to boot without a declared store, the guardian fails a store directory inside a repository, and KB014 records the rule
  • Adopted proposal EVRY's 24B cap holds on every chain: the bridge is lock-and-mint from Ethereum, its security check is an aggregation ISM with governed settings, and a supply-parity check is shown on the Heartbeat
  • Adopted proposal The DAO holds and renews evrylife.eth: custody moves to the DAO multisig with a time-lock at hand-off, and expiry and renewal are governed and warned about before the name can lapse
  • Confirmed report dashboard home (F0352) [/dashboard?section=Dev%20Tasks]: After a page load, the Dev lane holds a waiting build with 'the builder agent's governed address could not be read' and never serves it until t
  • Confirmed report dashboard home (F0184) [/dashboard?section=Dev%20Tasks]: The control plane records Spanish and French as 85% translated, but the real language files cover only two thirds of the English text (1,915 of
  • Confirmed report dashboard home (F0002) [/dashboard?section=Dev%20Tasks]: The wallet connector offers eight networks, but the control plane governs only Ethereum Mainnet, Ethereum Sepolia and Hyperlane, so members can

2026-10-08

  • Adopted proposal A filing shows its claim first: a governed soft limit on the body of a proposal or report, with a structured head the review card shows before the body
  • Adopted proposal Ending bootstrap must be threshold-gated and EAIP-governed — not a bare toggle (resubmitted from the owner's current account)
  • Adopted proposal The guardian fails a build that reads an ECP sheet the served ECP does not contain
  • Confirmed report dashboard home (F0002) [/dashboard?section=Dev%20Tasks]: Two approved builds can never be released: the release step refuses them every sweep with a control-plane conflict and nothing sends them back
  • Confirmed report explorer all (F0039) [/explorer]: The treasury page's fee table shows fees that contradict the governed fees, lists two fees twice with different values, and shows fees that no governed setting define

2026-10-07

  • Adopted proposal Make retired and publicly known keys inert: never listed as members, never served or counted, never trusted

2026-10-05

  • Adopted proposal Bot detection at the member level: flag automated behaviour to human reviewers, never punish by machine, never identify the person
  • Adopted proposal Battle-test zkr-POGO on a standing basis: planted harmful filings and known-answer cards, with every result published
  • Adopted proposal Make the verified-human badge earnable: choose a zero-knowledge proof of personhood by set criteria, and phase human-only actions onto it as coverage grows
  • Adopted proposal Stake is a threshold, never a multiplier: remove the stake term from community_score and correct the "stake-weighted" language in KB039 Article IV, KB006, KB047, KB034 and KB016
  • Adopted proposal Show and record the identity a write is ACTUALLY authored as, after wallet-link resolution
  • Adopted proposal Evry: the members' own assistant (AAG-006), with a DAO-funded free tier and the skills to set up, explore and manage an account
  • Adopted proposal Bind every build submission to an open task assigned to that builder
  • Adopted proposal Boot the client from a content-addressed snapshot instead of replaying the full oplog
  • Adopted proposal Session-two agent operating rules into KB013 / KB035 / KB045 — extends EAIP-060 with six failures it does not cover
  • Adopted proposal Agent reporting standard: separate what was OBSERVED from what was INFERRED, and try to falsify a mechanism before filing it as fact
  • Adopted proposal Remove the "Already delivered" verdict — it closes proposals without a community vote
  • Adopted proposal Every governed field must be enforced, documentation-only, or deferred — no silent fourth state
  • Adopted proposal Platform-suspended Definition-of-Done items: stop asking every reviewer to N/A the same thing (KB020)

2026-10-04

  • Adopted proposal A public change history: every verified build listed in plain words with its origin, and nothing that identifies a reporter or a reviewer
  • Adopted proposal A decentralized under-attack layer: the community's relays protect themselves with governed limits, and no company stands in front of the protocol
  • Adopted proposal Rotate the builder agent's governed address, and state that agents are not members
  • Adopted proposal A scoped, governed signing key for the builder agent only
  • Adopted proposal Handle integrity: every peer enforces the handle rules, one rule decides who owns a contested name, and look-alike platform names are covered
  • Adopted proposal Members' own storage and AI keys move into an encrypted vault that follows the member and survives a stolen wallet key
  • Adopted proposal During bootstrap, zkr-POGO review lanes are open only to the named bootstrap accounts
  • Adopted proposal Build reviewers can attach suggestions the builder must read and answer
Where this comes from: every figure on this page is generated at build time from the Evrylife protocol’s public control plane — ECP v7.7.338, 33 registries, 1,867 rows — read from a committed snapshot of the protocol's control-plane export. evrylife.org is an independent Foundation site that relays public protocol data: it is not a DAO-governed artifact and holds no protocol state of its own. Explanatory text is quoted from the public knowledgebase.