Contradiction detector
5 disagreements, found by machine, printed rather than resolved.
The detector was pointed at the staging folder. It extracted 9 checkable claims — a claim being a value at a locator, never a sentence somebody typed into a note — and compared them. What follows is what it found. Nothing here was corrected in the source files, and that is the point: editing an input so it agrees with a rule destroys the evidence that they ever disagreed.
A detector that fires on everything is measuring nothing. Three revenue rows were tested for arithmetic. Two are reported below. The third — Aggressive — adds up to the cent and is not listed.
Two of your own documents disagree. Somebody should say so out loud.
Finding 1 of 5
Pricing tier — Explorer POLICY CONFLICT
The tier sheet prices "Explorer" at Free. The standing access policy says nothing is free.
| Side | Value | Where it comes from |
|---|---|---|
| the source says | Explorer = Free | 03_DATASETS/Pricing_Tiers.csvrow 2, column "Price Concept" |
| the standing policy says | Nothing is free. Nonprofits may apply and still pay hosting and maintenance; every other buyer purchases the site. | BB2G access policy (Kristen Hall, 10 August 2026)standing instruction, not a file in this staging folder |
How it is handled: The CSV is kept exactly as written — it is the evidence that the proposal said this. Nothing published from this studio carries the word.
Finding 2 of 5
Revenue scenario — Conservative SUM MISMATCH
Revenue scenario — Conservative: the parts add to $265,200, the row states $265,000.
| Side | Value | Where it comes from |
|---|---|---|
| stated total | $265,000 | 03_DATASETS/Revenue_Scenarios.csvrow 2, columns Consumer/Team Run-Rate..Approx Total |
| parts as summed | $265,200 | 03_DATASETS/Revenue_Scenarios.csvConsumer/Team Run-Rate + Enterprise + Courses/Tools |
How it is handled: Neither number is corrected here. The row is reported as it stands and the arithmetic beside it.
Finding 3 of 5
Revenue scenario — Base SUM MISMATCH
Revenue scenario — Base: the parts add to $904,440, the row states $904,000.
| Side | Value | Where it comes from |
|---|---|---|
| stated total | $904,000 | 03_DATASETS/Revenue_Scenarios.csvrow 3, columns Consumer/Team Run-Rate..Approx Total |
| parts as summed | $904,440 | 03_DATASETS/Revenue_Scenarios.csvConsumer/Team Run-Rate + Enterprise + Courses/Tools |
How it is handled: Neither number is corrected here. The row is reported as it stands and the arithmetic beside it.
Finding 4 of 5
bornbetween2generals.com estate — addresses on the domain VALUE CONFLICT
2 sources give 2 different values for addresses on the domain of bornbetween2generals.com estate.
| Side | Value | Where it comes from |
|---|---|---|
| 06_APP_SPECIFICATIONS/BB2G Election Command and LockChain_ Full Production Build Blueprint.docx as at 2026-08-04 | 301 | 06_APP_SPECIFICATIONS/BB2G Election Command and LockChain_ Full Production Build Blueprint.docxexecutive finding, sentence citing the BB2G Standard |
| 03_DATASETS/bb2g_fleet_probe_2026-08-15.json as at 2026-08-15 | 543 | 03_DATASETS/bb2g_fleet_probe_2026-08-15.jsontotals.live |
How it is handled: Where the sources carry dates, the fresher one is shown first. It is not therefore correct, and the older is not deleted.
Finding 5 of 5
MBLTS VERSION CONFLICT
3 documents in the staging folder specify MBLTS, at 1.0, (no version line), 1.1 draft.
| Side | Value | Where it comes from |
|---|---|---|
| 1.0 — Draft architecture and implementation specification | Complete Mail-Ballot Lifecycle Token Specification | 06_APP_SPECIFICATIONS/complete_mail_ballot_lifecycle_token_specification.mdfront matter |
| (no version line) — architecture and implementation starter specification | Privacy-Preserving Mail-Ballot Lifecycle Token System | 06_APP_SPECIFICATIONS/mail_ballot_lifecycle_token_design.mdfront matter |
| 1.1 draft — (no status line) | Unified Mail-Ballot Lifecycle Token Specification | 06_APP_SPECIFICATIONS/unified_mail_ballot_lifecycle_token_specification.mdfront matter |
How it is handled: The supersession engine resolves which one governs. Until a chain says so, an answer drawn from any of them names its version.
The claims it extracted
Every one read out of a file at a locator, carrying the digest of the file it came from. If a file changes, its digest changes and the finding is rebuilt rather than inherited.
| Kind | Claim | Source | Locator | Digest |
|---|---|---|---|---|
| SUM | Revenue scenario — Conservative total $265,000 | Revenue_Scenarios.csv | row 2, columns Consumer/Team Run-Rate..Approx Total | 30e8567e3f… |
| SUM | Revenue scenario — Base total $904,000 | Revenue_Scenarios.csv | row 3, columns Consumer/Team Run-Rate..Approx Total | 30e8567e3f… |
| SUM | Revenue scenario — Aggressive total $2,820,000 | Revenue_Scenarios.csv | row 4, columns Consumer/Team Run-Rate..Approx Total | 30e8567e3f… |
| VALUE | bornbetween2generals.com estate — addresses on the domain = 301 | BB2G Election Command and LockChain_ Full Production Build Blueprint.docx | executive finding, sentence citing the BB2G Standard | a4e70453cd… |
| VALUE | bornbetween2generals.com estate — addresses on the domain = 543 | bb2g_fleet_probe_2026-08-15.json | totals.live | ea4f8183d7… |
| POLICY | Pricing tier — Explorer | Pricing_Tiers.csv | row 2, column "Price Concept" | 86aa2adf6c… |
| VERSION | MBLTS 1.0 | complete_mail_ballot_lifecycle_token_specification.md | front matter | 9d40107c16… |
| VERSION | MBLTS (no version line) | mail_ballot_lifecycle_token_design.md | front matter | f5df771255… |
| VERSION | MBLTS 1.1 draft | unified_mail_ballot_lifecycle_token_specification.md | front matter | 4122a2735f… |
The four kinds it can find
Sum mismatch
A stated total against its own stated parts. Tolerance is zero — a rounding convention should be written down, not inferred from the size of the gap.
Value conflict
The same subject and metric measured twice with different results. Where the sources carry dates the fresher is shown first, which does not make it correct, and the older is not deleted.
Policy conflict
A source asserting something a standing policy forbids. The source is preserved exactly as written; the policy governs only what ships.
Version conflict
Several documents specifying one system at different versions. Handed to the supersession engine, which will report "under-determined" rather than pick the highest number.