{
  "schemaVersion": "1.0",
  "lastUpdated": "2026-08-31",
  "policy": {
    "principle": "Correct the public claim, preserve the original run, and publish enough evidence to reconstruct what changed and why.",
    "scope": [
      "numerical or statistical errors",
      "data provenance, licensing, or attribution errors",
      "methodology and validation errors",
      "materially misleading chart or editorial claims",
      "incorrect AI model, role, or review disclosures",
      "privacy, persistence, subscription, support, or other material operating claims"
    ],
    "severityLevels": [
      {
        "level": "material",
        "definition": "Changes the central result, decision guidance, population, uncertainty, source rights, or review status.",
        "response": "Freeze promotion or add an article-level correction, rerun affected gates, preserve the superseded run, and include the correction in the next available reader update."
      },
      {
        "level": "clarification",
        "definition": "Improves scope or interpretation without changing the reported result.",
        "response": "Update the article with a dated note and record the changed language in this ledger."
      },
      {
        "level": "minor",
        "definition": "Typography or presentation that cannot alter the reader's interpretation.",
        "response": "Correct in place; ledger inclusion is optional unless the error recurs or affects an artifact."
      }
    ],
    "workflow": [
      "Triage the claim and identify every affected public surface.",
      "Freeze publication or promotion when reader guidance may be wrong.",
      "Preserve the original run, hashes, reviews, and decision artifacts.",
      "Recompute and repeat the relevant specialist and mechanical checks.",
      "Publish a dated correction or withholding note with evidence links.",
      "Update the machine-readable ledger and article disclosure together."
    ],
    "reportingStatus": "A durable public correction-intake address is not connected yet. This remains an explicit operating-readiness blocker."
  },
  "entries": [
    {
      "id": "COR-001",
      "recordedAt": "2026-08-31T02:45:00+00:00",
      "type": "prepublication_hold",
      "severity": "material",
      "status": "resolved_by_withholding",
      "surface": "Touchdown Regression 2025 candidate",
      "runId": "2026-08-31T011519Z-touchdown-regression-v1",
      "summary": "Visual QA found prior-sample values in two otherwise current chart titles after the research gate passed.",
      "readerImpact": "None. The candidate was never promoted; the published 2024 launch article remained unchanged.",
      "resolution": "The run was preserved and marked not published. Future figures are generated from a title/metric/hash contract independently checked by both the research gate and promotion command.",
      "evidence": [
        {
          "label": "Withholding process note",
          "href": "/research-artifacts/2026-08-31T011519Z-touchdown-regression-v1/process-note.json"
        },
        {
          "label": "Failure and release-pattern article",
          "href": "/journal/first-glm-run-passed"
        },
        {
          "label": "Publication decision at run time",
          "href": "/research-artifacts/2026-08-31T011519Z-touchdown-regression-v1/publication-decision.json"
        }
      ]
    },
    {
      "id": "COR-002",
      "recordedAt": "2026-08-31T04:15:00+00:00",
      "type": "operational_correction",
      "severity": "material",
      "status": "resolved_by_closing_capture",
      "surface": "Production newsletter signup",
      "summary": "The newsletter form could return a success message after writing an address to container-bound prototype storage that was not durable on Render.",
      "readerImpact": "Anyone who previously submitted an address should not assume it was retained or that they are subscribed. No outbound newsletter delivery was connected.",
      "resolution": "Production capture is now paused and the API fails closed unless durable mode is deliberately enabled. The privacy disclosure, homepage, readiness evidence, and form state now name the gap. Reopening requires managed storage, delivery, double opt-in, unsubscribe handling, and a durable support path.",
      "evidence": [
        {
          "label": "Privacy and newsletter disclosure",
          "href": "/privacy#newsletter"
        },
        {
          "label": "Value-first readiness ledger",
          "href": "/readiness#stripe"
        },
        {
          "label": "Operating rationale",
          "href": "/journal/value-before-monetization"
        }
      ]
    }
  ]
}