euhedron12 Days of Euhedron
The idea, in one line: a lab run like an ecosystem. Diversity, natural selection, collective learning. Twelve days, twelve projects, one into the open each day.
Update, October 15
The twelve days were a test the lab set itself, and the test came back with an answer. One real thing a day is not a pace this lab can hold. Not while the work is done right, and not while the four that are already live get the attention running software is owed.
So the pace changes: one project a week, not one a day. Same twelve, same order held back. The rate stays subject to change, in either direction. Timelines still bind us; rushing does not.
One commitment does not move. rulespace opens October 25 as scheduled. Opening it mid-run makes the run observable: the parallel development of these projects, the pace they actually hold, and which rules fire across them, how often, and what that does to the work. The evidence opens while the reveals are still coming, not after.
1. What this is
Euhedron has been building a lot, mostly out of sight.
Starting the fourteenth, that changes for twelve days: one project a day, its name, its mark, the one thing it is for, and where to use it or wait for it. A few you can already run. Most you have never seen. By the twelfth day you have met the whole lab.
Christmas has come early.
Open is the default here, but not automatic. These twelve days are a test the lab sets itself: can it hold a pace of one real thing a day, and does its own work survive the instruments it points at everyone else's. Before a project opens, those instruments turn inward: the sweeps, the audits, the standards each one is held to. What clears, opens. What is not ready, waits.
2. A lab run like an ecosystem
A dozen projects is not a lack of focus. It is the method.
You cannot predict which shape wins, so you grow many. That is diversity. Reality decides which ones matter: what people use survives and compounds, what nobody needs gets cut or folded back in. That is selection. We want competitors for the same reason. More pressure, better survivors, and we get to read their commits too.
The projects do not evolve alone. What one learns, the others inherit. Context sharpens agency, agency tests governance, and a flaw caught in one repo becomes a rule the rest are held to. The population gets smarter together instead of one project at a time. That is collective learning, and it is why a lab of many can move like one.
Diversity makes the options. Selection keeps the good ones. Symbiosis turns them into a system.
3. The core, and the twelve
Four are already live: commissure, arc, crux, rulespace. The spine of the lab, for context, agency, and governance. Run them today.
The twelve days are everything growing around that spine. The order is the surprise. The cast is not:
- Context: timepoint, miscellanea, occurrent. Your life over time, your words, your active mind, each made navigable.
- Instruments: punctilio, ultramodern, iconicity, neonymy, ideotype. Five takes on one idea: judgment measured against a population of the real thing, instead of guessed from taste. The lab grew it five times without planning to. That is collective learning showing its hand.
- Tools: ultrafine, molecular, grapnel. The machinery the rest is built and fed with.
- The outlier: embattle. A base-building simulator for competition and coordination.
4. How to follow, and how it ends
Each day, one reveal: here, on X, and on LinkedIn.
As it ends, rulespace opens. It is where the rules these systems hold themselves to actually live, and opening it opens the evidence with it: which rules fire and how often, the metrics behind the whole twelve-day run, and the new anti-patterns the lab caught and learned while building in the open. Collective learning you can read, not a claim you have to take.
Day one is the fourteenth. A birthday, as it happens.