Internal · 30 July 2026 · visual map

Your diagram,
lit up.

The architecture you drew, redrawn box for box, coloured by what actually exists. Twenty-four boxes, three colours, one uncomfortable pattern.

This is the picture. The reasoning, the evidence and the section-by-section verdicts live in the companion document.

Read the full detail13 sections · evidence · blockers Skip to the patternwhat the colours reveal
9
boxes built as drawn
5
built, but differently
10
boxes that don't exist
3
we added, not on your map
built as drawn built, deviated not built added beyond the brief every box links to its row in the detail document
the seam Everything above this line exists. Almost nothing below it does. That line is exactly where Workflow A ends and Workflow B begins in your §2.
and one arrow your diagram doesn't have

What the colours say

We built the intelligence. We did not build the execution.

The pattern, in one sentence

The diagram splits cleanly at Generate Action Brief. Above it — collect, normalize, dedupe, cluster, classify, score, gate — is almost entirely built. Below it — route to a team, create a task, notify, dashboard — is almost entirely missing.

That isn't a random scatter of gaps. It is precisely your §2 split: Workflow A exists, Workflow B does not. The system can tell you what to do and write the first draft. It cannot yet put that in anyone's queue.

Why it happened that way, honestly

Everything above the seam is machinery that only had to satisfy itself — data in, score out. Everything below it needs a decision from a person: which channel the digest lands in, which task system owns the work, who accepts the SLA. Those decisions are still open, so the branches were never built.

It would have been possible to build them against guesses. That would have produced five task-creation branches pointed at a tool nobody agreed to use.

What closes the seam

Two things, in order. One: name the digest channel — one word, open since 9 July. That unlocks the move to a permanent home, without which none of the routing matters because nothing runs unattended. Two: agree the task system, and the five branches become roughly a day of work each, because the classification that feeds them already exists and is already correct.

The Content Intelligence box is separate and worth doing regardless — it sits above the seam, needs no decision from anyone, and is the step you yourself called the brief teams actually need.