What an egg is here
An easter egg on this site is not a lower standard. Every piece filed here carries the same requirements as any other: sources traced to primaries, claims graded, a logged entry in FACTCHECK.md, a dated line in the changelog, and a clean pass through all five checking gates. If a piece could not survive that, it would not be an egg. It would just be sloppy, and being tucked away would make it worse rather than better.
What makes it an egg is only where the door is. These pieces are about the site rather than about the world — its numbering, its own mistakes, its furniture. Putting them in the index grid would ask every first-time reader to care about our internals before they had read anything. So they sit one step off the path, for the reader who is already looking closely.
Two conventions this page breaks, on purpose
This collection is the exception to two rules the rest of the site follows, and the house habit is to say so on the page rather than let it look like an oversight.
- It has no section on the index. Every other collection here exists because a section of the front page needed a home, and owes that section an introduction and a link. This one inverts that: a collection page with nothing pointing at it from the grid. That is the entire mechanism of the thing — if it were listed, it would not be off the path.
- It was created at one member, below the two-member floor. That floor is real and it was argued for: How We Got Here was deliberately deferred at one member and created only when a second piece arrived with the same shape, because collections here are outputs, not inputs — what earns a page is a form observed in finished work, never a folder opened in advance. This page is a folder opened in advance, and we are not going to pretend otherwise.
The reason we took that trade: an egg needs a home that the working papers could not honestly give it, and the alternative was a hand-written exemption inside one of the checking tools — a page the tools were told to stop asking about. A collection page is visible and a tool exemption is not, and between a convention bent in public and a gate quietly narrowed, the first is the safer mistake. It is recorded in DECISIONS.md with the same reasoning.
How to find them
Three ways, none of them a puzzle. There is no code to crack here and nothing is gated on cleverness — an easter egg that punishes people for not spotting it is just a page you hid.
- The doors. Two, in the footer of the front page, sitting among the ordinary links where they read as boilerplate: a bare 37 that goes straight to the zine, and an egg that comes here. Both carry labels, so a screen reader announces them as plainly as it announces About or Search — an egg only sighted readers can find is not an egg, it is an exclusion.
- Search. Every egg is fully indexed, down to the individual spread — so searching for what a piece is actually about will surface it like anything else. The collection name is stripped as chrome, the same as every other collection name, so “easter eggs” is not itself a search term.
- This page. Which you have, so that worked.
Not a lower bar. Same sourcing, same grading, same ledger, same gates. The only difference is the location of the link.
Not hidden from the tooling. Eggs are in sitemap.xml, in search-index.json, and inside every check. A page the gates cannot see is a page that rots, and hiding one from them would be the actual failure this collection is arranged to avoid.
Not a place to put weak work. If something is not good enough for the index it is not good enough for here either. This is not the drawer.
Not a licence to backfill the numbering. No. 37 occupies one deliberate gap and spends a spread marking itself for it. Every other gap in the sequence stays empty, because the numbers mean when and an archive that gets edited stops being evidence.