↩ ExploRational · A Catalogue of Divergent Rationality
explorational · a divergent move
The architecture diagram says the services are independent. One log line — a timestamp, twice — says they are not. Hold a fine detail and a high abstraction together, and let each correct the other. Zooming chooses a level to work at; crossing refuses the choice and works the ladder itself.
Every field keeps its abstractions on one shelf and its particulars on another, and most reasoning stays on the shelf where it started. Strategy documents argue with strategy documents; log lines argue with log lines. The catalogue already has a move for choosing your shelf — zooming — and choosing well takes judgment. But the debugging sessions people retell for years, the audits that actually found it, the field notes that overturned a theory: those almost always contain a crossing — a moment when something tiny was laid directly against something huge, and one of them broke.
David Chapman's account of meta-systematic practice describes exactly this motion: running up and down between a formal system's terms and the concrete circumstances they are supposed to cover, treating neither as the truth of the other. The detail is not an instance to be filed under the abstraction; the abstraction is not a summary to be shrugged at from the trenches. Each is a witness against the other. The timestamp indicts the diagram — two “independent” services fail in the same hundred milliseconds. And the crossing runs downward just as well: the org chart explains the log line, because the retry storm lives exactly on the boundary where two teams stopped talking. Neither level could have told you alone; the information was in the crossing.
The move, as a discipline: when stuck at one altitude, fetch a witness from another. Reading strategy? Bring one raw particular — a support ticket verbatim, one invoice, one commit — and make the strategy account for it. Drowning in particulars? Bring one abstraction and make it earn each detail: which clause of the diagram predicts this line? Where the account fails is never noise. It is the finding.
the signature instrument
One production incident described at four altitudes. Read any level alone — each is locally coherent. Then cross a pair and read what the confrontation yields. Every crossing pairs real levels of the same event; nothing is computed.
The crossing bench
qualitative — four levels, six crossings; the yield is in the confrontation
select two levels
Each level is honest on its own. Pick one, then a second; the bench will read them against each other.
Six crossings are possible; each yields something no single level contains.
what to try
1 · One particular into the strategy meeting. Bring a single verbatim artifact — one ticket, one recording snippet, one receipt — to the next abstract discussion. Ask the plan to account for it specifically. Watch where the plan's vocabulary runs out; note the exact sentence where it does.
2 · One abstraction into the weeds. Mid-debug, mid-edit, mid-sort: stop and state the highest-level claim your current activity presupposes (“retries make us resilient,” “this chapter belongs in the book”). Ask whether the particular in your hands is evidence for it or against it. You will sometimes find you are polishing a counterexample.
3 · Find the boundary detail. Details that sit where two abstractions meet — the timestamp shared by two services, the expense that two budgets both refuse — carry the most cross-level information. Collect one per week; they are the cheapest audits you will ever run.
the mapping
| in the instrument | at your desk |
|---|---|
| a level | any altitude of description with its own vocabulary and its own experts |
| a crossing | one detail and one abstraction made to account for each other, explicitly |
| the yield | whatever survives in neither account — the finding |
| the boundary detail | a particular that two abstractions both claim, or both disown |
| the broken witness | the level that had to revise — sometimes the diagram, sometimes the log |
where it tears
risk · token opposition
One customer story wheeled into the strategy review to be admired and dismissed is the ceremony of this move with none of its work. The test: did any level have to revise? A crossing that ends with both accounts intact was theater — the catalogue's token-opposition risk at a new address.
risk · the vivid detail wins
A concrete particular beats a statistic in the room even when the statistic is right — one plane crash against a safety record. Crossing levels gives the detail a hearing, and the hearing needs a judge: one witness can indict an abstraction, and cannot convict it alone. The abstraction is owed its base rates.
risk · altitude sickness
A quark explains no quarterly report. Crossing works between adjacent or near-adjacent levels, where the two vocabularies still share referents. Stretched across too many rungs it produces profundity-shaped sentences with no yield — the connection is real, and empty.
Fetch a witness from another altitude, and let the two accounts fight until one of them revises.
can you use it?
RECOGNITION — Which is crossing the levels? A: choosing to analyze the outage at the service level rather than the code level. B: reading the org chart while holding one log line, and asking the chart to account for that line. C: summarizing the logs into a dashboard.
B. Two altitudes are held at once and made to confront each other. A is zooming — choosing an altitude. C converts detail into abstraction, which is aggregation, not confrontation.
THE NEAREST NEIGHBOR — Zooming also moves between scales. What separates crossing from it?
Zooming ends on one level: change scale until the problem changes shape, then work there. Crossing keeps two levels live simultaneously and extracts its finding from their disagreement. Zooming picks the courtroom; crossing stages the confrontation.
PRODUCTION — Take a document you own (a plan, a syllabus, a budget). Name one fine-grained particular from the world it governs, and write the sentence the document cannot currently say about it.
Budget: the £34 monthly charge for a tool one person still uses. The budget speaks in categories (“software: £2,300”) and cannot say “we pay for the departed designer's habit.” Yours works if the particular is real, the document genuinely cannot account for it in its own vocabulary, and writing the missing sentence would change the document.