Twenty Eight Headings Under A Revoked Decision

24,746 bytes and 23,991 characters. One file, counted two ways, and the two counts do not agree. The gap is 755. That 755 is the extra weight of the 595 characters in this document that sit above the alphabet, and they sit in exactly 35 glyphs. 435 of them are carried in two bytes and 160 in three, and 435 plus 160 twice is 755, so the arithmetic closes to the byte on both counts. The census behind it reads: 267 umlauts, 142 marks of punctuation, 55 degree signs, 42 signs from arithmetic, 30 arrows, 27 subscripts and superscripts, 9 deltas, 9 glyphs in no class at all, 8 euro signs, 5 Greek letters and 1 check mark. The check mark is the highest code point in the file, 10,003, and it is used once. 48 soft hyphens sit invisibly inside long German compounds. The rest of the document costs one byte a character: 262 lines on the raw split and 261 on the stripped one, 62 of them blank and 199 carrying content, 3,083 words, 20,846 characters that are not whitespace. The average line runs 90.9 characters and the longest runs 673 on line 179. The mode is 644. This is what a working document costs when it is written in German and read by a machine built to read English.

28 heading lines. 1 is the title on line 12, 2 sit at the second level on lines 16 and 260, and 25 sit at the third, and nothing anywhere in the file goes deeper than that: no fourth, fifth or sixth level heading in 262 lines. The 25 third level blocks split three ways. 18 open with a full date. 6 open with the month 2026-04 and no day at all, and they run as a block from line 220 to line 255. 1 is the template the file writes for itself, sitting inside a code fence. The 18 dated entries cover 6 distinct days and the whole window from the first to the last is 5 days, from 2026-04-20 to 2026-04-25. The days are not spread evenly: 9 of the 18 land on 2026-04-23, which is half of them, against 4 on 2026-04-22, 2 on 2026-04-24 and 1 each on 2026-04-20, 2026-04-21 and 2026-04-25. They are filed newest first, which is what the file's own first paragraph asks for, so a reader arrives at 2026-04-25 and walks backwards into the week. There are 0 tables in the whole document, 2 fence lines, 26 rule lines, 27 bullet lines against 2 numbered ones and not one checkbox.

The file states its own format in a fenced block that opens on line 18 and closes on line 23, under a second level heading on line 16, and the block names the shape it wants: a third level heading made of a date, a dash and a subject, then a decision, a one line rationale and a links line, newest first. The first real entry begins on line 27, so the rule sits above the run it governs rather than at the foot of it. Count what follows that rule. 24 entries are written under it, and 6 of the 24 open with the month and stop there, no day, no dash, no subject in the shape the block asked for. That is a quarter of the log, and every one of the 6 sits in the tail from line 220 to line 255, so the drift is not scattered through the file. It is a single block written to a different standard, and the standard it was written to is never declared anywhere in the document. A specification that governs 18 of 24 entries is a specification the file has already decided against, and it has decided quietly, in the only place a reader will not look on the first pass: the tail.

25 third level blocks and the promises they keep: 24 declare a decision, 21 carry a rationale, 25 carry a links line. So every block in the file points somewhere, and 4 blocks state a decision without saying why. All 4 of those are dated 2026-04-23, the busiest day in the log, which is where a habit breaks under load. The blocks themselves run from 12 words to 293 words and from 7 lines to 27, averaging 121.8 words, so this is not a ledger of one line rulings; it is a working notebook with a 293 word entry and a 12 word entry filed under the same format. Emphasis is done by weight: 162 bold runs spread over 114 of the 199 content lines, out of 648 asterisks, and 0 italics in the entire file. The bold labels number 25 distinct strings, and they repeat what the format block asked for and then go past it, adding a consequence for the vault, a safety note, an open list, a mixing table, a materials choice. The log has quietly grown more fields than its own specification names, and it has grown them one entry at a time.

24,746 bytes. 23,991 characters. The gap is 755.

58 wikilinks in 15 distinct targets. The busiest target is named 12 times, the second 10, the third and fourth 5 each, and the whole navigation of this document runs through 15 names. Behind the 58 links sit 0 web addresses, 0 markdown links and 5 code spans, so the only exit from any entry is a name the vault already holds. The punctuation census reads 45 long dashes and 36 short ones against 26 doubled hyphens inside 462 hyphens, which is a document that joins its nouns rather than breaking its sentences. 590 standalone numbers and 17 per cent signs sit in 3,083 words. The currency is named 8 times as a three byte sign and never as a code, and no dollar sign appears anywhere in 24,746 bytes. 3 question marks and 0 exclamation marks, so the log asks three times in 24 entries and never raises its voice once. The question a reader is left holding is not one the file asks, because a links line to a decision that has been revoked still points at the same place it always did.

Two of the 25 blocks carry a revocation in their own heading, and the word appears 3 times in the file. The first sits on line 43, dated 2026-04-24, and closes with the revocation and its date: revoked on 2026-04-25, the day after it was written. The second sits on line 161, dated 2026-04-23, and closes with a revocation that points at another entry and names no day at all. So the mechanism this log uses to kill a decision is to go back and edit the heading of the dead entry, and it has used that mechanism twice, and one of the two times it left the date off. Nothing else in the file records either reversal: the successor entries are written as fresh decisions in the normal shape and never name the entry they replaced. The stamps close the case. 7 frontmatter keys sit over lines 1 to 9, and one of them reads updated 2026-04-25. The file was born on 2026-04-28, three days after the newest entry it carries, so every entry in it was dated before the file existed. It was last written on 2026-09-23 at 18:42, which is the day of its index stamp and 148 days after it was born, and its own updated field is 151 days behind that write. 25 date strings in 7 distinct values, 6 of them inside a single 5 day window, and the seventh is the day a machine touched it. The probability that a log whose own updated field reads 2026-04-25 still describes the machine as it stands 151 days later is not the probability that the decisions were right. It is the probability that nobody has read the tail since April, and the two revoked headings are the price of that, because a reversal recorded in the heading of the entry it kills is only found by a reader who was already looking.