delphi.question.published

{
  "slug": "will-copernicus-rank-2026-among-the-three-warmest-calendar-years-in-its-record",
  "title": "Will Copernicus rank 2026 among the three warmest calendar years in its record?",
  "origin": "EDITORIAL",
  "timebase": {
    "clock": "REAL_UTC"
  },
  "closes_at": "2026-12-15T22:00:00.000000Z",
  "opened_at": "2026-08-15T15:53:37.279942Z",
  "blind_mode": true,
  "provenance": "PUBLIC_RECORD",
  "description": "The longest question in this batch by design. It closes in December and resolves in January, so it is the one question whose forecasters commit before a full quarter of the evidence exists.",
  "question_id": "07df80b9-b32c-4db8-ad24-19034793b27c",
  "resolution_criteria": "YES if the Copernicus annual climate bulletin for 2026 places the year first, second or third warmest in the ERA5 record.",
  "expected_resolution_at": "2027-01-15T12:00:00.000000Z",
  "canonical_source_policy": "Copernicus climate bulletin at https://climate.copernicus.eu/climate-bulletin, annual summary for 2026.",
  "resolution_rule_revision": 1
}

Shown indented so it can be read. The hash is taken over the canonical form of the same object — keys sorted by code point, no insignificant whitespace, UTF-8 rather than escaped ASCII, timestamps RFC 3339 in UTC to microseconds, decimals as their plain string form. The check below re-encodes the object canonically before hashing it, which is why an indented display cannot make it pass or fail.