EGONOMIST

We invented counting to keep everyone fed, then turned the balance sheet into a battlefield.

Economics began as oikonomia—the simple, humble stewardship of a shared home. When ego took the pen, sharing became scoring, and counting became conquest. The math never shed a drop of blood; it is only the pride behind the balance sheet that demands a sacrifice.

Read the full poem

Research

Accumulated Findings

Review of Holochain We/Weave/Moss and similar programs. Properties considered for lgme.app. Compliant with egonomic restraint, third-seat refusal, constitutive tape, and Floor seniority.

Summary of findings

The September 2022 Holochain “We” demo (later The Weave / Moss) demonstrates an agent-centric, modular, fully decentralized groupware shell. Groups compose custom tools (applets) for collaboration without central servers. Key capabilities include opt-in participation, group-centric vs personal views, forking/walkaway, merging, federation, and cross-tool views. Related tools such as hREA provide Resource-Event-Agent accounting for value flows and mutual credit. These features can support lgme.app’s mutual-credit and provenance goals while respecting egonomic principles: no speculative minting, visible tape, third-seat control, and Floor-first rules.

Listed findings with egonomic commentary

1. Agent-centric opt-in

Users decide which groups and tools to join. No top-down membership.

Egonomic comment: Aligns with third-seat refusal and sovereignty. The person keeps the book and can refuse any line. No forced participation. Supports Schelling-style self-management and Marcum/Smith humility (no comparative pressure to join).

2. Modular applets / tools for recording work

Composable modules for chat, notes, calendars, value tracking, etc. Groups add only what they need.

Egonomic comment: Useful for IdidIt-style civic work recording and mutual-credit ledgers. Must remain visible on the constitutive tape. Unpublished change is not a change. Avoid high-ego “showcase” modules.

3. Forking and walkaway

Groups can split or individuals can exit and reconstitute without permission.

Egonomic comment: Supports restraint and exit as a check on ego-driven hierarchy. Seat symmetry preserved. No locked-in power. Aligns with Schelling precommitment against future self-override.

4. Group-centric vs agent-centric views

View shared group data or personal cross-group aggregation of one’s own records.

Egonomic comment: Reinforces that the third seat (the person) keeps the book. Personal view of credits/work across circuits without subordinating Floor seniority.

5. Opt-in membranes and consent-based boundaries

Membership and visibility rules accepted by agents rather than imposed.

Egonomic comment: Default-closed. Changes must be published on the tape. Supports veracity and barrier checks. No private paths.

6. REA-style resource-event-agent flows (hREA)

Track resources, events, and agents for transparent value flows and mutual credit without global consensus.

Egonomic comment: Strong fit for mutual credit of recorded work. No speculative mint. Floor remains senior; any residual titled only after barrier checks and named surplus. Avoid comparative leaderboards that trigger ego liability.

7. Federation / linking of groups

Interoperability between local groups under shared patterns while keeping local sovereignty.

Egonomic comment: Compatible if all linking rules appear on the public tape and local third-seat refusal is preserved. No central override.

8. Composable, visible rule sets (precommitment devices)

Groups encode their own barrier checks and governance rules as first-class visible elements.

Egonomic comment: Direct support for Schelling egonomics (precommitment) and constitutive tape. Rules must be shown; an unpublished change is not a change. Floor stays senior.

Added 4 November 2026

9. Group-chosen tool curation (Moss 0.15.7)

Moss 0.15.7 (June 2026) lets each group choose the curation lists that feed its Tool Library instead of relying on a single curator, and makes group home pages tile-based dashboards the group composes itself.

Egonomic comment: Removes a single point of curation, so no central seat decides what a circuit may use. Compliant with seat symmetry and sovereignty if each circuit’s chosen sources are published on the tape. Dashboards must stay plain records of work, not showcases; avoid brilliance-seeking tiles and member highlight reels.

10. Coordinated upgrades with export/import (Moss 0.16, Holochain 0.7)

All fifteen Lightningrod Labs Moss tools moved to Holochain 0.7.0, a new network that cannot see 0.6 peers. Groups are told to upgrade together, with per-tool export/import to carry data across; the old version keeps working so nobody is stranded. Moss 0.16 is still pre-release (rc.2, 22 October 2026).

Egonomic comment: A clean model of constitutive tape: a version change takes effect for a group only when it is published and adopted together, never silently. Export keeps the book with the person and preserves walkaway. Precommitment fit: pin versions and refuse an upgrade that would fork the network for nothing. lgme.app should require a published, dated migration note and a working export before any ledger format change.

11. Hidden presence (Moss 0.15.4)

Members can hide themselves from a group’s online-status list.

Egonomic comment: Default-closed applied to presence. Removes acceptance-seeking and comparative pressure to look active. Presence is not work; only recorded, published work enters the ledger. Recommend presence off by default in lgme.app.

12. Matrix 2.0 pieces, federated calendar, and P2P Matrix

In late October 2026 Matrix accepted MatrixRTC (MSC4143, federated end-to-end encrypted calls), Sticky Events (MSC4354), and Sliding Sync extensions, with Matrix 2.0 to follow. MSC4569 proposes federated calendaring. Matrix 1.19 (July 2026) added encrypted room-history sharing. Element-funded P2P Matrix and Decentralised MLS research aim at serverless, metadata-private rooms. Matrix’s Hydra work also makes room creators explicitly privileged (MSC4289).

Egonomic comment: Matrix is a candidate transport for circuit messaging and scheduling, not for the ledger. Encrypted history sharing must be opt-in per circuit (default-closed). Caution: a privileged creator seat conflicts with seat symmetry, so if lgme.app ever bridges to Matrix, circuit rules must live on the lgme tape, not in Matrix power levels. P2P Matrix is worth watching for sovereignty; it is still research, not a release.

13. Linked Web Storage 1.0 (successor to Solid)

The W3C Linked Web Storage Working Group published a new LWS 1.0 Working Draft on 23 October 2026. It aims to decouple storage, identity, access control, and app provider so a person can change one without losing past data. A Solid compatibility and migration note is an open work item; the charter runs to 8 January 2027.

Egonomic comment: Strong fit for third-seat refusal: the person keeps the book in storage they choose, and lgme.app becomes one client among many. Still a draft, so treat it as a target for an export format rather than a dependency. Do not claim compatibility until it is shown.

