A Dispatch Protocol With Three Inboxes

37,104 bytes and 36,908 characters. One file, counted two ways, and the two counts do not agree. The gap is 196. That gap is not slack and it is not padding. It is the extra weight of the 107 characters in this file that sit above the alphabet, and those 107 sit in exactly 4 glyphs. 76 em dashes at 3 bytes each carry 152 of the 196. 18 section signs carry 18. 12 arrows carry 24. 1 en dash carries 2. 152 plus 18 plus 24 plus 2 is 196. The arithmetic closes to the byte, so the character count and the file size are two views of one number. 686 lines on a raw split. 204 of them blank. 482 carrying content. 5,463 words in total. 0 question marks across all 5,463. 0 exclamation marks as well. A specification that routes work between 5 engines asks the reader nothing and shouts at nobody.

69 headings, and 31 of them are first level. 12 are second level and 26 are third. That ratio says the top of this document is not a spine with chapters hanging off it. It is a list, and the list is the document. Under those headings sit 16 tables spread across 119 table lines. The tables hold 103 data rows and 367 cells, and not one of the 367 is empty. 32 bullet lines run against 14 numbered ones, so three quarters of the enumerations here are unnumbered. 18 lines are three dashes. 76 bold runs and 1 italic. 15 per cent figures and 0 euro signs. 0 URLs. 0 wikilinks. A file that decides which engine gets which job links to nothing outside itself. It names 15 dates across 5 distinct values, and the newest of them is 2026-09-23, which is the day the index stamp was written and not the day anything in it changed.

The roster names 5 engines. Claude orchestrates planning, architecture and coordination, and it is always running. Codex executes implementation, debugging and adversarial review. Kimi handles vision, visual to code, video analysis and deep research. Gemini holds the long context at 2 million tokens, against Kimi at 256,000 and Claude at 1 million. Qwen 3.5 4B classifies inbound messages on localhost port 11434 and does nothing else. It has 1 tier and it returns a label or a score, never a sentence. Three of the five are doors opened by hand, one task at a time, launched and closed again. And 3 headings in this file carry the word DORMANT, all 3 of them for the same engine. The document keeps a door on the list that it has already shut, and marks the shut one in the heading rather than deleting the row.

A dispatch matrix built on twelve task classes sits in section 1, across 6 columns. Task type, trigger patterns, primary engine, model tier, fallback, invocation. Planning is the only class that does not leave the orchestrator, so 11 of the 12 rows end in a handoff. Section 3 reads 8 allowed combinations, and 2 of those 8 read NEVER while 4 read CONDITIONAL. The ceiling is the machine underneath it. 24 gigabytes, roughly 82 per cent used at active session load, about 4.3 gigabytes of headroom. The pre-flight threshold is 18 gigabytes, which is 75 per cent of 24. The file names 24 gigabytes 10 times and 18 gigabytes 7 times, and it runs the same check script 6 times, once beside a cleanup command. 2 external engines at a time. 3 orchestrator terminals, no more. 4 thermal states from 0 to 3, each with its own action, and state 3 stops all heavy processing. The budget is written in gigabytes, not in good intentions.

37,104 bytes. 36,908 characters. The gap is 196.

The anti-patterns section holds 9 rules filed under 8 numbers. The list runs 1, 2, 3, 4, 5, 6, 7, 8 and then 8 again. The second number 8 is the rule that caps the machine at 3 concurrent terminals, so the strictest line in the section is filed under a number that had already been spent. In 5,463 words this is the only place the document breaks its own ordering, and it breaks it on the list of things never to do. The rules themselves read plainly. Never open the vision engine's interactive mode. Never run more than 2 external engines at once. Never skip the pre-flight. Never hand planning to an executor. Never put a project path in the portable spec. Never ask the classifier for a sentence. Never run a dormant engine where the working one already covers the job. Never open an interactive session inside automation. Never open a terminal without counting the ones already there. 9 rules. 8 numbers. 0 question marks.

The exit contract holds 9 codes. 0 for success. 1 for a general error. 5 when memory runs above 90 per cent. 6 on a thermal critical. 7 when the engine is already running. 8, 9 and 10 for the three auth failures. 124 when the retries are exhausted. 2 of the 9 are auth failures and the file says those 2 are never retried automatically, because a retry cannot fix a login. The closed door gets a check of its own. One request, a 30 second timeout, one word back. If that word returns, 3 more tests run at 5 minute intervals before the status line in the roster is allowed to change. 3 numbers get watched while it waits, discussion 22970 and issues 22545 and 23362. Version 2.0.0 landed on 3 April 2026 and the frontmatter was stamped 4 April, one day after the version it describes. 9 of the 15 dates in this file are the third of April. It was indexed on 23 September 2026, 172 days after that stamp, with its own date line still reading 3 April. The probability that a routing table written in three days still routes correctly a season later is not zero, and the document prices that at zero by never checking.