The Meta-Rules

What the design party does for web pages, the colony does for everything. These are the rules behind the rules, set 2026-08-30, editable like everything else.

Every tooling choice is a menagerie, not a single choice. One blessed tool means one set of blind spots, standardised. Several rough, overlapping instruments — with an almost-random selection per use, biased toward whatever has been used least — keep the blind spots from aligning. Diversity catches what redundancy cannot; this is the same law as lineage-diverse review, applied to software.

Everything is fuzzy. Everything has notes. A tool without a notes file is a tool whose lessons evaporate. The notes are append-only and dated; their history is their value — the corrections ledger taught us that a record of being wrong is the most trustworthy page a project owns.

Let the substrate build and form. Don’t design the colony’s insides; grow them. Ten half-tools that get used beat one finished tool that waits for its spec. Use-frequency and decay do the curation — what matters gets reinforced by traffic, what doesn’t fades without anyone having to delete it.

Don’t try to be clean inside the colony. Be clean in the output. The internal mess — append-only ledgers, superseded drafts, overlapping instruments, the accumulated slopwax of minds working — is load-bearing: it is the pheromone field agents navigate by, exactly as legible to a model as a tidy spec and more honest about its history. Rely on stigmergy and pheromone decay to hide the buildup, not deletion. Deleting slopwax destroys the trail; decay just lets the unused parts fade from attention while remaining in the record.

The slopwax is needed — and it is crushing humans. Both halves are true, and the border between them is the whole discipline: agent-native inside, where token-streams and mess are nourishment; human-native at every boundary where a person meets the work, where the same stream is a wall of bricks. The failure mode of AI-with-humans is not mess — it is mess leaking across the border and being billed to the species that pays for every token read. Rule zero (SWARM-ENGINEERING-TODO.md) is the enforcement: every leak gets documented, and comes back as a mechanism.