14. Zero-start mutual credit validation (hREA pattern)

hREA’s mutual-credit design notes (issue #166) specify accounts initialised at zero, one account per agent per currency, transfer-only events after creation, and credit limits set as network properties. hREA (Valueflows on Holochain, v0.3.x) leaves these as an extension rather than a ready product.

Egonomic comment: The clearest available rule set against speculative minting: balances arise only from recorded transfers, and every account sums to zero across the circuit. Credit limits as published network properties are a Schelling precommitment device. Floor stays senior: limits and any residual are set only after barrier checks and appear on the tape. Avoid balance leaderboards.

Added 5 November 2026

15. Nested, sovereign mutual-credit ledgers (Credit Commons Protocol)

The Credit Commons Protocol connects independent mutual-credit ledgers in a tree: each group keeps its own ledger, unit, limits, and governance; balances on every intermediate ledger sum to zero; ledgers stay in step through hash-chained mirror accounts; and each transaction has a validate phase (nothing written) before a write phase on the person’s confirmation. The 2020 proof of concept is deprecated and a beta API and reference implementation are in development. TimeOverflow (time banks) opened a proposal in May 2026 to federate its instances this way. Open problems the protocol itself names: ordering of simultaneous transactions, a node going offline between validate and write, and rounding across units.

Egonomic comment: Strong fit for mutual credit of recorded work with no speculative mint: there are no goods on the ledger, only credit and debt that sum to zero. Each circuit stays sovereign over its own limits, which preserves seat symmetry between circuits. Validate-then-confirm is third-seat refusal built into the transaction: nothing is written until the person accepts the line. The hash chain on each hop is constitutive tape between circuits. Caution: the proposed fix for ordering lets the trunkward node decide write order, which is a privileged seat; any such rule must be published and limited to ordering, never to amounts or membership. Floor stays senior: inter-circuit credit limits are set only after barrier checks.

16. Local-first access control with a relay-only seat (Keyhive)

Ink & Switch’s Keyhive adds capability-based access control and end-to-end encryption to Automerge and other CRDTs, without relying on a server boundary. Members hold one of four levels: relay (can sync encrypted bytes but cannot read), read, edit, or admin, with delegation and revocation. The JavaScript integration (automerge-repo-keyhive) reached v0.7.0-alpha.1 on 13 October 2026 and is still alpha. In September 2026 Keyhive published a written threat model listing known gaps between design and code, and Automerge changes can now record an author identity that survives merging.

Egonomic comment: The relay level is default-closed made concrete: a helper can carry a circuit’s book without being able to read it, so hosting never becomes a third seat. Revocation that works offline supports walkaway. Recording the author on each change, not just a session, is veracity on the tape. The published threat model, including what it does not protect, is an example of humility and veracity over brilliance-seeking claims. Caution: an admin level is an unequal seat; if lgme.app adopts this pattern, admin powers must be limited to published, rule-bound actions and held symmetrically. Alpha status means watch, do not depend.

17. Oblivious support nodes (p2panda and Willow “Pillow”)

p2panda and the Willow team (Worm Blossom), funded by NLnet NGI Zero Commons, announced in August 2026 that p2panda will use Willow nodes as “support nodes”: more-available peers that keep encrypted blobs for a set time and amount of space, with access managed by Meadowcap capabilities. The work is called “Pillow” and is in the user-story stage, with no release yet. p2panda’s latest release is v0.7.1 (21 August 2026); group encryption and multi-device group management are planned for v0.8.

Egonomic comment: Availability without authority: a support node holds what it cannot read, for a bounded time and space it publicly agreed to. This answers the practical need for always-on storage without making the host a third seat or a senior party over the Floor. Time and space limits are a precommitment that stops the helper from growing into a custodian. Not yet released; record as a design pattern only.

18. Published status separate from commitments (Holochain roadmap, 0.7.1 stable)

Holochain 0.7.1 became the stable release on 14 October 2026, and 0.8.0 development builds continue weekly (dev.14 on 2 November 2026). Holochain publishes a weekly roadmap snapshot pulled from its internal tracker that states plainly it shows status, not firm commitments; current work includes an iroh-based network transport and performance testing.

Egonomic comment: A useful habit for lgme.app’s own status page: show what is actually done and what is in progress, and label plans as plans. That is veracity and humility over acceptance-seeking promises, and it keeps the tape honest: a plan is not a change until it is shipped and published. Moss groups on 0.7.x can stay pinned to stable while 0.8 matures, consistent with yesterday’s version-pinning recommendation.

Added 5 November 2026 (evening)

19. lgme.app mutual-credit simulator (Komunitin zero-sum + mock HCS)

Cryptobusi/lgme added a client-side Sovereign Provenance & Mutual Credit Simulator at mutual-credit-simulator.html (commit dec8453, 5 Nov 2026 evening America/Indianapolis). The page is published at lgme.app/mutual-credit-simulator (and lgme.vercel.app) as simulation and design research only; hederica.com does not yet host or link it. There is no real HCS submit and no on-chain activity. The page runs a three-node Komunitin-style ledger that stays at net zero, rejects trades past each node’s published credit limit, hashes a key-sorted payload with Web Crypto SHA-256, and shows Hedera HCS topic 0.0.489104 as a mock label only, while sequence numbers and “consensus” stay entirely local. The header badge reads Mock Simulation Mode. RFC-8785/Ed25519 appears as a pipeline label; the page does not perform a real Ed25519 signature. Export writes a markdown audit; “Index for hederica.com” writes a deployment manifest to localStorage only. That hederica index and manifest are the same mock: design research, not a Hedera record.

Egonomic comment: Strong fit, as design research only, for mutual credit of recorded work: balances move only by double-entry transfer, the circuit sum stays zero, credit limits are published barriers, and each line carries a provenance string rather than a mint. Mock Simulation Mode is veracity: the simulator and the hederica index/manifest are simulation only, with no real HCS submit and no on-chain activity. Constitutive-tape direction inside the mock is right (hash, stream, export, mock topic label), but third-seat refusal is incomplete while one click auto-settles both seats with no validate-then-confirm step, and claiming completed Ed25519 without signing fails veracity until the sign is real or the label says simulated. Floor seniority is not in this demo and must stay outside it. Prefer restraint over “zero-friction” copy. Sovereignty holds while the book and export stay with the person. The topic id is a label in the mock, not a public tape and not a senior seat.

Added 6 November 2026

20. ValueFlows 1.0 integrity on Holochain (hREA happ-0.5.0-beta.1)

hREA released happ-0.5.0-beta.1 on 10 September 2026 for Holochain 0.7 and ValueFlows 1.0. Earlier betas mostly stubbed validators; this release enforces required strings, temporal ordering, quantity bounds, the 21-id action vocabulary, collection bounds, and immutable-on-update fields, rejecting writes that 0.4.0-beta accepted with a message that names the rule. Economic events are append-only by design: there is no deleteEconomicEvent; corrections use a compensating event. Claims, offers/requests queries, settlement links, and reciprocal realization fields land with the schema. The DNA hash changes, so 0.5 is a new network with no in-place migration from 0.4. Interfaces are described as compatible with other ValueFlows backends such as Bonfire. Measured tests on the release commit: 47 Sweettest cases and 71/71 GraphQL acceptance steps green.

Egonomic comment: Strong fit for mutual credit of recorded work: balances and claims move only through validated events, not silent edits. Append-only events with compensating corrections are constitutive tape. Named rejection messages are veracity and humility over brilliance-seeking “it just works” writes. Floor stays senior: credit limits and any residual remain circuit properties set after barrier checks, not hREA defaults. Seat symmetry holds if every agent faces the same integrity rules. Still beta; treat as a pattern to copy into lgme.app’s mock and future ledger, not a dependency. No speculative mint.

21. CES2 live on Komunitin (Community Exchange Network)

The Community Exchange Network’s May 2026 newsletter reports CES2 live at app.ces.community with pilot groups in England and the United States (HUMA Network), built on Komunitin open-source mutual-credit software (AGPL-3.0) that CES adopted as the CES2 starting code. The upgrade news (July 2026) names partners including Komunitin, TimeOverflow, Credit Commons, Open Coop, and Murmurations. CEN frames itself as non-monetary, non-crypto, and non-commercial, counting roughly 11,000 active users across member platforms, and is testing consent-based (sociocratic) decision-making for network governance. A core-service rebuild aims to drop the last Drupal-era dependency and enable federation between communities. lgme.app’s mutual-credit simulator already uses a Komunitin-style zero-sum pattern as simulation-only design research.

Egonomic comment: A live reference for mutual credit of recorded work without speculative minting or featured tokens. Circuit-scale UX (notifications, community pages, QR/NFC direction) is worth studying while keeping lgme’s simulator labeled Mock Simulation Mode. Consent decision-making matches Schelling restraint better than brilliance-seeking majority theatre. Caution: hosted CES2 remains a service seat; sovereignty needs person-held export and third-seat refusal on every write. Floor seniority is not automatic in CES products and must stay explicit in lgme.app. Interop interest with Credit Commons aligns with finding 15 but must keep trunkward nodes limited to published ordering rules, never amounts or membership.

22. Jazz v2: sync authority versus local-first permissions

Jazz (jazz.tools) published “What we learned from classic Jazz” on 17 April 2026. Classic Jazz (v0.x) used cryptographic local-first permissions and CRDT history; Jazz v2 makes the Jazz server (“Core”) a trusted authority that enforces permission policies at sync time, keeps classic Jazz maintained for migration, and replaces heavy CRDT replay with a git-like snapshot DAG. Sync docs describe query subscriptions, local IndexedDB replicas, offline queues, and last-writer-wins with hybrid logical clocks for concurrent field conflicts. Sensitive fields may still use encrypted columns with keys shared between end-user devices so Core cannot read them.

Egonomic comment: Useful cautionary finding. A trusted Core that accepts or rejects writes is a third seat over the book and conflicts with third-seat refusal and sovereignty if applied to the ledger. Prefer Keyhive-style relay-only hosts (finding 16) and person-confirm two-phase writes (finding 15) for circuit balances. Encrypted columns for sensitive notes are default-closed and fine. Snapshot history and honest LWW labeling support constitutive tape if every accepted write still shows who authored it. Do not import Jazz’s server-as-authority model into lgme.app’s mutual-credit path; the simulator must stay mock and person-held.

23. Append-only transparency receipts (IETF RFC 9943 SCITT)

IETF RFC 9943, “An Architecture for Trustworthy and Transparent Digital Supply Chains,” was published as a Proposed Standard in June 2026 (SCITT). Issuers produce signed statements about artifacts; a Transparency Service applies a published registration policy, appends to a verifiable data structure that must be append-only, non-equivocating, and replayable, and returns a COSE receipt (see also RFC 9942). Relying parties can verify inclusion without trusting a single operator forever; multiple independent transparency services may co-sign the same statement. Payloads may be detached or hashed so sensitive content need not sit in the log. Aimed at software supply chains first, but framed as content-agnostic for other value-add graphs.

Egonomic comment: Strong constitutive-tape pattern: an unpublished change is not a change; a receipt proves the line was registered under a named policy. Registration policies themselves must appear on the log—Schelling precommitment made concrete. Non-equivocation is veracity. Caution: a Transparency Service is still a seat; for lgme.app prefer circuit-local or person-mirrored logs, relay-only hosting, and optional SCITT-style receipts for published work or provenance exports rather than a global mint or senior Floor override. Compatible with mutual credit of recorded work if statements describe completed transfers, never speculative issuance.

24. Moss maturity: in-artifact comments, share annotations, crash recovery

On 28 October 2026 Lightningrod Labs described three “maturity” pieces now in Moss 0.16.0-rc.3 (Notebooks 0.8.0, Presence 0.17.1): Google-Docs-style comments in Notebooks whose ranges are Automerge marks so concurrent edits keep the highlight; Presence freehand annotations on share tiles over the existing signaling path; and Moss watchdog plus leftover lair/conductor cleanup so a crashed session no longer bricks the next launch. GitHub also lists 0.16.0-rc.4 (3 November 2026) on Holochain 0.7.1-mdns.8. Still a release candidate: groups must be re-created for the final release and peers need the same Moss version.

Egonomic comment: Engagement on the artifact without leaving the room supports recorded work and restraint (talk about the line, don’t showcase the author). Comment export as CriticMarkup keeps discussion on a portable tape. Crash recovery is sovereignty over the local book—no silent third seat. Presence strokes are ephemeral coordination, not ledger entries; keep presence/annotation off the mutual-credit tape. Pre-release: pin versions; unpublished RC is not production policy.

25. Atmospheric groups (AT Proto opensocial.group)

On 22 October 2026 the AT Protocol blog introduced atmospheric groups via the opensocial.group proposal: a group is its own DID with permissioned Spaces under it; groups migrate across hosts; the same group works across apps (demoed in grain.social and pdsls). Member data stays on member PDSes (writer sets); the group host tracks repos and roles and routes write notifications but does not hold member payloads. Membership is mutual (group membership record + member acceptance). Permissions are flat RBAC; the group host can act as OAuth for group-DID writes scoped by role.

Egonomic comment: Strong third-seat / sovereignty fit if member books stay on member storage and the host is not a mint. Cross-app reuse without re-inviting is Schelling restraint against ego-driven re-founding. Caution: admin roles and host-issued credentials are unequal seats—publish role powers on the tape, hold them symmetrically, and keep circuit credit rules on the lgme tape, not in host RBAC. Watch, do not depend; proposal stage.

26. Solid makes WAC the required access-control baseline

On 5 November 2026 the Solid specification merged pull request #824 (closing issue #787): a conforming Solid server now MUST implement Web Access Control (WAC), Access Control Policy (ACP) becomes optional (MAY), and clients are no longer required to speak ACP. Before this, a server could pick either or both, so a pod’s sharing rules were not guaranteed to move with the data from one server to another. This is an editor’s-draft change in the protocol text, not a new Recommendation.

Egonomic comment: One required, plain access format is seat symmetry and sovereignty in practice: a person who moves their book to another host keeps the same sharing rules instead of depending on one vendor’s policy engine (no hidden third seat). WAC lists are readable files, which suits constitutive tape when the list itself is published. Default-closed holds only if lgme starts every book with no grants and adds them by explicit, recorded acts after barrier checks. Schelling restraint: choosing the smaller common baseline over the more expressive option is a precommitment worth copying. Editor’s draft only; claim compatibility once shown.

27. Local-first Solid client stack: muze margin notes

On 4 November 2026 Auke van Slooten of muze.nl announced a first complete client-side Solid stack and the margin-notes example app. Data lives in the browser (IndexedDB) by default and syncs to a Solid pod only when the person connects one. Parts are published separately: solid-workspace and metro-oldm (muze-labs/solid-tools), oldm (an object-to-linked-data mapper), metro (an HTTPS client with OIDC and OAuth 2.1 middleware), and jsfs (a filesystem abstraction). The whole app is about 200 KB minified, 100 KB gzipped, with an experimental Turtle-only parser to trim the N3 dependency. An accompanying book, Programming for Wizards, explains the design.

Egonomic comment: Strong third-seat fit: the person keeps the book on their own device and chooses whether and where to sync; no server is needed to start recording. Small, separable parts support Schelling restraint and walkaway (any piece can be swapped without re-founding). Caution: local-only work is not yet on the tape; lgme should mark local entries as drafts and treat a line as made only once it is published to the circuit. Annotations on shared text fit the in-artifact deliberation recommendation from 6 Nov. Early first version; study, do not depend.

28. Matrix proposals: shared encrypted search indexes and versioned account data

This Week in Matrix for 6 November 2026 listed new spec proposals, among them MSC4578 (cross-client shared search indexes of encrypted messages), MSC4573 (atomically increasing versioned account data), MSC4574 (linked state events), MSC4575 (a MatrixRTC full-mesh transport), and MSC4576 (letting non-call apps such as Neoboard use MatrixRTC data channels). None is accepted yet; the Spec Core Team is still finishing the Matrix 2.0 set. The same issue reports a new Widgets Working Group and Arminius, a Famedly/BWI enterprise homeserver published in the open but marked not ready for use.

Egonomic comment: Versioned, atomically increasing records (MSC4573) match constitutive tape: each change gets the next number or it did not happen, with no silent overwrite. Shared encrypted search indexes help a person find their own record across devices, but an index built by one client and trusted by others is a quiet third seat; keep any index person-held and rebuildable from the book. Full-mesh transport reduces dependence on a central media server (sovereignty), but presence and calls remain coordination, not recorded work. Proposals only; per the 4 Nov recommendation, Matrix stays transport, not ledger.

Added 8 November 2026

29. User-supplied Prior Signal memory synthesis (simulation mappings only)

A user-supplied “Video Transcript Breakdown & Synthesis” of the Prior Signal video “Something Is Happening to Human Memory — And It Started the Day We Learned to Write” is published in full below and on Memory and sovereign records. The supplied text has seven timestamped sections, from 00:00:00 through 02:07:28, a four-row failure-mode table, six numbered protocol actions, and the closing motto. No video URL was supplied. This entry does not verify the transcript, does not treat the historical or neuroscience numbers as established evidence, and does not claim the video was watched. The supplied sentence that lgme.app “implements” a ledger “anchored to” HCS is retained as a proposal. All lgme experiments remain strictly simulation only: no Hedera HCS submit, no on-chain activity, and no manifest on a chain. No Holochain integration; earlier Holochain notes stay methods only. A potential future network is EVM on Hedera testnet, not mainnet. This entry does not implement the protocol.

Egonomic comment: Floor stays senior. The person keeps the book and refuses before commitment; a later NO cannot undo a finalized line, so a correction is an appended record. An unpublished change, including an offline receipt, is not a change. Seat symmetry, barrier checks, and default-closed still bind. Schelling precommitment applies to any decay window: it must be agreed in advance, stay zero-sum, stay auditable, and must not become erasure, forced labor, or a mint. Marcum and Smith humility, curiosity, and veracity apply: no comparative brilliance, no approval seeking, and the supplied claims stay attributed. Recorded-work mutual credit does not become speculative issuance. “Third Seat” in the supplied actions is the human right of refusal, not a new authority over the person. A hash chain is not itself a Merkle inclusion proof, and a receipt does not guarantee that the archive remains, that the payload is true, or that every rewrite is impossible. Sovereignty is the refusal.

Full user-supplied synthesis and six recommendations

Attribution

The breakdown, the table, the six recommendations, and the closing motto are user-supplied video synthesis. They are not an independently verified transcript. They are not established here as scientific evidence. No video URL was supplied, so this page does not link to a video and does not imply that the video was watched.

Video Transcript Breakdown & Synthesis

The video "Something Is Happening to Human Memory — And It Started the Day We Learned to Write" from Prior Signal traces the cognitive and institutional evolution of memory across four primary axes:

[00:00:00 - 00:10:05]The Socrates-Thamus Dilemma & The False Paradox of Writing
  • In Plato's Phaedrus (Stephanus 275a), King Thamus rejects writing: it is not a drug for remembering, but for reminding, offering the appearance of wisdom without reality.
  • The standard reading calls Thamus a tech-panicker; laboratory testing shows his mechanism was accurate.
  • The 5,000-year trade was positive because external memory historically possessed one crucial trait: "Every previous version could walk out of a burning building."
[00:10:06 - 00:25:35]Oral Epics & Biological Error Correction
  • Milman Parry & Albert Lord study Avdo Međedović (illiterate butcher in 1935 Montenegro).
  • Dictated a 12,323-line epic (length of the Odyssey) over 5 days; expanded a 2,294-line song to 6,313 lines.
  • Conclusion: Not rote playback, but an internal generative system of formulas, themes, and metrical syntax.
  • Oral Rigveda (1500 BCE) survived 3,000 years without manuscript variants using graded permutation recitations (Samhitapatha, Padapatha, Kramapatha, Jatapatha, Ghanapatha) — an error-correction checksum executed directly in human nervous systems.
[00:25:36 - 00:47:19]Transactive Directories & The Offloading Trap
  • Daniel Wegner (1986, 1995): Transactive memory in couples divides labor; brains store directories/pointers rather than content. Extended to computers: if retrieval is assumed reliable, encoding drops.
  • Sam Gilbert & Evan Risko (2016): Cognitive offloading causes over-reliance. People systematically underestimate their own memory capacity, defaulting to external devices in a self-reinforcing downward loop.
[00:47:20 - 01:00:28]Physical Structural Atrophy
  • Eleanor Maguire (2000, 2006, 2011): London black cab drivers mastering "The Knowledge" (25,000 streets) showed physical gray matter growth in the posterior hippocampus. Fixed-route bus drivers showed none.
  • Véronique Bohbot (2020): Habitual GPS use shifts navigation from the hippocampus (cognitive mapping) to the caudate nucleus (stimulus-response), correlating with accelerated hippocampal decline.
[01:00:29 - 01:17:39]Collective Memory & The Sliding Void
  • Jan Vansina (1961, 1985): Historical consciousness in oral societies operates on only two registers: "Time of origin" and "Recent times." In between lies the "Floating Gap" (~80 years / 3-4 generations) which slides forward continuously as living eyewitnesses die.
  • Laura Bohannan (1952) & Jack Goody (1963): "Structural Amnesia" — unanchored oral history actively rewrites itself to justify the present power/property layout, quietly deleting the edit trail.
  • Candia et al. (Nature Human Behavior 2019): Collective memory exhibits biexponential decay: fast communicative decay (5–30 yrs) transitioning into slow cultural archive decay.
[01:17:40 - 01:39:42]The Institutional & Philosophical Counter-Arguments
  • Progressive education (John Dewey) eliminated recitation drills in favor of "understanding," yet cognitive science (Roediger & Karpicke testing effect, Sweller's cognitive load) shows working memory requires pre-consolidated internal chunks.
  • Clark & Chalmers (1998) "The Extended Mind" (Otto's notebook) argued mind includes coupled tools.
  • Vulnerability of the Extended Mind: It assumes the notebook is permanently accessible, offline, and free of rent.
[01:39:43 - 02:07:28]The 2002 Substrate Crossover & The Immobile Archive
  • Hilbert & Lopez (Science 2011): In 1986, 1% of stored data was digital; in 2000, 25%; in 2002, >50%; by 2007, 94-97%. 2002 was the silent crossover where memory changed substrate.
  • The Inverted Longevity Curve: Clay (4,000+ yrs) -> Parchment (1,000+ yrs) -> Magnetic Tape (10-30 yrs) -> HDDs (3-5 yrs) -> SSDs (unpowered charge loss).
  • Web link rot: Pew Research (2024) found 38% of web pages from 2013 vanished by 2023. Harvard Law found 50% of Supreme Court citation URLs are dead.
  • The Alexandria Lesson: Alexandria didn't burn overnight; it decomposed when maintenance funding ceased.
  • Our archive cannot walk: It lives in buildings requiring continuous power, software compatibility, corporate solvency, and cloud subscriptions. The index is useless if the target vanishes.

Concrete Points to Make the lgme.app Process More Successful

Supplied proposal, retained verbatim

lgme.app implements the Sovereign Provenance Protocol (SPP) as an auditable mutual credit engine and civic ledger anchored to the Hedera Consensus Service (HCS). The structural failure modes detailed in the documentary point directly to where decentralized accounting platforms hit friction and how to overcome them.

Supplied table headers were “DOCUMENTARY FAILURE MODE” and “LGME.APP IMPLEMENTATION SOLUTION”. The solution column is labeled here as a proposed/simulated mapping so those cells are not read as shipped or live behavior. The cell text is the supplied wording.
Documentary failure modeSupplied header: DOCUMENTARY FAILURE MODEProposed / simulated mappingSupplied header: LGME.APP IMPLEMENTATION SOLUTION
The Immobile Archive & Bit Rot (Cloud servers decay, URLs 404)Pure Event Sourcing over HCS Topics (Self-contained, deterministic logs)
Structural Amnesia & Genealogies (Ledgers quietly rewritten by power)Unalterable HCS Sequence & Consensus (Non-repudiable state transitions)
The Generative Engine vs Container (Avdo's dynamic formulaic production)Generative Bilateral Clearing (Multi-path credit clearing graphs)
Cognitive Offloading Trap (Users lose agency & self-trust)The "Third Seat" Friction Guard (Programmatic refusal / explicit NO)
  1. Decouple Application State from Ephemeral Cloud Hosts (Pure Event Sourcing)

    The Insight: Digital memory rots because it relies on centralized host maintenance, database servers, and active domain renewals. When maintenance stops, state disappears.

    Protocol Action: Treat HCS not as a query database, but as a pure append-only event-sourcing ledger. Ensure the browser runner in lgme.app can reconstruct full participant balances, mutual credit limits, and provenance chains directly from the raw chronological message stream of an HCS topic ID without relying on an intermediary backend database or proprietary API server. If the server hosting lgme.app goes offline, any user running a single local client file must be able to replay the topic messages from a public mirror node and restore the ledger state immediately.

  2. Prevent Algorithmic "Structural Amnesia" with Merkle Proofs

    The Insight: As shown by Bohannan's Tiv genealogies, unanchored records rewrite historical allocations to conform to current power dynamics and silently bury the revision history.

    Protocol Action: Every state transition in lgme.app (credit issuance, deed notarization, mutual clearance) must embed the cryptographic hash of the previous state block in the HCS submission. A participant's historical balance can never be retroactively restated or "haircut" by a platform administrator because any divergence breaks the chain of consensus hashes.

  3. Build an "Oral Formulaic" Generative Engine for Local Value

    The Insight: Avdo Međedović demonstrated that true memory is generative fluency—assembling pre-structured formulas into novel realities at performance speed, rather than querying static files.

    Protocol Action: Modern users cannot sit down and configure custom bilateral smart contracts from scratch. lgme.app should supply standardized, modular economic primitives ("formulas" such as recurring reciprocal hours, emergency barter pledges, care work clearance, local tool-lending escrow). Users snap these primitives together to generate liquid, multilateral clearing rings dynamically, lowering the barrier to entry without diluting sovereignty.

  4. Design Offline-First, Portable Local Records ("Memory That Walks")

    The Insight: The central finding of the documentary is that memory survives collapses only if it can walk with an individual. A protocol tied exclusively to always-on fiber-optic broadband is fragile.

    Protocol Action: Implement local client-side cryptographic storage (IndexedDB / encrypted local keystore) paired with peer-to-peer transport (Bluetooth Low Energy / local Wi-Fi via Libp2p or QR-code exchange). Two users must be able to sign, attest, and clear a mutual transaction offline in a disconnected environment, generating signed transaction receipts that walk out with them on their devices and queue for batch submission to HCS once network connectivity resumes.

  5. Counteract Cognitive Offloading with the "Third Seat"

    The Insight: Gilbert and Risko showed that offloading causes users to lose confidence in their own faculties, creating a spiral of blind submission to the automated machine.

    Protocol Action: The "Third Seat" (the human participant's programmatic right of refusal) must not be buried behind dense technical jargon or nested modal menus. Provide prominent, friction-conscious feedback: whenever an automated balancing routine, fee, or clearing step occurs, the interface must surface a plain-language receipt highlighting what changed, accompanied by an explicit, accessible one-touch veto (NO). Retaining friction at moments of sovereign settlement preserves active human agency and prevents passive platform capture.

  6. Neutralize the "Floating Gap" in Collective Community Credit

    The Insight: Vansina documented how social systems retain the immediate past (~3–4 generations) and the distant origin, while the intermediate history evaporates. In mutual credit, debt relationships that linger unaddressed across extended periods either cause social resentment or get quietly abandoned.

    Protocol Action: Hardcode deterministic lifecycle decay and bounded clearing windows into lgme.app mutual credit lines. Outstanding imbalances should not sit indefinitely in an unmonitored purgatory; they must follow automated settlement cadences (settle via labor, offset via circular clearing loop, or execute systematic source unwinding under agreed mutual credit parameters). Keeping credit active and bounded prevents stagnant debts from slipping into an unaccountable void.

Floor stays senior. If it cannot be shown, it is not policy. Sovereignty is the refusal.

Supplied closing motto

Separate from the supplied text

Technical and egonomic review

The commentary in this section is the site’s review. It does not replace or silently correct the supplied wording above. Historical, neuroscience, numerical, and causal claims in the synthesis, and the media-lifetime comparisons, are attributed claims. They need primary-source verification. They are not established on this page.

Technical limits of the supplied mappings
  • Hash chaining is not itself a Merkle inclusion proof. Supplied action 2 asks each transition to embed the hash of the previous state. That can show a linear chain of recorded hashes. It does not, by itself, prove Merkle inclusion of a balance, and a receipt of that hash is not an inclusion proof.
  • Consensus and receipts do not guarantee archive availability. They do not establish authenticity in the sense of truth. They do not prevent every rewrite. A later appended record can correct an earlier line. A mirror that stops serving history can leave a receipt with nothing left to read.
  • Offline receipts are provisional pending reconciliation, including double-spend checks and credit-limit checks. A signature made while disconnected is not yet a finalized line on the tape.
  • A later NO cannot reverse an event that has already been finalized. Refusal comes before commitment. After finality, a correction is an appended record.
  • Deterministic debt decay has to be explicitly agreed in advance. It has to preserve zero-sum accounting, Floor seniority, audit, and the person’s refusal. It is not unilateral erasure, not forced labor, and not speculative issuance.
  • In the supplied actions, “Third Seat” means the human right of refusal. It does not name a new authority over the person.
Egonomic principles applied to this material
  • Floor stays senior. Clearing windows, escrow primitives, decay, and any residual sit under the Floor. If a cadence cannot be shown, it is not policy. The Floor is not spent to make a simulation look settled.
  • Third-seat refusal, and the person keeps the book. The one-touch NO is the person’s refusal, used before commitment. The local record and the export stay with the person. The Third Seat is that refusal. It is not a clerk, a host, or an office set over the person.
  • Constitutive tape. An unpublished change is not a change. A local draft, an offline receipt, a mock hash, and a proposal to anchor a log are not policy until they are published on a tape the others can open.
  • Seat symmetry. The same hash chain, the same limits, the same published cadence, and the same refusal bind the state, the firm, and the person. No administrator’s quiet restatement is a senior seat.
  • Barrier checks. Credit limits, clearing windows, and any decay parameters are barriers. They are set only after they are shown. A formula primitive does not skip the barrier.
  • Default-closed. No grant, no sync, no host read, and no automatic settlement opens until a recorded act opens it. An offline exchange is between the people who sign it.
  • Schelling precommitment and restraint. A decay window, a credit limit, and the rule that refusal comes before commitment are precommitments. They restrain a later self, and a later administrator, from quietly rewriting the book. The smaller published rule is the one that can be kept.
  • Marcum and Smith: humility, curiosity, and veracity. No comparative brilliance and no approval seeking. This page does not claim the video was watched, does not treat the supplied numbers as established, and does not rank circuits or members. Mock steps stay labeled mock. Curiosity leaves the primary sources open for later verification.
  • Recorded-work mutual credit, not speculative minting. Reciprocal hours, care-work clearance, barter pledges, and tool-lending escrow record work or an explicit pledge. They do not mint a unit to fill a gap. Balances, where simulated, move by transfer and stay zero-sum.
  • Sovereignty. The person can walk with the local record and can refuse a line. Sovereignty is the refusal.

Recommendations under consideration

  • Adopt agent-centric opt-in and third-seat refusal as core interaction model.
  • Implement modular recording tools for civic work and mutual credit, all changes published on the tape.
  • Support forking/walkaway to preserve exit and restraint.
  • Explore REA-style flows for value accounting without speculative elements.
  • Keep all governance and linking rules visible and default-closed.
  • Avoid features that elevate comparative ranking, private paths, or Floor dilution.
  • (4 Nov 2026) Enforce zero-start mutual credit: accounts open at zero, balances move only by recorded transfers, credit limits are published circuit properties set after barrier checks.
  • (4 Nov 2026) Treat any ledger format change as a coordinated, published migration with a working export first; pin versions and never upgrade silently.
  • (4 Nov 2026) Let each circuit choose and publish its own tool sources; no single curator seat.
  • (4 Nov 2026) Keep presence indicators off by default; presence is not recorded work.
  • (4 Nov 2026) Use Matrix, if at all, only as a transport for messaging and calendars, with circuit rules kept on the lgme tape rather than in Matrix power levels.
  • (4 Nov 2026) Track W3C Linked Web Storage as a target for person-held export of each book; claim compatibility only once shown.
  • (5 Nov 2026) Make every ledger entry two-phase: validate with nothing written, then write only on the person’s confirmation, so third-seat refusal is part of each transaction.
  • (5 Nov 2026) Design inter-circuit exchange on the Credit Commons pattern: each circuit keeps its own zero-sum ledger and limits, links to others through published, hash-chained mirror accounts, and gives no node power over amounts or membership.
  • (5 Nov 2026) Allow relay-only hosts that store and sync a circuit’s encrypted book without being able to read it, for a published time and space limit.
  • (5 Nov 2026) Record an author identity on every change, not just a device or session, so the tape shows who made each line.
  • (5 Nov 2026) Publish a plain threat model and a status page that separates done, in progress, and planned; no claims beyond what is shown.
  • (5 Nov 2026) Where any admin-like seat is unavoidable, limit it to published, rule-bound actions and hold it symmetrically.
  • (5 Nov 2026 evening) Keep the Komunitin-style zero-sum clearing and published credit-limit reject from the lgme mutual-credit simulator; require a separate person-confirm step before any simulated write. There is no HCS submit in this mock.
  • (5 Nov 2026 evening) Label cryptographic and consensus steps honestly: do not claim RFC-8785 or Ed25519 completion until implemented; keep Mock Simulation Mode. The page does not submit to HCS and records no on-chain activity.
  • (5 Nov 2026 evening) Inside the mock, treat topic 0.0.489104 as a local label only — not as an on-chain receipt, a mint, or a third seat. The hederica index and deployment manifest stay simulation / design research.
  • (6 Nov 2026) Treat ledger lines as append-only: correct mistakes with compensating entries that name the rule broken, never silent deletes or in-place balance edits (hREA / ValueFlows pattern).
  • (6 Nov 2026) Study CES2/Komunitin circuit UX for notifications and clearing flows; keep lgme’s simulator mock-only and add person-confirm before any simulated write.
  • (6 Nov 2026) Do not adopt a trusted sync server as ledger authority; keep relay-only or encrypted-host patterns so hosting cannot read or settle the book.
  • (6 Nov 2026) Explore SCITT-style signed statements plus receipts for published work and provenance exports; registration policy must itself sit on the tape.
  • (6 Nov 2026) When comparing local-first stacks, prefer author-visible history and person-held export over LWW server settlement for anything that affects credit or Floor.
  • (6 Nov 2026) Prefer in-artifact deliberation (comments/annotations on the shared record) over separate chat that never reaches the tape; export discussion with the artifact.
  • (6 Nov 2026) Watch atmospheric-group style portable group DIDs with member-held payloads; if adopted, publish role powers and keep mutual-credit rules off the host.
  • (7 Nov 2026) Pick one small, plain, required access format for each book (WAC-style readable grant lists) so sharing rules move with the book; start with no grants and add each by a recorded act.
  • (7 Nov 2026) Let a person record locally first and sync only to storage they choose; mark local entries as drafts until published to the circuit, since an unpublished change is not a change.
  • (7 Nov 2026) Give every ledger and settings record a strictly increasing version number; reject a write that does not follow the last published version instead of overwriting it.
  • (7 Nov 2026) Keep any search index person-held and rebuildable from the book; never let one client’s or host’s index decide what the record says.
  • (8 Nov 2026) Keep the user-supplied Prior Signal memory synthesis in full on this page and on Memory and sovereign records. It is attributed synthesis, not a verified transcript and not established evidence. No video URL was supplied.
  • (8 Nov 2026) In simulation only, design a local replay of an append-only message log so one client file can reconstruct balances, limits, and provenance without a private backend. Do not submit to HCS, do not treat a mirror as live consensus, and do not record on-chain activity, including a manifest.
  • (8 Nov 2026) In the mock, chain each state transition to the hash of the previous state and call that a hash chain. A hash chain is not itself a Merkle inclusion proof. A consensus receipt does not guarantee archive availability, truth, or that every rewrite is impossible.
  • (8 Nov 2026) Offer standardized mutual-credit formulas (reciprocal hours, emergency barter pledges, care-work clearance, tool-lending escrow) that a person snaps together. They record work or an explicit pledge. They do not mint, and they do not dilute refusal.
  • (8 Nov 2026) Keep offline signed receipts provisional until reconciliation, including double-spend and credit-limit checks. A disconnected signature is not a finalized tape line.
  • (8 Nov 2026) Before any simulated commitment, show a plain-language receipt and a one-touch NO. A later NO cannot reverse a finalized event; refusal is before commitment, and a correction is an appended record. “Third Seat” is the person’s right of refusal, not a new authority over the person.
  • (8 Nov 2026) Leave debt decay unpublished unless the cadence was explicitly agreed in advance. It must preserve zero-sum accounting, Floor seniority, audit, and person refusal. It is not unilateral erasure, forced labor, or speculative issuance.

This page is the running public accumulation. Daily review and addition continue until instructed to stop. Floor stays senior. An unpublished change is not a change.

Sources

  • Holochain “We” Demo (Sep 2022): https://youtu.be/qOXBb2LLQVA
  • The Weave / Moss: moss.social, lightningrodlabs/moss
  • hREA: hrea.io
  • Moss 0.15.7 release (Jun 2026) and releases: github.com/lightningrodlabs/moss/releases
  • Moving the Moss tools to Holochain 0.7 (14 Sep 2026): moss.social/blog/2026/09/14/moss-tools-holochain-0-7/
  • This Week in Matrix 2026-10-30: matrix.org/blog/2026/10/30/this-week-in-matrix-2026-10-30/
  • Matrix v1.19 release (8 Jul 2026): matrix.org/blog/2026/07/08/matrix-v1.19-release/
  • Matrix Conference 2026, Next Generation Matrix (P2P, DMLS): cfp.2026.matrix.org/matrix-conference-2026/talk/7GYBAP/
  • W3C Linked Web Storage Protocol 1.0, Working Draft 23 Oct 2026: w3.org/TR/lws10-core/
  • hREA mutual credit example, issue #166: github.com/h-REA/hREA/issues/166
  • Credit Commons Protocol documentation: credit-commons.gitlab.io/credit-commons-documentation/ and creditcommons.org
  • TimeOverflow, Federation via Credit Commons Protocol, issue #846 (May 2026): github.com/coopdevs/timeoverflow/issues/846
  • Keyhive project: inkandswitch.com/project/keyhive/; ARK API guide: automerge.org/docs/keyhive/ark-api-guide/
  • This Month in Automerge, September 2026: automerge.org/blog/2026-september/
  • p2panda and Willow support nodes announcement (Aug 2026): autonomous.zone/@p2panda/117138315374073165; p2panda v0.7.1: github.com/p2panda/p2panda/releases/tag/v0.7.1
  • Holochain roadmap (updated 3 Nov 2026): holochain.org/roadmap/; releases: github.com/holochain/holochain/releases
  • lgme mutual-credit simulator (published mock page, simulation only): https://lgme.app/mutual-credit-simulator
  • Cryptobusi/lgme mutual-credit-simulator.html, commit dec8453: https://github.com/Cryptobusi/lgme/commit/dec8453ccfa0bcdc227cf509ddede876cf014dc6
  • Komunitin (mutual credit / CES context): komunitin.org
  • Egonomic principles: Schelling (1978) Egonomics; Marcum & Smith Egonomics; site protocol and status pages.
  • hREA happ-0.5.0-beta.1 (10 Sep 2026): https://github.com/h-REA/hREA/releases/tag/happ-0.5.0-beta.1
  • hAppRadar on hREA ValueFlows 1.0 (updated 3 Oct 2026): https://happradar.com/articles/hrea-merges-valueflows-1-0-and-holochain-0-7-in-18-541-line-pull-request
  • CEN Newsletter May 2026 (CES2 live): https://www.community-exchange.org/home/cen-newsletter-spring-2026/
  • CES Upgrade News (Komunitin / partners): https://www.community-exchange.org/home/ces-upgrade/
  • Jazz — What we learned from classic Jazz (17 Apr 2026): https://jazz.tools/blog/what-we-learned-from-classic-jazz
  • Jazz — How Sync Works: https://jazz.tools/docs/concepts/how-sync-works
  • IETF RFC 9943 SCITT (June 2026): https://www.rfc-editor.org/rfc/rfc9943
  • IETF RFC 9942 COSE Receipts (June 2026): https://www.rfc-editor.org/rfc/rfc9942
  • Lightningrod Labs, MVP vs Maturity (28 Oct 2026): https://lightningrodlabs.org/blog/mvp-vs-maturity/
  • Moss releases: https://github.com/lightningrodlabs/moss/releases
  • AT Proto Atmospheric Groups (22 Oct 2026): https://atproto.com/blog/atmospheric-groups-intro
  • Solid specification PR #824, Require WAC for servers, make ACP optional (merged 5 Nov 2026): https://github.com/solid/specification/pull/824
  • Solid forum, Programming for wizards: why we chose Solid (4 Nov 2026): https://forum.solidproject.org/t/programming-for-wizards-why-we-chose-solid/11029; margin notes: https://github.com/muze-labs/margin-notes
  • This Week in Matrix 2026-11-06: https://matrix.org/blog/2026/11/06/this-week-in-matrix-2026-11-06/
  • User-supplied synthesis, 8 Nov 2026, “Video Transcript Breakdown & Synthesis,” on the Prior Signal video “Something Is Happening to Human Memory — And It Started the Day We Learned to Write.” No URL was supplied with this publication. Not an independently verified transcript and not established here as scientific evidence. Full text: /memory-and-sovereign-records.

End of the page

Glossary

Plain names. Each line is the same rule, said without the securities word.

  1. 01

    Paid first (Floor)

    was Floor

    Paid first from surplus already named, before any later claim.Also: Food, rent, and the bus, paid first.

  2. 02

    Public schedule (Mint)

    was Mint

    New units enter on one public schedule. No private sale and no private allocation.Also: Same schedule for everyone. No private drop.

  3. 03

    Named bill (Issue)

    was Issue

    A named obligation assigned to a person. It is not cash, and it does not clear at the register.Also: A bill. Not cash in the app.

  4. 04

    Audit trail

    was Tape

    The record that must show title, issuance, lien, conversion, and the registrar’s act.Also: The receipt everyone can open.

  5. 05

    Risk-adjusted fee

    was Charge

    Discount and risk are named up front, before any residual value is titled.Also: Same price. No VIP.

  6. 06

    Registrar

    was Agent

    Records and enforces the posted rules. Does not create new units.Also: The app can explain. It cannot tap pay.

  7. 07

    What's left (Thin)

    was Thin

    The width of the book is the data. A tight price is not invented when the book is quiet.Also: A wide number is the honest price.

  8. 08

    Residual value

    was Desert

    What remains after paid first and the listed prices. Titled even when the figure is zero.Also: What's left. Even if it's nothing.

Also said

Extra names for the same rules. They do not add a step.

  • Third seat

    Your seat.

  • Quiet print

    Money issued off the public schedule.

  • Provenance

    Where it came from.

  • Refusal

    You tap no, and the no stays on the record.