Schema and classification-vocabulary reconciliation
§3 — Schema and classification-vocabulary reconciliation
Phase 7 §33 demanded this explicitly: "Phase 8 must reconcile this schema divergence." Phase 1 §2 (SETUP-002) demanded that Phases 2–7 be notified of a prior change. Neither instruction was fully carried out.
3.1 Five vocabularies are in use across eight phases
| Source | Vocabulary | Used by |
|---|---|---|
| Phase 0 §3.2 | CONFIRMED · OFFICIAL-FINDING · CHARGED-OR-FORMALLY-ALLEGED · REPORTED-SINGLE-SOURCE · DISPUTED · RUMOR · INFERENCE · UNSUPPORTED · FALSE · RETRACTED (10) | Phase 5 |
| Project Handoff p.7 | Confirmed fact · Credible reported allegation · Disputed interpretation · Circumstantial connection · Analytical inference · Unsupported or false · Not independently verified (7) | Phases 1, 3, 6 (via SETUP-002) |
| Phase 2 ad hoc | VERIFIED FACT · REPORTED ALLEGATION · ANALYSIS · UNVERIFIED · ATTRIBUTED RUMOUR · CONTRADICTED · NULL — plus direction tags (BENEFITED / HARMED / NEUTRAL / MIXED) | Phase 2 only |
| Phase 7 brief | Phase 0's list minus INFERENCE, UNSUPPORTED, FALSE, RETRACTED, plus INDEPENDENTLY-CORROBORATED, NOT-SUBSTANTIATED, DEVELOPING, NOT-FOUND | Phase 7 |
| Stage documents | Confirmed fact · Disputed interpretation · Commercial inference · Unsupported allegation · Not established on retrieved record | Stages 1–2 |
3.2 What went wrong
SETUP-002 (Phase 1) resolved a genuine governance collision correctly: the Handoff is the older, governing authority, so its 7 labels became PRIMARY and Phase 0's tags became SECONDARY. It then instructed: "Phases 2–7 must be notified, or Phase 8 reconciliation will surface a false 'conflict' that is merely a vocabulary change."
The notification reached Phases 3 and 6. It did not reach Phases 2, 5 or 7. Phase 5 was still applying Phase 0's superseded 10-value list. Phase 7 was applying a third list its own brief supplied, and flagged the divergence itself. Phase 2 never adopted any of the project's vocabularies.
3.3 The binding mapping (Phase 8 ruling)
Phase 1's SETUP-002 mapping stands and is extended to the two vocabularies it did not cover:
| Phase 2 term | Phase 7 term | Stage term | → Handoff PRIMARY label |
|---|---|---|---|
| VERIFIED FACT | CONFIRMED / INDEPENDENTLY-CORROBORATED | Confirmed fact | Confirmed fact |
| — | OFFICIAL-FINDING | — | Confirmed fact (+ secondary: official finding) |
| REPORTED ALLEGATION | CHARGED-OR-FORMALLY-ALLEGED | — | Credible reported allegation |
| UNVERIFIED / NULL | REPORTED-SINGLE-SOURCE / NOT-FOUND | Not established on retrieved record | Not independently verified |
| ANALYSIS | (carried in "Allegation or interpretation", prefixed INFERENCE:) | Commercial inference | Analytical inference |
| ATTRIBUTED RUMOUR | — | — | Not independently verified or Unsupported or false, case by case |
| CONTRADICTED | NOT-SUBSTANTIATED | Unsupported allegation | Unsupported or false |
| — | DEVELOPING | — | no equivalent — see 3.5 |
| — | — | Disputed interpretation | Disputed interpretation |
Direction tags (Phase 2, Phase 6): BENEFITED / HARMED / NEUTRAL / MIXED are orthogonal to claim classification and are preserved as a separate axis. They are not evidence status and must never be mapped onto one.
3.4 Two schema items Phase 8 must answer, not defer
- Phase 3 open question #2 — "Recover Phase 2's ARG-### IDs." Answer: they do not exist. The Phase 2 output in the Project contains zero
ARG-###identifiers. Every Phase 3 cross-reference to Phase 2 material (Grondona's death, Segura's interim presidency, the 38-38 election, the DOJ indictments) is therefore permanently descriptive rather than ID-linked, unless the Phase 2 base deliverable surfaces. Do not renumber — Phase 0 §3.1 rule 3 makes IDs permanent, and inventingARG-###numbers now would create identifiers no earlier phase can have meant. - Phase 0 §3.5 — the incident-ID convention (
PARENT-ID-INC##). Adopted in practice and confirmed. Phase 6 usesTOURN-032-INC01…INC07,TOURN-038-INC01…INC05,TOURN-039-INC01…INC06. Phase 7 usesMIA-025-INC01,MIA-033-INC01/02/03. The provisional rule worked; it is now settled.
3.5 DEVELOPING has no home in the governing vocabulary — ruling
Phase 7's DEVELOPING (used for MIA-023 and MIA-034) has no equivalent in the Handoff's 7 labels and cannot be mapped without loss. Ruling: preserve it as a secondary status tag, never as a primary classification. A developing item carries its primary label for what is established (Confirmed fact for played matches) plus (secondary: DEVELOPING as of YYYY-MM-DD). Phase 0 GAP-4 anticipated exactly this: "Do not let Phase 8 merge stale Phase 7 output as settled." Honoured — see §24.