Instrument 04 · runs in your browser
The reconciliation floor
Building something that already exists produces duplicates, not capability. This is the table that decides which is which — and the arithmetic underneath it.
The proposed architecture describes seven products. Five of them already exist in the portfolio under other names. Building them again would produce duplicates, not capability. Here is what is actually new.
case-engine-architecture.html, “Reconciliation”
Finding F3
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.
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.
| Proposed component / what to do about it | Status |
|---|
Against the sentence above the table
Reclassify any row and every figure moves. The counts are computed from the table each time; nothing on this page is a stored number.
Where the five that exist already live
Intelligence Command Center — five live verticals
This is DAYBREAK. Twelve editions run, generator in place, per-item routing to a response app already working. Add the five verticals as filter categories; do not build a second dashboard.
Evidence card on every item
DAYBREAK items already carry Admiralty ratings and the built-how ledger. Add three fields: second-order effects, teaching application, age band.
Evidence Graph — entities, money, routes
The Binney metadata lens plus the Exploitation Network Map. Two-hop walk, unconnected items discarded and shown, private individuals masked. Point the graph at case objects instead of briefing items.
Claim Checker
Galley for manuscript claims, Discern for public claims. Route to them; do not build a third.
Digital Pipeline — grooming and recruitment case files
Module 04 of the Dallas kit plus the Job-Offer Verifier, Forced-Criminality Screening Guide and Sextortion First-Response. The simulated-phone exercise is the one genuinely missing piece.
And the five that do not
All five are built and running on this site. That is what the instruments room is.
Maritime Chokepoint Simulator
No portfolio equivalent. Smallest honest version: EIA throughput volumes with a consequence chain, three reading levels.
Outbreak Detective Lab
No portfolio equivalent. Teaches the case-definition ladder, which is the same skill as the evidence ladder.
Civic Evidence Room — how a rule becomes law
Adjacent to the civic knowledge tests but distinct: procedural literacy, not knowledge testing. Build as a DAYBREAK response app.
Household Economics Simulator
Build it, with the lag rule below enforced in the model. Without that rule it teaches something false.
Simulated-phone grooming exercise
The highest-value new build for Dallas. Marker-based, not scripted: the learner names the behavior, the system does not name it for them.
The build order
Sequenced against the existing Dallas milestones, not added alongside them.
- Reconcile the two documents. Update Refresh No. 01 and the curriculum kit to state the New Mexico components rather than the total alone. Removes the flagged conflict.
- Correct Module 02 framing. Split the four-state and 29-state claim sets in the facilitator text and handouts before print.
- Extend the evidence card. Three new fields on DAYBREAK items: second-order effects, teaching application, age band. No new dashboard.
- Build the simulated-phone exercise. Highest value for Dallas. Marker-based scoring; the learner names the behavior.
- Build the household chain with lag enforced. Month-versus-year toggle is mandatory, not optional.
- Build the chokepoint and outbreak modules. Both keyed to official volumes and case definitions respectively; three reading levels each.
- Build the civic evidence room. Procedural ladder with the actual filings linked at each rung.
- Point the graph at case objects. Existing Binney lens, new input type. Two-hop limit and masking rules unchanged.