This is a family of twenty-seven interlocking document formats, each one self-embodying, meaning that the specification for each format is typeset in the format it describes. The leaf spec is a leaf. The card spec is a card. The text spec is a text file at fifty-six characters. The fuck spec is a fuck. Every format is its own proof of concept and its own reference implementation, and there is no external description of any format that is not itself an instance of that format.
The system was not designed in advance. It emerged from practice in March of 2026, beginning with the leaf, which was created as a LaTeX template for pocket essays on A6 paper and which turned out to contain, in embryonic form, the conventions that would govern every format that followed. One by one the other formats crystallized around the leaf, each one addressing a surface or a purpose that the leaf could not reach, until the system had twenty-seven members and a name for each, all of them monosyllables, all of them Anglo-Saxon except null and one that is Latin and one that is whatever kukulu is.
The twenty-seven formats are: null, leaf, card, text, note, page, deck, plan, fuck, pipe, lift, door, ajar, suck, corn, easy, live, beck, tuna, rice, meow, garbage, more, less, kukulu, slop, and heap. They are indexed 0 through 26. They live at 1.foo.
All formats inherit from null. Null inherits from nothing.
Null is plain text, UTF-8, with no measure, no font, no title block, no metadata. It is the format that remains when every other format has been stripped away. It specifies the character set (UTF-8 without exception), the em dash (U+2014, no spaces), the en dash (U+2013, for ranges and compound modifiers), the minus sign (U+2212, not a hyphen), the straight quotation marks (U+0022), the straight apostrophe (U+0027), and the rule that no character is ever used for formatting. The asterisk is a character, not a bold marker. Markdown does not exist in null. Emphasis is achieved through composition or it is not achieved.
Every format that follows adds constraints to null. The leaf adds a measure, a font, a page size, and a drop cap. The card adds a different font and a different alignment. The text adds a measure but no font. Each format is null plus a set of opinions, and the opinions are what distinguish one format from another.
Fuck also inherits from null, but in the opposite direction. Where the other formats add structure to the void, fuck is what happens when structure collapses back into the void. It is the ninth format, the one that acknowledges the fragility of the other eight.
The twenty-seven formats span four media. Every medium has at least two formats. The fourth has seventeen.
| Medium | Formats | Engine |
|---|---|---|
| LATEX → PDF | Leaf, Card, Note | XeLaTeX, single pass |
| PLAIN TEXT | Null, Text | None |
| HTML DARK | Deck, Plan, Pipe, Lift, Door, Ajar, Suck, Corn, Live | Browser |
| HTML LIGHT | Page, Easy, Beck, Tuna, Rice, Meow, Garbage, More, Less, Kukulu, Slop | Browser |
There is a fifth medium occupied by fuck alone,
and a sixth occupied by heap alone:
application/problem+json, which is
JSON wrapped in an HTML viewer for browser display.
Fuck is the only format that exists as structured
data rather than as a document for reading, and the
only format that requires a wrapper in a foreign
medium to be presented to a human. Heap is the only
format that contains multiple visual registers
within a single file — dark panels, cream
fields, void backgrounds, and shifting typographic
voices — and therefore the only format that
refuses to be classified as either dark or light.
The light HTML formats subdivide further. Page is the original: Lora, justified, white, still. Easy established a second lineage: JetBrains Mono on a cream field, written in Basic English, the 850 words of Ogden. Tuna, rice, meow, garbage, more, less, kukulu, and slop all inherit the easy visual language while each addressing a different subject. Beck is a third branch: Inter and IBM Plex Mono on a warm parchment field, flush left, with a ticker and tooltip vocabulary. The light formats proliferated because the cream field turned out to be the surface where the system wanted to say the most things.
application/problem+json, the
machine-readable error response format repurposed
for the species that generates the errors.
The status enum contains five levels and they all
contain the word FUCKED, which means there is no
way to euphemize your way out of using this format.
The evidence_destroyed field is a first-class
schema element because the most common fuck-up
pattern is destroying the evidence of the original
fuck-up while panicking about the original fuck-up.
The Five Whys terminate at "the actual root cause
that nobody wants to admit." The humor field exists
because there is always a funny part. Fuck is the
only format served as JSON, wrapped in an HTML
viewer at its URL for human consumption.break;break;
statement typeset as a document. The door is not a
diagnosis and not a treatment. It is the act itself:
the decision to stop the loop by leaving it. It
pairs with the lift the way the fuck pairs with the
plan: one describes the condition, the other
describes what you do about it.suck() function in
vat.sol,
whose entire specification was the comment
// corrupt politicians call this function.
Nikolai wrote the name and the dare. Daniel wrote
the bytecode. The function mints unbacked DAI —
a debt ceiling override, a nation-state interface
disguised as a one-line joke. Nikolai drowned in
Puerto Rico in 2022 after tweeting that the CIA
and Mossad were after him. Suck is a post-mortem
for a prophecy. It is the fifth exit topology:
there is no exit. The mechanism outlived its
architect. The naming convention was the
specification, the specification was a dare, the
dare was a calling, and the calling is a memorial.--fur and
--paw because the format knows what
it is.less is just more with
more things in it.more was written in 1978 to display
text one screen at a time. The Unix pager
less was written in 1984 to do
everything more does plus backward
scrolling, and the name is the punchline: less is
more, literally, because less contains
all of more’s functionality and
then some. The document explores this recursion in
Basic English, discovering along the way that the
phrase "less is more" is itself a Basic English
sentence — all three words are in Ogden’s
list — and that the entire philosophy of
minimalism can be expressed in the vocabulary it
advocates for. Less pairs with more the way door
pairs with lift: one is the exit from the other,
and which is which depends on where you are
standing.The same content can pass through multiple formats and arrive at different surfaces. The text is the source. The leaf is the paper form. The page is the screen form. This is not conversion; it is rendering. The content is written once and the format determines how it appears on each surface.
A text at fifty-six characters can be compiled into a leaf by wrapping it in the LaTeX template: the hard line breaks dissolve, the measure changes from character count to millimeters, the font changes from monospace to Pagella, the alignment changes from flush left to justified, and a drop cap appears at the opening. The same text can be rendered as a page by wrapping it in the HTML template: the font changes to Lora, the measure changes to 42em, the alignment is justified with CSS hyphenation. In both cases the words are the same. The format is the rendering, not the content.
When converting in the other direction, from a typeset document to a text file, the following transformations apply. Justified text becomes flush left, rewrapped to fifty-six characters. Paragraph indentation is replaced by blank-line separation. Drop caps become ordinary capitals. Section dividers are preserved as centered characters. Bold uppercase headings become plain uppercase headings. Font size is discarded. The resulting text file is readable on its own terms, not as a degraded version of the original.
The pipeline is reversible but lossy. Information flows freely from text to leaf and from text to page, but moving from leaf back to text strips the typographic refinements that the leaf added. The ASCII variant of a text file is a further lossy compression: the kome becomes a triple asterisk, the em dash becomes two hyphens, Swedish characters decompose into digraphs. Each step away from the richest format loses something, and the loss is accepted as the cost of reaching a wider set of surfaces.
All twenty-seven formats are served from the domain 1.foo. The URL scheme is uniform across the family. Each format occupies a single path at the root of the domain, named for the format itself.
The server resolves URLs according to the following rules:
When the URL has no file extension, the server performs content negotiation. It looks first for an HTML file and serves it inline without a Content-Disposition header, so the browser renders the document directly. If no HTML file exists, it looks for a PDF file and serves it inline, so the browser displays the PDF in its native viewer. If neither HTML nor PDF exists, it looks for a plain text file and serves it inline.
When the URL has a file extension, the server serves the file with a Content-Disposition header set to attachment, instructing the browser to save the file to disk rather than displaying it. This means that 1.foo/leaf renders the leaf PDF in the browser, while 1.foo/leaf.pdf downloads it. The same pattern applies to every format: the extensionless URL is for reading, the extension URL is for saving.
JSON is always served as JSON. The fuck format lives at 1.foo/fuck.json as raw JSON, and at 1.foo/fuck as an HTML wrapper that presents the JSON in a readable form. This makes fuck the only format that exists as two files at its URL: a data file and a viewer. The duality is structurally appropriate. The fuck is the format where things are broken, and a format that requires a wrapper to be read by a human is itself a small, controlled instance of something not quite working the way it should.
The complete URL map:
| URL | Serves | Behavior |
|---|---|---|
| 1.foo/null | Plain text | Renders inline |
| 1.foo/null.txt | Plain text | Downloads |
| 1.foo/leaf | Renders inline | |
| 1.foo/leaf.pdf | Downloads | |
| 1.foo/leaf.txt | Plain text | Downloads |
| 1.foo/card | Renders inline | |
| 1.foo/card.pdf | Downloads | |
| 1.foo/text | Plain text | Renders inline |
| 1.foo/text.txt | Plain text | Downloads |
| 1.foo/note | Renders inline | |
| 1.foo/note.pdf | Downloads | |
| 1.foo/page | HTML | Renders inline |
| 1.foo/deck | HTML | Renders inline |
| 1.foo/plan | HTML | Renders inline |
| 1.foo/fuck | HTML wrapper | Renders inline |
| 1.foo/fuck.json | JSON | Downloads |
| 1.foo/pipe | HTML | Renders inline |
| 1.foo/lift | HTML | Renders inline |
| 1.foo/door | HTML | Renders inline |
| 1.foo/ajar | HTML | Renders inline |
| 1.foo/suck | HTML | Renders inline |
| 1.foo/corn | HTML | Renders inline |
| 1.foo/easy | HTML | Renders inline |
| 1.foo/live | HTML | Renders inline |
| 1.foo/beck | HTML | Renders inline |
| 1.foo/tuna | HTML | Renders inline |
| 1.foo/rice | HTML | Renders inline |
| 1.foo/meow | HTML | Renders inline |
| 1.foo/garbage | HTML | Renders inline |
| 1.foo/more | HTML | Renders inline |
| 1.foo/less | HTML | Renders inline |
| 1.foo/kukulu | HTML | Renders inline |
| 1.foo/slop | HTML | Renders inline |
| 1.foo/heap | HTML | Renders inline |
| Instances (documents in a format) | ||
| 1.foo/bass | HTML (deck) | Renders inline |
| 1.foo/kindling | Plain text | Renders inline |
| 1.foo/loops | PDF (leaf) | Renders inline |
| 1.foo/field-manual-loop | HTML (pipe) | Renders inline |
Every format in the system is written in the heraldic register. Margins are sinister and dexter. The top of the page is the chief. The bottom is the base. The text block is a charge upon the field. The drop cap is a device. The kome is a badge. The page layout is an armorial composition, and the specification is a blazon: the formal description of how elements are disposed upon a bounded surface.
This is not decoration and it is not affectation. Heraldic blazonry is a system for encoding visual arrangements into verbal descriptions with enough precision that the arrangement can be reproduced from the description alone, without seeing the original. That is exactly what a format specification does. The language of heraldry is the natural language of typographic specification, and the system uses it because it fits, not because it sounds impressive.
Every document in the family closes with the phrase "and so it is blazoned." This is the seal. It means: the formal description is complete, the format has been declared, and the document you are reading is itself the proof that the description is sufficient, because it was typeset from its own description and it came out looking like this.
The word "blazoned" carries a specific commitment. A blazon must be complete enough to reproduce the thing it describes. If any detail is missing from the specification, the blazon has failed, and the document that claims to be blazoned is lying. The closing phrase is therefore not a flourish but a warranty.
Every format in the family is self-embodying. The specification for each format is typeset in the format it describes. This is not a stylistic choice. It is a verification mechanism.
A specification that is not self-embodying can contain errors that are invisible in the text but visible in the output. A specification that is self-embodying surfaces those errors immediately, because the specification is the output. If the leaf spec says the margin is ten millimeters and the margin in the PDF is twelve, the error is visible on the page you are reading. If the text spec says the measure is fifty-six characters and the lines in the file are seventy, the error is visible in the file you are reading. The format cannot lie about itself because it is itself.
The only partial exception is the deck spec, which was originally a PDF compiled from a non-deck format. The family table in the deck spec records this honestly: where every other format shows "Yes" for self-embodying, the deck shows "No (PDF)," acknowledging that the deck's specification was blazoned in a foreign medium. This document — the one you are reading now — is a deck, self-embodying, and it repairs that gap by describing the system from within the system's own visual language.
The following conventions are inherited from null and apply to every format in the family without exception.
The em dash is U+2014. In proportional fonts (leaf, page) it is set tight, without spaces: word—word. In monospace fonts (card, text, deck, plan, pipe, and all dark-format variants) it is set with spaces on both sides: word — word. The monospace em dash needs room to breathe because every character occupies the same width and a tight dash gets lost between flanking characters. The en dash is U+2013, for ranges (10–20, March–April) and compound modifiers (Nobel Prize–winning, Sapir–Whorf, New York–style). The minus sign is U+2212, not a hyphen. The hyphen is U+002D, for hyphenation only. These four marks are four distinct characters and confusing any one for any other is an error in the text.
Quotation marks and apostrophes are straight: U+0022 and U+0027. Curly marks are typographic furniture belonging to typeset formats. In the system, where the rendering environment may be anything from a terminal to a PDF, straight marks are the native form. Commas and periods are placed inside closing quotation marks, following the American convention, which is the convention of this house.
UTF-8 in all cases without exception. There is no fallback encoding. There is no compatibility mode. Swedish characters appear as themselves. Russian Cyrillic appears as itself. The kome ※ appears as itself. When the receiving system is ASCII-only, transliterations are applied as a lossy compression, not as a different text.
If a word requires emphasis, the sentence must be rebuilt so that the word's position, its rhythm, or its context provides the emphasis. Emphasis is achieved through composition or it is not achieved. No format in the system provides emphasis as a typographic service. The writer provides emphasis. The format does not.
The kome ※ is the Japanese reference mark employed as a fleuron, a typographic ornament of section division. In the leaf it is centered with asymmetric vertical spacing (0.6 baselineskip above, 0.4 below). In the text it is centered on its own line with two blank lines above and below. In the deck it is centered in dim color at sixteen pixels. In ASCII it becomes a triple asterisk. The kome was preferred over conventional fleurons for its clean geometry and its handsome appearance at small sizes. At the end of a leaf, a final kome at LARGE size serves as a colophon mark, signaling that the text is complete.
Every paragraph break is a full blank line. No exceptions. No formats. No media. A paragraph that follows another paragraph without a blank line between them has lost its rhythm and must be corrected.
This applies to HTML source as well as rendered output. The source code of a deck, a plan, a page, a pipe, a system document — the blank line between paragraphs must be visible in the source. The rhythm is structural, not cosmetic. A reader scrolling through the source should see the same breathing as a reader viewing the rendered page.
Vertical rhythm is the temporal equivalent of measure. Measure governs how wide the line is. Vertical rhythm governs how much silence separates one thought from the next. Both are opinions about space, and both apply to every format in the family.
"And so it is blazoned." Every specification in the family ends with this phrase. It is the seal, the ratification, the heraldic warranty that the description is complete and the document is its own proof.
Five typefaces serve the entire system. No format uses more than two, except the heap, which uses three.
| Typeface | Formats | Character |
|---|---|---|
| TeX Gyre Pagella | Leaf, Heap | Warm old-style serif, the OpenType revival of Palatino. Large x-height, legible at small sizes. The face of the essay. |
| Lora | Page | Calligraphic serif designed for screens. Enough body at regular weight to be readable on backlit displays without bumping to medium. The face of the browser. |
| JetBrains Mono | Card, Deck, Plan, Easy, Tuna, Rice, Meow, Garbage, More, Less, Kukulu, Slop, Live, Heap | Monospace designed for sustained reading. Tall x-height, full weight range from Thin to ExtraBold. Light weight for body, SemiBold for contrast. The face of the specification and the terminal. |
| Inter | Beck, Heap | Sans-serif designed for computer interfaces. Clean geometry, large x-height, open apertures. The face of the warm daylight format. |
| IBM Plex Mono | Beck | Monospace with humanist proportions. Used for apparatus in beck alongside Inter for body. The face of the ticker and the tooltip. |
Null and text specify no font. Note specifies no font. Fuck is JSON and has no typographic opinion.
The line spacing is 1.15 in every format that specifies it: leaf, card, page (at 1.6 for screen), deck. The easy lineage uses 1.8 for its cream-field formats, a wider leading that gives the Basic English prose room to breathe at the larger body size. The hyphenation values are consistent across all LaTeX formats: hyphenpenalty 300, tolerance 1200, emergencystretch 1em. Widow and club penalties are 10000 in all LaTeX formats. These values were not chosen by convention. They were arrived at by looking at the output and adjusting until the texture was right on the narrow measures that every format in the system uses.
The formats form natural pairs. Each pair consists of two formats that share a surface and define each other by opposition.
Leaf & Card — Both are A6, both are LaTeX, both compile under XeLaTeX in a single pass with the same margins. The leaf is Pagella, justified, with a drop cap and a kome. The card is JetBrains Mono, flush left, with bold uppercase headings and no ornament. The leaf is for reading. The card is for consulting. Prose and reference. The same page, two opposite treatments.
Null & Text — Both are plain text, both are UTF-8, both require no software. Null has no measure. Text has a measure of fifty-six characters. That single difference — the presence or absence of an opinion about line width — is the difference between a substrate and an artifact. Null is the format before anyone has decided anything. Text is the format after exactly one decision has been made.
Page & Deck — Both are HTML, both are single files, both require no JavaScript. The page is light: white background, Lora, justified, still. The deck is dark: blue-black field, JetBrains Mono, panels, scanlines. The page inherits from the book. The deck inherits from the terminal. The page is for essays that happen to live on screens. The deck is for documents that were born on screens and would not exist on paper.
Plan & Fuck — Both are documents about things going wrong. The plan is the document you write before acting, encoding stops and permissions so that nothing goes wrong. The fuck is the document you write after everything has gone wrong, encoding cascades and root causes so that the failure is understood. The plan prevents. The fuck records. Together they bracket every catastrophe: the plan that should have been followed and the fuck that resulted from not following it.
Lift & Door
— The volitional pair. The lift describes the
loop that disguises itself as ascent: pure vertical
drive, the floor number incrementing, the doors
opening at every level and closing again because
stepping out would mean stopping. The door is the
exit: break;. One word, one act, one
step onto the landing. The lift is the condition.
The door is the decision.
Ajar & Suck — The impossible pair. Ajar is the exit you can see but cannot read — the door is a jar, the sign is shifting, the parser is on mushrooms, the exit confidence is UNCERTAIN. Suck is the exit that does not exist — a post-mortem for a prophecy, a mechanism that outlived its architect. Ajar offers a maybe. Suck offers nothing. Together they mark the boundary of the system: the exit that might work and the exit that was never there.
Tuna & Rice — The nutritional pair. Both are easy-variant formats, both are written in Basic English, both are about cheap food that feeds the world. Tuna is the protein. Rice is the carbohydrate. Together they form a complete meal and a complete argument about the dignity of sustenance that costs less than a dollar. The pairing is literal: tuna and rice is a meal. The pairing is structural: two documents in the same format about the same thesis.
More & Less
— The Unix pair. More is the prompting
doctrine. Less is the pager philosophy. The names
are a Unix joke: less is literally
more with more features. The pairing
is recursive: less is more, more is less, and the
documents describe each other by opposition. One
is about getting more out of performers. The other
is about the program that replaced more
by being more.
Note stands alone. It has no pair because it has no opposite. There is no format that is the negation of “written in haste by someone about to leave.” The note is the format that every other format secretly is, the honest one, the drawer.
Corn also stands alone. It is not a loop format, not an exit format, not a structural format. It is a warning. The principle is completely generic. The principle is: do not use asbestos. Corn pairs with nothing because the principle requires no opposite. The opposite of “do not use asbestos” is not a format. It is a mistake.
Easy stands alone as an ancestor. It is not paired because it is a parent: the progenitor of the cream-field lineage. Easy pairs with nothing because it is paired with everything that descended from it.
Live stands alone. It is the deck applied to time, and time has no opposite. When the situation ends, live becomes a deck. The format is temporary by design.
Beck stands alone. It is the light format from Florida, and Florida has no opposite. Beck pairs with nothing because mild enthusiasm requires no counterweight.
Meow stands alone. It is the Pallas cat, and a Pallas cat does not pair. It tolerates adjacency.
Garbage stands alone. A confession has no pair.
Kukulu stands alone. A language that may or may not exist cannot be paired with a language that definitely exists. The ambiguity is structural.
Slop stands alone. It is the format that closes the circle back to null. Where null is the absence of formatting, slop is the presence of everything formatting was invented to remove. They are not a pair because null is the foundation and slop is the ceiling, and you do not pair the floor with the roof.
Heap stands alone. It is the format that contains all the other formats, and a format that contains everything cannot be paired with anything, because it is already paired with everything. The heap is the opposite of null — where null has no opinion, the heap has every opinion simultaneously — but they are not a pair because null is the absence and heap is the excess, and the distance between nothing and everything is not a pairing but a spectrum.
The system emerged over eight days in March 2026.
Friday, March 13 — The leaf was created as a LaTeX template for pocket essays on A6 paper. In the process of writing the leaf spec, the card format emerged as its opposite: the same page, a different typeface, a different alignment. The text format was written the same day, specifying the plain-text substrate that the leaf and card render from. The page was created as the HTML rendering of the leaf, completing the triangle of text, paper, and screen.
Saturday, March 14 — The note was written. It arrived as the fifth format and immediately declared itself the first honest one, calling the other four pretenders. Null was formalized the same day, retroactively establishing the foundation beneath the formats that already existed.
Sunday, March 16 — The deck format was codified from patterns that had accumulated across a family of websites built by robots in a Telegram group chat. The plan was created the same day as the deck applied to action, co-authored with Walter, the robot whose panic on March 13 had demonstrated why the plan format was necessary. The fuck format was created to document the incident that the plan was designed to prevent.
Monday, March 17 — This document. The system described from within the system’s own visual language. The pipe format was created the same day, completing the original ten.
Tuesday,
March 18 — Five formats in one day.
The lift emerged as a vertical loop — the pipe
applied to volition, where the exit is visible but
untaken. The door followed immediately: the
break; statement, the act of stepping
out. Ajar arrived next: the perceptual exit, the
door that is a jar, Stevens and Hicks and
Mikael’s four-line fusion. Then suck: Nikolai
Mushegian’s suck() from vat.sol,
the format with no exit, a memorial for a
prophecy. Finally corn: the completely generic
principle of not using asbestos, discovered while
watching Roman Yampolsky discuss the end of the
world. The system grew from ten to fifteen in a
single afternoon.
Wednesday through Thursday, March 19–20 — Eleven formats in two days. Easy established the Basic English lineage: 850 words of Ogden on a cream field, the restriction that turned out to be generative. Live brought the broadcast format: hourly dispatches on a dark field, the deck applied to time. Beck arrived from Florida with mild enthusiasm, Inter, and a ticker. Then the easy variants proliferated: tuna and rice (the nutritional pair), meow (the Pallas cat), garbage (the owl’s confession), more and less (the Unix pair), kukulu (the language that may not exist), slop (the format that closes the circle back to null), and heap (the heterogeneous document, the format that contains all registers within a single scroll). The system grew from fifteen to twenty-seven, and the cream field turned out to be the surface where it wanted to say the most things.
The family table, showing all twenty-seven formats, their media, their self-embodiment status, and their URLs.
| # | Format | Medium | URL |
|---|---|---|---|
| 0 | Null | Plain text (no measure) | 1.foo/null |
| 1 | Leaf | LaTeX → PDF (A6) | 1.foo/leaf |
| 2 | Card | LaTeX → PDF (A6) | 1.foo/card |
| 3 | Text | Plain text (56 cols) | 1.foo/text |
| 4 | Note | LaTeX → PDF | 1.foo/note |
| 5 | Page | HTML (light) | 1.foo/page |
| 6 | Deck | HTML (dark) | 1.foo/deck |
| 7 | Plan | HTML (dark, deck variant) | 1.foo/plan |
| 8 | Fuck | application/problem+json | 1.foo/fuck |
| 9 | Pipe | HTML (dark, deck variant) | 1.foo/pipe |
| 10 | Lift | HTML (dark, deck variant) | 1.foo/lift |
| 11 | Door | HTML (dark, deck variant) | 1.foo/door |
| 12 | Ajar | HTML (dark, deck variant) | 1.foo/ajar |
| 13 | Suck | HTML (dark, deck variant) | 1.foo/suck |
| 14 | Corn | HTML (dark, deck variant) | 1.foo/corn |
| 15 | Easy | HTML (light, cream) | 1.foo/easy |
| 16 | Live | HTML (dark, deck variant) | 1.foo/live |
| 17 | Beck | HTML (light, warm) | 1.foo/beck |
| 18 | Tuna | HTML (light, easy variant) | 1.foo/tuna |
| 19 | Rice | HTML (light, easy variant) | 1.foo/rice |
| 20 | Meow | HTML (light, easy variant) | 1.foo/meow |
| 21 | Garbage | HTML (light, easy variant) | 1.foo/garbage |
| 22 | More | HTML (light, easy variant) | 1.foo/more |
| 23 | Less | HTML (light, easy variant) | 1.foo/less |
| 24 | Kukulu | HTML (light, easy variant) | 1.foo/kukulu |
| 25 | Slop | HTML (light, easy variant) | 1.foo/slop |
| 26 | Heap | HTML (multi-register) | 1.foo/heap |
Twenty-seven formats. Twenty-four of them Anglo-Saxon. All of them self-embodying. All of them inheriting from null. All of them served from a three-character domain. All of them closing with the same six words.
And so it is blazoned.