F1
One product, four per-voter prices, three of them live
blocking
Safe Elections quotes $0.50–$1.50 per registered voter per cycle. The GTM package quotes a $5.23 floor and a $7.66 target. StrongRoom SE carries $18.00 as the ask. All four are Born Between 2 Generals numbers for the same jurisdiction and the same cycle.
Checkable: The spread between the deck floor and the SE ask is 36×. On Maricopa’s roll that is $1.27M against $45.7M. Both the deck and the SE mods site are live right now.
To settle it: One number is BB2G’s position. Until it is chosen, any two people reading two BB2G documents quote prices that differ by more than an order of magnitude to the same county.
Safe-Elections-Maricopa-Pilot.pptxSafe-Elections-National-Rollout.pptx~/bb2g-gtm/README.md~/strongroom-se/pricing/inputs.mjs
Open the instrument →
F2
The Wardroom’s one control cannot run
blocking
wardroom.html routes a task by POSTing to api.anthropic.com from the reader’s browser. The request carries no x-api-key and no anthropic-version header, and the endpoint does not allow a browser origin without an explicit opt-in header.
Checkable: Read the fetch call in the page source. Every click lands in the catch branch, which prints “That did not come back cleanly. Try again with a shorter description.” — wording that reads as a transient fault rather than a missing capability.
To settle it: Routing this task does not need a model. The rules that decide it are already written down in the page: a sensitivity gate, five bench entries with a stated speciality, ten assistants with a stated host. Those rules run in the browser with no key and no network.
wardroom.html
Open the instrument →
F3
The reconciliation headline and its own table do not agree on the count
material
The Case Engine states: “The proposed architecture describes seven products. Five of them already exist in the portfolio under other names.” The table underneath it has ten rows.
Checkable: Three rows are marked Built, two Extend, five New. Built + Extend = 5, so “five already exist” holds. But 5 existing + 5 new = 10, not 7, and the five New rows are never reconciled against the headline.
To settle it: Either the headline count or the table is the record. The build order underneath depends on which — it sequences eight steps against rows, not against the seven.
case-engine-architecture.html
Open the instrument →
F4
The New Mexico violation count is still double in one place and half in another
material
The Case Engine states a March 2026 jury found 75,000 violations. The Digital Resilience Lab ledger and Handout 01 — already published — state 37,500 counts. The dollar figure, $375M, is identical in both.
Checkable: 75,000 is exactly twice 37,500. The Case Engine’s corrections register resolves the *money* conflict ($375M + $567M = $942M) and does not touch the count.
To settle it: One transcription is wrong. Both appear in material intended for a facilitator to read aloud.
case-engine-architecture.htmldigitalresiliencelab.bornbetween2generals.com ledger 1.2
Open the instrument →
F5
Two documents disagree about the size of Maricopa’s roll
material
The Maricopa deck says 2.59M registered voters. StrongRoom SE carries 2,540,618, sourced to a Maricopa County elections news release.
Checkable: A 1.9% difference — about 49,000 voters. It changes every per-voter total on both sides of the price question.
To settle it: The sourced figure should win, and the deck should carry the same source line.
Safe-Elections-Maricopa-Pilot.pptx~/strongroom-se/pricing/inputs.mjs
Open the instrument →
F6
A live investor deck ships template placeholders and unagreed partner names
blocking
Protecting Every Home closes on hello@reallygreatsite.com, @reallygreatsite and (12) 3456-7890 — the Canva template’s placeholder contact block. Two slides present Fortinet, Cisco and CrowdStrike as partners. The market chart is the template’s own dummy series.
Checkable: Page 26 is the contact slide. Pages 19–20 name the three vendors. Page 9 plots “Series 1 / Series 2” against “Item 1…Item 6” under the heading “Quantifying growth across intersecting industry sectors”.
To settle it: The market arithmetic does check out — $150B + $6B + $12B = $168B. The placeholders and the partner claims do not, and this deck names a real person and a real email at the top of it.
Presentation - Protecting Every Home copy.pdf
Open the instrument →
F7
An unsourced health rate is stated as established
note
“rising EMF exposure rates at 20% per year” is presented as one of three established threats, with no source and no unit — 20% of what, measured where, by whom.
Checkable: No citation appears anywhere in the deck.
To settle it: On the four-rung ladder this is not rung 4 — a documented measurement — because nobody is named as having measured it. It has no rung.
Presentation - Protecting Every Home copy.pdf
Open the instrument →
F8
Two of the three revenue scenarios do not add up to their own totals
note
Conservative: 115,200 + 90,000 + 60,000 = 265,200, printed as 265,000. Base: 424,440 + 360,000 + 120,000 = 904,440, printed as 904,000. Aggressive: 1,320,000 + 1,200,000 + 300,000 = 2,820,000, printed exactly.
Checkable: Rounding, almost certainly — but two rows round and one does not, so a reader cannot tell by looking whether a total is a sum or a separate estimate.
To settle it: Print the sum or print the rounding rule. Not one row each way.
Intelligence_Workshop_MASTER_COMPLETE/03_REVENUE_AND_PRICING/Revenue_Scenarios.csv
Open the instrument →
F9
One source document is under an executed NDA and is not publishable
blocking
StrongRoom — Technical Architecture and Hosting is marked “Confidential — covered by executed NDA. Not for distribution.” It is the most detailed mechanism document in the set.
Checkable: The marking is on page 1, under the date.
To settle it: Nothing from it is reproduced on this site beyond what the public Safe Elections decks already say. Its own talking notes agree with that rule: “enough mechanism detail for them to evaluate fit, no more.”
StrongRoom-Technical-Architecture-and-Hosting.docx
Open the instrument →
F10
Every source in the set reaches the same conclusion, and none of them acts on it
note
Five separate documents independently conclude that the portfolio must be one substrate configured many ways rather than many applications: the Intelligence Workshop risk register (“Product sprawl — High/High — one substrate”), the PROOFCORE blueprint (“Build one common professional intelligence substrate”), the AI Ecosystem Strategy (“Build these capabilities once”), StrongRoom (“the strong part is built once and kept deliberately small”), and the Case Engine (“do not build a second dashboard”).
Checkable: The Mould Loft is the tool that acts on it. It is the only instrument in the set that will answer “do not build this”.
To settle it: Nothing to settle. It is the finding that decides what this site is.
Intelligence Workshop master packagenick_box_pkg/02_Architecture_Blueprint.mdProfession_in_a_Box_ORIGINAL_AI_Ecosystem_Strategy 2.docxStrongRoom-Technical-Architecture-and-Hosting.docxcase-engine-architecture.html
Open the instrument →