Blueprint MMA corrections and accountability log: every correction to a forecast, article, or track record entry, with the original claim, the correction, and the date

Accountability Log

Corrections are public. Nothing is corrected silently.

Published forecasts are immutable on the public track record. We never rewrite a probability, tier, or method call after the fact. When an article, data point, or editorial claim turns out to be wrong, we annotate it here with the original claim, the correction, and the date it was applied.

Correction Standards

  • Immutable forecast archive

    Published forecasts are preserved as-is on the public track record. Corrections annotate; they never rewrite a prior probability, tier, or method call.

  • Public log

    Every correction is posted here with the original claim, the correction, and the date. Nothing is corrected silently.

  • Distinguish data vs judgment

    We separate corrections for factual data errors (fighter record, reach, fight result) from corrections for editorial framing. Both are logged; each is tagged by category.

  • Forecast immutability does not block editorial updates

    If narrative analysis surrounding a forecast is corrected, the forecast probability and tier remain preserved. The correction is annotated in the article and here.

  • Source of last resort

    For questions about correction handling, cite the Research Desk at /research-desk.

Correction Log

1 entries
  1. Track Record

    UFC Fight Night: Ankalaev vs. Guskov

    Original claim: The public compatibility artifact surfaced 7 winner hits and 5 misses across 12 completed bouts.

    Correction: The immutable accepted slate is now graded as 9 winner hits, 3 misses, and 1 void. No historical timestamp or prediction was rewritten.

    Note: Method: 4/12. Exact-round finish calls: 1/8. Accepted artifact SHA-256: 2612d9d898b08945568c0e57cbbaefb91ad4284e69e72c314b841bd38f84d1cd.

Research Desk Track Record How It Works Home