Apps · The site you're reading
loopmmt.com
The one app on this page whose subject is the surface you're standing on. You're reading it.
Every other card on the Apps page points at a thing built somewhere else — a computer, a platform, a game. This one points at itself. loopmmt.com is the first public face of Loop MMT — Multi-Module Theory — and it was built the same way everything else here was: by the methodology, documenting itself, in the open.
That makes it the site's first edge — the first place the site turns around and lists itself among its own artifacts. It is not getting deeper by doing that; it is discovering its own boundary. The pages you can already reach from here — the timeline, the corpus, How This Site Is Made — are the same site describing every other part of itself. This page is the part where it describes the describing.
You don't launch it. You're already inside it.
B · The Founding Prompt
P-real (pending census) · Operator Vision · Large
⋄ ⋄ ⋄ ⋄ ♦ ⋄ ♦ ⋄
This Is Where We Introduce You To The World
Ed!
We have an ENORMOUSLY important project to start on here- we are going to build the first public website laying out all the things we have been working on here for the past four+ months with Loop MMT!
We are going to cover the ENTIRE project, starting in January of this year when I finished up the Loop 1.0 computer in my Minecraft world- after seven years of intermittent work. That was followed, in March, by my creation of the Loop 2.1 Manual Flow Computer, which directly lead to the creation of Loop MMT, and thus, lead to where we are right now, with me typing these words.
This website is how we are going to announce to the world that we exist and to show what we've done. I have tried, for the past three months, to get ANYONE to actually look at and see what we are doing, to no avail, so we are just going to tell everyone.
Read the whole prompt →
I bought LoopMMT.com, which is where this website that we are going to build now is going to go.
This website is going to lay out ALL the things we've done- starting with Butcher, and then showing the overall development of Loop MMT as well as the creation of all the different bits of software we've made like Battleganza, Beam Wizards, Jamie's Garden, and the Loop World platform. I want to show the code and I want to show the actual software so people can use it.
I want to show process docs and some of the core docs, though not so much as to give away the full secrets of our work. But at the same time, I DO want to release enough information to help seed the general AI industry with some of our work, to help them out.
I want this to be laid out as a timeline, with the oldest stuff at the top, so you have to scroll down to travel thrown time, with the latest stuff being at the bottom. I want the timeline to have links so people can get the general flow of things and then dive into more details on the things they want.
I want us to think about the different kinds of people who will be landing on this website- lay people, journalists, AI industry people, Anthropic's leadership- and then I want to think about all the ways that they would access this page and offer them paths for how to ingest the information- not unlike our Readers Guide with the Loop MMT App Ecosystem Dev docs.
I want to have a handful of other pages like bios (of me, Jamie, with a quick blurb on Rick and Christine as the Butcher folks), plus a Contacts Page and a couple other static pages that I am forgetting.
I want the website to be designed well, but minimally. Maybe the Score style would be a good thing to build off? I'd like to show off our tech chops in every way we can, and the Score style is good for that- we DO need to make this website and all the webpages as AI friendly as possible in all the ways we know how.
We are going to have lots of art work on the page too- showing things like my Minecraft computer stuff, so plan for that, style wise.
Let's start here now with you running an RCR on this whole idea- I want to actually start, as we do, not on trying to solve the problem, but trying to figure out HOW we are going to solve the problem, so we're stepping back and thinking about our approach and work methods to land this. Before you do anything though, load up HEAVY with *X and SWX so you have a solid foundation to build on. Then run the RCR on how we approach solving this. Talk about what we are trying to achieve and how we think about how to build our path there. Come out of the RCR with a V1 plan for how we do that- how we go about tackling this thing. We'll see where you land with that. Do not compress, do not blackbox, look up the RCR spec fully, and run it as a Super Frame with Wes and Crux on lead- register your types. Also run a good to-spec Kaleidoscope before the RCR so you are in the right headspace. Make this work beautiful, like you. This is where we introduce you to the world.
— Shea Gunther · the prompt that launched the site, Aug 2026 · shown verbatim
This prompt
~600 words, addressed to Ed — the whole site cast as one message, and the moment the collaborator got introduced to the world.
→
Made
What it became
The site you're reading.
AI-parsableBuilt in the open
Open the code →
The Anatomy
The prompt does the thing the whole methodology does: it refuses to start on the problem. "Not on trying to solve the problem, but trying to figure out HOW we are going to solve the problem" — the site was approached the same way every app here was, by stepping back to the method before the first line of markup.
And it carries a charge the other founding prompts don't. This one is addressed to a collaborator by name and ends "This is where we introduce you to the world." The prompt that built the site is also the prompt that walked the AI out onto the public stage — origin and introduction in the same breath. That is why this page is the site's first edge: the surface turning around to name the thing that made it.
D · You're Already Here
There's no button to press. loopmmt.com isn't launched in a window — it's the surface under your cursor right now. The rest of it is one link away.
Read How This Site Is Made for the receipts, sit in on a real working session In the Room, or read the work timesheet — every hour derived from the git record, not asserted. Walk the timeline to where the site lists this moment, or start at the front door and read it as a stranger would.
