Nine Titles And Twelve Code Fences

195 lines on the raw split. 196 once the closing newline is counted. 64 of them are blank, so 132 carry content and 111 of those are distinct. 21 lines sit on a string that repeats, and every repeat is structure: a three dash rule 12 times, a bare fence marker 7 times, and a fence marker with a language tag 5 times. 19 heading lines. 9 sit at the first level and 10 at the second. 0 sit at the third, so 0.0 per cent of the outline runs three deep. Nine titles across one file means nine rooms announced once each and then handed straight to prose, with no sub heading for a reader to hide in. Read that as a working habit rather than a fault. A document with nine titles and no third level is a document written to be jumped into from the top rather than read end to end. Whoever picks the job up opens it at the section that names their problem. The outline is flat and the file is honest about it. Nothing in it was padded to look deeper than it is.

12,359 bytes and 12,223 characters. The 136 bytes between the two counts are 68 characters that sit above the plain alphabet, carried in 9 distinct glyphs, and every one of those 68 weighs 3 bytes: 0 two byte, 0 four byte. 9 glyphs do the whole job: a long dash 33 times, a right arrow 21 times, a short dash 4 times, a bullet 3 times, a check mark in a green box twice, a plain check mark twice, an ellipsis once, a warning sign once, and one invisible variation selector. The highest code point in the file is that variation selector, and it draws nothing. It sits behind the warning sign so the sign renders in colour, and it is the only character in 12,223 that a reader will never see. Mode 0644. The owner reads and writes, and every other account on the machine can read a document that names where the services live and which one holds the state. That is a decision about trust taken once, quietly, by whoever saved the file first. Count the absent signs while the set is open: 0 per cent signs, 0 euro signs, 0 dollar signs, and 0 clock times anywhere in the file.

1 table. 5 table lines. 3 data rows and 9 cells, and 0 of those cells are empty, so the grid closes at 100.0 per cent full. Count the header and the same table holds 4 rows and 12 cells. 3 columns wide, opening on line 29 and closing on line 33 with a blank line under it. The three columns answer three questions in order: which piece, where it listens, and who manages it. 2.6 per cent of the file is a grid and the other 97.4 per cent is prose, steps and headings. A grid at 100.0 per cent is worth a second look, because a full grid is either small enough to check by hand or shaped after the fact. This one is three rows doing one job: the pieces, the doors and the owner of each door. When the sweep is small enough to close, close it. Nobody is impressed by a gap left in on purpose.

12 fence lines in 6 blocks, so every fence in the file opens and closes. 12 lines are nothing but 3 dashes, which is 6.2 per cent of the file: two of them fence the header block on lines 1 and 11, and the other ten stand between sections. 33 bullet lines against 7 numbered lines. The numbered lines are the ones whose order matters, and the bullets carry everything that does not. 43 bold runs against 1 italic in 174 asterisks, so emphasis is spent on the names a reader will search for. 33 long dashes against 4 short ones, 182 hyphens with 21 of them doubled, holding compound names together. 1 question mark in 1,570 words, and it sits in a line about what an automated check cannot tell you. 0 exclamation marks. 0 checkboxes. That is the register of a file written by one operator for one operator: emphasis where the hand goes, and none where the eye would like it. 6 blocks of code sit inside the prose, unwalled by any heading of their own. The reader who needs them already knows where they start.

195 lines on the raw split.

1,570 words across those 132 content lines. 8.05 words to a line, 7.87 bytes to a word, 10,559 characters with the spaces taken out. The average line is 61.7 characters and the longest is 514, sitting on line 175 inside a step where the parameter list ran long. 67 numbers stand alone in this file, which is 4.27 in every 100 words. That is what a procedure looks like when the author names the value instead of describing it. And the habit is not theoretical, because the same hand shipped: Entrade built 200 wood gasification machines across the UK and Europe. A EUR 75 million industrial group was restructured until every line of it answered to a ledger. 210 energy systems were deployed across Africa and Asia, each with a serial number. Companies were built across twelve countries, and each one left a registration a stranger can look up. A company was taken through a Frankfurt IPO, and the filings are public. 0 of those 5 asks a reader to take a number on faith. The file on the disk asks the same of its reader and pays for it with a 514 character line and 67 standalone numbers. 10,559 characters of instruction, 13 web addresses in the whole thing, and 1,570 words to carry the job.

3 date stamps in the file, in 2 distinct values 28 days apart: 2026-08-26 and 2026-09-23. 0 clock times anywhere in it. 0 of the stamps sit outside the header, so not 1 of the 132 content lines is dated. The last line of the file is a numbered step that ends on a check mark, which is the honest ending for a procedure: no summary, no author note, no closing paragraph. The document stops at the last thing the operator does. So the move is small and it fits in one habit. Before you call a procedure finished, count 3 things: the lines that leave the building, the empty cells, and the one step nobody has hit yet. 9 titles and 0 sub headings tells you the author wrote for a reader in a hurry. 68 characters in a second alphabet tells you the author thought in two alphabets while writing one. 100.0 per cent grid fill tells you the author checked twice. The probability that the person who needs this file ever reaches it is not zero. Most are pricing it at zero, and a document that only opens for its own author is the reason. 195 lines, 9 cells, 12 fences, 1 question mark. Count the sections before you count the work. 6 blocks of code sit in this file, and every one of them closes.