How to drive it

0:00 · What this is. This is the Order of Battle. Every named engine, every app, and every tracked mechanism in one list, in one order.

0:08 · Two ceiling figures. Two ceiling figures sit on the front page, because they are two different calculations. The binder states one. The rows add up to another. Both are shown, and each is labelled for what it is.

0:20 · The five scores. The order is not an opinion. Every item carries five scores — revenue ceiling, build readiness, I P protection, partner fit, and mission impact — and these five sliders decide how much each one counts.

0:33 · The five presets. So ask the room what matters most to them, and press it. Revenue first. Build Now first. Fit first. Protected first. Mission first. The list re-ranks in front of them.

0:46 · What a row carries. Each row carries its own evidence: the tier, the priority, the I P status, the revenue model, and the ceiling in the words it was written in.

0:55 · Filtering, and the subtotal. Filter by family, tier, priority or I P status, and the ceiling of whatever is left on screen totals itself underneath.

1:02 · The two exports. Two exports. The ranked list in whatever order is on screen, and the Build Now pack. Both download in the room, with no connection at all.

1:11 · The four agents. And four agents sit on the same list. The Analyst explains the ordering. The Skeptic attacks the numbers before the other side does. Counsel holds the line on how much mechanism detail leaves the room. The Briefer gives you the words to say back.

1:26 · What is actually built. One more page, and it is the one to open first. The list is the I P and revenue view — it does not say what is deployed. The reconciliation maps every row onto the repositories and hosts that actually implement it, and it is honest about how few that is.

1:44 · The close. Ceilings are illustrative arithmetic, not forecasts, and the page says so before anyone else does. Whichever order the room chooses — that is the order that gets handed over.