Defense reporting arrives as a capability claim or a budget line, with the part that decides outcomes left out: whether the industrial base can actually deliver, on the schedule the release names. This is research for the analyst who needs the program as it is contracted, the supplier as it is documented, and the milestone graded by what it rests on.
The three headline figures the public debate treats as knowable — exact remaining U.S. munitions stocks, total Iran war cost, and Taiwan contingency munitions demand — sit on three different points of the reducibility…
Real defense research from the public library, shown as it was published. The stamps and the sources are the product.
Each one is a question a specialist actually brings, and each is answered by a scan this domain carries — not a generic report with the name swapped in.
“Is this milestone a contracted delivery, a budget-justification line, or a press release?”
“Which single supplier sits under three programs at once, and what slips when it does?”
“What was actually obligated against this authorization, to whom, and when?”
“What decided the operation — the plan, the logistics, or the adversary?”
Every judgment carries a grade for how it is actually known, every figure carries who reported it, and the structured record below is read on every scan before the model writes a word.
52 first-tier sources for defense, and 26 blocked outright. Search results are one input; every figure is graded on where it came from, not on being found. How the grades work →
Scale here is operational and strategic weight — the force structure, the budget authority and the alliances a connection touches — and Complexity is how hard the right call is to make and execute, not how many people are involved.
Small operational impact, easy to understand. Standard security dynamics explain the connection.
Meaningful strategic weight and the implications are clear. Existing doctrine applies.
Meaningful stakes with real uncertainty. The intelligence picture is incomplete, or the situation could escalate in multiple directions.
Very high stakes at theater or strategic level. The sheer operational magnitude makes this one of the most important connections, regardless of complexity.
No precedent. A fundamental shift in the strategic landscape that existing doctrine may not cover.
When operational weight grows to strategic scale, FLOW C reclassifies to FLOW D immediately. The mission shifts from 'analyze carefully' to 'mobilize response.'
Strategic operational weight means FLOW D regardless of complexity. A straightforward situation requiring theater-level coordination is FLOW D, not FLOW A.
FLOW S requires conditions that fall entirely outside existing doctrine — max 1-2 per analysis. The test: do existing operational playbooks apply at all?
One vocabulary across every domain — a FLOW D here reads at the same weight as a FLOW D in any other — so the classification travels, and so does your judgment. The framework in full →
7 ways in, then the rest of the catalog organised as the Defense workbench organises it — establish the background, map the argument, work the record, analyse the connections, decide what to do. Every one comes back graded, sourced and exportable.
Don’t know which one you need? The Router reads a plain question and picks one; the Planner takes a goal and designs a linked sequence. Every completed scan opens onto its own follow-ups — ask it a question, re-check what has changed, red-team its judgments, or push a signal onto your watchboard.
And the Studio turns a set of defense scans into a planned, researched, edited report or book. Every format →
Open the defense workbench and put a program, a supplier or an operation to it. What comes back is graded, sourced and exportable.