A Grant Master That Instructs Itself

26,448 bytes and 25,982 characters. One file, counted two ways, and the two counts do not agree. The gap is 466. That gap is the extra weight of the 242 characters in this file that sit above the alphabet, and those 242 sit in exactly 30 glyphs. 224 of them are carried in three bytes and 18 in two, and 224 twice plus 18 once is 466, so the arithmetic closes to the byte. This is where the file departs from the shape the corpus has been measuring for days: on most of these documents the gap is exactly twice the glyph count, and here it is not, because the same file that keeps its 110 long dashes also keeps 8 o with an umlaut, 4 a, 2 u and 1 o with an accent, and every one of those 15 letters is one byte cheaper than the punctuation around it. 443 lines on the stripped split and 444 on the raw one, because the file ends in a newline. 97 of those lines are blank and 346 carry content. 3,784 words in total. 22,036 characters that are not whitespace. 36 code spans. 144 standalone numbers. 2 question marks across all 3,784 words and 0 exclamation marks, on a file whose last line is an instruction to keep it accurate. The mode is 600: readable by its owner and closed to everyone else.

54 headings. 1 top level, 15 second level, 38 third level, and nothing deeper. The 15 second level headings are numbered 0 through 14 and the sequence has no number missing, which means the document opens at section zero and runs to section fourteen without a gap. A document that starts counting at zero is telling you it expects to be edited at the front. Under those headings sit 12 tables spread across 75 table lines. 12 of those 75 lines are header rows and 12 more are separator rows, which leaves 51 rows carrying data. Count the header rows as data and the same grid reads 63 rows and 233 cells, and count only the bodies and it reads 51 rows and 188 cells. Both readings are honest and the difference is 12 and 45. Neither reading finds an empty cell: 0 either way. The widths run 5, 5, 3, 3, 6, 3, 4, 2, 6, 3, 2 and 3, so the widest table compares six things at once and the narrowest compares two. 172 distinct values sit in those cells and the longest of them runs 107 characters. The tallest table is 12 lines of a 4 column grid holding 10 rows, and it is the one table in the file whose columns are a person, a role, a contact and a responsibility.

The tenth section holds 10 laws and every one of them opens with a circled digit, running from the circled one to the circled ten. Those 10 characters are the only 10 in the file drawn from that block, so the count of circled digits in the document and the count of laws in it are the same count, written twice. Each law is set in bold and each closes with a full stop. Only 2 of the 10 carry a number in their heading: the one that caps personnel at 20 per cent and the one that names the compliance floor, and that floor is itself numbered C1 to C15. The string for the floor appears 4 times in the file. So a document of 10 rules puts 2 numbers in the headings and leaves the other 8 to be read. It also names 4 compliance items in the body against the 15 the floor is built from. The laws are not the only list here. 120 bullet lines run against 27 numbered ones, so more than four fifths of the enumerations are unnumbered. 18 lines are three dashes and 2 are code fences. 164 bold runs against 3 italics. 34 per cent signs, 23 euro signs and 0 dollar signs.

The file holds 10 links and they resolve to 7 distinct addresses. 0 wikilinks and 0 markdown links, so all 10 are written out in full rather than carried as references to something else in the vault. 1 of the 7 is malformed: a backtick is glued to the end of it inside the code span, so the address as written cannot be opened. That is the defect a file of this class produces, because the value is written once and read by a program that does not check it. Two lines pair a variable name with a value long enough to be a credential. Across the file there are 6 strings of 16 characters or more, and they come to 237 characters. The file is mode 600 and it carries a deploy credential in the open beside a note telling the next reader to rotate it if it stops working. The document that tells an agent what to load at every session also tells it what to send, and it puts the sending material in the same block as the reading list. Nothing in the file is a link to a person. The last table in the document, at the foot, is a routing table: 6 rows that pair a kind of work with the file that should be read before it, 3 distinct files named in backticks across those 6 rows, and exactly 1 of the 6 rows sends the reader back to this file.

26,448 bytes. 25,982 characters. The gap is 466.

The punctuation census is where the writing shows its hand. 110 em dashes, 11 en dashes and 215 double hyphens, against 724 single hyphens of every kind. 90.9 per cent of the dashes that are not hyphens are the long em dash, so this is a document written by something that reaches for the long dash by reflex and then reaches for two short ones when it wants to set a term apart. The 30 glyphs above the alphabet are the same story. 27 arrows, 15 of them pointing right and 4 of them pointing left, because the file carries a small diagram drawn in box characters: 4 box glyphs used 30 times. 2 warning triangles. 7 less than or equal to signs, 1 not equal to sign, 1 subscript two, 1 middle dot and 1 multiplication sign. 1 top level heading carries an em dash inside its own title. Highest code point in the file is 10,003. 0 times of day anywhere in it. That is the shape of a working document rather than a published one: it measures and warns and points, and it never once says what time of day anything happened.

The last line of the file reads Last updated 2026-04-13. The frontmatter says the document was created and last modified on 2026-05-28, which is 45 days after the date the body carries. The index stamp reads 2026-09-23, 118 days after the modified date. The disk says the file was born on 2026-05-28 and last written on 2026-09-23 at 18:42, the same 118 days, and the day of that write is the day of the index stamp. So the three stamps agree on when the file was touched and disagree on when it was last true. There are 4 date strings in the whole document in 3 distinct values and 0 times of day. The newest date anywhere inside it is 2026-09-23, and that is a stamp about the file rather than a fact inside it. The other 3 values sit in the frontmatter, on the last line, and in the sentence that closes section 12. The file's own closing instruction is to keep it accurate after every entity registration, every programme confirmation and every partner letter, and the gap between its stamp and its last write is 163 days. On the arithmetic in front of it, the probability that a briefing file still describes the world on the day it is read is not the probability that it was written, and this one is its own evidence.