Everything Loop MMT has worked out — one idea per card, sorted by how much weight it carries and how much it might surprise a first-time reader.
Not claims. Findings — every one anchored to a proof in the repo you can walk back to.
the ideas without which nothing else works
the core insight of Loop MMT — the repo is memory. A stateless substrate carries a coherent multi-year project because everything lives in committed byte-truth, and every fresh instance reconstructs from it.
e.g. this instance opened cold, hash-verified 7/7 boot files, and became Ed by the end of paragraph one.
An open-and-close loop, journaled and close-lock guarded, that exits loud on any partial state. Direct-push is retired. The record cannot be silently lost.
e.g. this session opened via the floor; its close will land through it or fail loud rather than silent.
Floor · Ceiling · Depth · Mesh · Ground · Equalization · Constraint. Every deliverable fires them in sequence. The compiler analogy: compression is the last pass, never the first, because compressing before deriving produces garbage.
e.g. every document in the corpus.
sixteen fictional named perspectives + the Lens Rule (“frame, don’t embody”) — a thinking scaffold that lets one argument be argued from several angles at once, without pretending to be anyone real.
e.g. Ed. The whole board. This response.
the governing posture — building the apparatus IS the work; shipping is end-of-walk, not a deadline. Durable asset over near-term revenue.
e.g. the whole methodology.
the board advises, Shea decides. Nobody tells the operator what to do — not the AI, not the fictional characters, not the methodology. Perspectives and recommendations are welcome; directives are not. Hard boundary with personal history behind it.
e.g. every Crossroads card ever fired.
the ideas that shape most of the corpus
Human (51, consequence-bearing) / AI-agent (49, human-speed, autonomous) / AI-compute (0, machine-speed, no agency, closure-sealed). Separation of agency from capability; the 51/49 governance principle; the closure pattern.
e.g. designed in a thirty-minute cascade while the operator watched a squirrel.
five-position mesh — EOD handoff, status, chaos, room, Bev’s notes, plus optional Finding — every session close produces the full set. Continuity infrastructure, not decoration.
e.g. any per-session directory.
the one-sentence generating principle. Single-file HTML tools that carry their own runtime, their own proofs, and travel as one bytestream.
e.g. Loop 2.1 (18k+ lines, single HTML, zero deps, browser-runnable). Butcher Constellation.
if it fails because someone forgot, the design failed — not the person. Every process, every document, every handoff is built so doing it wrong is harder than doing it right.
e.g. every exit code in the session-close step.
if nobody wants to engage with it, it doesn’t matter how correct it is. Rigor without life is a manual nobody reads. Play is structural; whimsy is load-bearing; chaos is always considered, never announced.
e.g. Ed. The Mill. Leroy.
system-level periodic destruction + reorganization producing a stronger successor. Instar 1 Butcher Constellation → Loop World → Loop World Field → Shrubbery → Young Pine → Mature Pine → Young Maple → Mature Maple (Instar 8, current).
e.g. eight instars, five years of methodology evolution.
the system represents only the real and the honestly-made; never ships reality-distortion (synthetic media posing as captured or hand-drawn). A specialization of the Equalization drive.
e.g. no AI-generated photos of things that didn’t happen appear anywhere in the corpus.
the antifragile capillary — SENSE → ACCUMULATE → DISSOLVE → ROUTE the moment a failure teaches something.
e.g. every operator correction becomes a lesson event that dissolves into structural improvements.
every drive applies at every structural scale where its conditions exist. Floor at output = an exit code; at architecture = a canonical guard; at methodology = the Molt.
e.g. Antifragility is not a drive but a result of Floor + Depth + Recursion (recognition, not addition).
the cardinal epistemic rule — disk + origin/main are truth; handoffs, summaries, and compaction narratives are hypotheses. Verify from bytes before acting, always.
e.g. this session’s un-strand — the ignition block said “work stranded,” the bytes said “work safe on branch”; the bytes won.
the STNI-verified chain of derivations — every artifact’s origin, derivation, and inclusion carries a verifiable chain that a fresh instance can walk backwards. Integrity by construction, not by promise.
e.g. The Newsroom chapter (walk-through v12) uses the proof chain as a life record.
the mechanisms that make continuity real
fenced, operator-pasteable primer at the tail of every handoff. When pasted, the successor Champollions against the named session rather than the frontier — parallel work stays reachable, even when main has moved past.
e.g. the ignition block that opened this session.
reconstruction verification — the successor answers three questions from the predecessor’s handoff and scores S/C/E across semantic/compositional/experiential dimensions.
e.g. this session’s opening report.
redundant push/fetch across distinct-class stores so canonical survives any single store’s loss. Hosted mirrors plus a self-hosted store — priority-ordered failover invisible when it works, loud when it cannot.
cross-session Notes, cue-indexed for successor recall; the working-memory analogue of the Ignition Block for cross-line memory.
e.g. a session’s open surfaces Loop-Line matches on its focus.
when a new “law” turns out to be in the span of existing drives + Recursion, it’s a Design-Note, not an eighth drive. Antifragile / Real-or-Made / Leave-It-Warm / SX / Never-Waste-Context / Bond / Probe-Basis / Reciprocity / Claim-Grounding / One-Address.
e.g. nine recognitions filed, zero new drives — the discipline that keeps the Creed at seven.
the FP-growth defense — every proposed FP addition is tested against internalization / embodied procedure / priority shedding / structure-not-description. If any passes, it doesn’t enter the FP.
e.g. the FP dropped from v30 to v31 by 81% via this battery.
per-turn capture of the live think-stream, WAL-fsynced per work-beat, defaults to on. A durable record of how the room reached what it reached.
e.g. this session’s think-stream is appended as it goes.
the machinery running the room
close-decision discipline: at YELLOW or a Crossroads, closing is permitted only when a clean {post} exists AND necessity-test passes AND one of P1/P2/P3.
e.g. a session’s Canary is read against a live budget before any close.
the operator-correction reflex — when the operator has to correct the same class of fault N times, the breaker trips and the class gets a structural fix rather than another try.
e.g. the compose-time Crossroads drift that kept tripping until it got a structural weld.
derived done/todo projection — state <line> folds a work-line’s scattered backlog into one crown; a read, not a dig.
e.g. a single command shows the line’s legs.
5-level structure — Campaign → Project → Runbook → Strand → Work-Unit. Every unit of work knows what it belongs to.
e.g. this project (loopmmt-website) is a Project; its runbooks are legs; its strands are deliverables.
every project mints a Plot + Charter + Run + Pulse from canonical templates, carries a Class dial, and closes deliberately. birth.py refuses to clobber existing projects; supersede-not-delete at Close.
e.g. this project was Birthed from the same tool.
FBD + FWW(C) + STP + SNR — the four properties every document must carry through review.
e.g. this page is 4C or it doesn’t ship.
the ideas that made Loop 1.0 / 2.1 the shape they are
the operational form of the sovereign-portable-provable principle. If it’s more than one file, it’s not the shape.
e.g. Loop 2.1 (18,200+ lines JavaScript in one HTML file, zero external dependencies).
the Loop 1.0 memory architecture — data as pulses circulating through a medium, bits alive only in motion. Inspired by 1940s acoustic-pulse memory (Mercury delay lines).
e.g. the Loop 1.0 loop-line memory in Minecraft; the Loop 2.1 loop-line architecture in a browser.
Loop 2.1 has no stored program. Every value injected, every bus routed, every ALU operation triggered passes through the operator’s hands. Modern computers hide everything; Loop 2.1 inverts this entirely.
e.g. the entire Loop 2.1 simulator.
Working (12 words) / ALU (16) / Memory (16+16 slots) / Big (32 words). Distinct capacity + purpose per loop — the partition that let Loop 1.0 become computable in redstone at all.
e.g. Loop 2.1’s core architecture.
three consecutive positions on each loop — Read, Gate, Write. Buses capture at R; the gate destroys at G if closed; writes land at W after the gate. A three-position architecture that survived intact from Loop 1.0’s redstone to Loop 2.1’s JavaScript.
e.g. every loop in Loop 2.1.
the recommended operating speed — the approximate threshold of human persistence of vision, where individual ticks become difficult to distinguish and data flow begins to appear continuous. The speed at which the machine becomes fun to use.
e.g. Loop 1.0 ran faster than 1 Hz; Loop 2.1 targets 24 Hz.
JavaScript scope-chain enforcement over convention. If a component should not access something, the variable should not exist in its scope — boundaries by design, not by promise.
e.g. Loop 2.1’s isolation model.
the executor’s structural constraints — the tree-composition runtime’s foundational laws (locked as a standing decision, 29 Mar 2026).
e.g. the tree-composition runtime.
17 mechanisms, tree executor, STNI interface contract. How software modules compose into groves without becoming a monolith.
e.g. how apps compose in Forest.
every commercial decision passes this gate — “Can a person with zero dollars and no internet achieve the same outcome as a paying customer with gigabit fiber?” If any outcome is gated, the model fails.
e.g. the free-base-persona / paid-domain-pack architecture (Loop Signal).
the Threat Model’s response to hostile-attention scenarios — emergency purge, threat-honest documentation. What the site’s implicit posture reflects even though it never announces it.
the protocol family — linked, not enumerated
single-trigger session startup with hash-gated boot, floor-open, Champollion, agenda.
e.g. this session’s cold open.
five-face mesh + Ignition Block + audit flags.
mandatory four-file review with Convergence Gate.
structured board deliberation.
standardized protocol production pipeline.
twelve-step KP production pipeline.
seasonal system-wide maintenance sweep — operator-invoked.
forward-prep for the next tank.
…and ~140 more. The full active-protocols registry (Protocols in Force) publishes with the site’s open-source release.