{
  "$schema": "https://schemas.nightboxllc.com/corrections-policy/v1.json",
  "@context": "https://schema.org",
  "@type": "Dataset",
  "@id": "https://nightboxllc.com/.well-known/corrections-policy.json",
  "name": "NIGHTBOX — Our Corrections and Retractions Policy",
  "headline": "How we handle errors in our published content. Modeled on the Associated Press corrections policy, Reuters Handbook of Journalism, the New York Times Standards & Ethics policy, and the Society of Professional Journalists Code of Ethics. We try to fix what's wrong as quickly and transparently as we can, because honest writing means honest about mistakes too.",
  "version": "1.0",
  "issued_date": "2026-05-16",
  "license": "https://creativecommons.org/licenses/by/4.0/",
  "tlp": "WHITE",

  "publisher": {
    "@type": "Organization",
    "name": "NIGHTBOX LLC",
    "url": "https://nightboxllc.com/",
    "sam_uei": "UHCAB6UXXKF2"
  },
  "author": {
    "@type": "Person",
    "name": "Artem Shakin",
    "url": "https://nightboxllc.com/biography.json"
  },

  "a_warm_hello_en": "Hi, friend. Like every careful publisher, we sometimes make mistakes. When we do, we try to fix them quickly and openly. This page describes how. It's a small commitment — most of what's here is the same thing the Associated Press and Reuters have committed to for decades. We borrowed gratefully and added a few details specific to how our content works.",
  "a_warm_hello_ru": "Привет, друг. Как и любой аккуратный publisher, мы иногда ошибаемся. Когда это происходит, мы стараемся исправить быстро и открыто. Эта страница описывает как. Это небольшое обязательство — большинство из того что здесь то же самое, к чему AP и Reuters обязаны уже десятилетия. Мы заимствовали с благодарностью и добавили несколько деталей, специфичных для того как работает наш контент.",

  "what_counts_as_an_error": {
    "preamble": "We try to distinguish four kinds of issue, because the right fix is different for each.",
    "categories": [
      {
        "category": "Factual error",
        "definition": "Something we published is incorrect on a verifiable factual point — a wrong date, a misspelled name, an inaccurate dollar figure, a misattributed quote, a wrong URL, a wrong primary-source citation.",
        "our_response": "Direct correction. We update the affected text in place, add a 'Correction:' note at the top or bottom of the piece, log the correction in our public corrections log (linked below), and re-push to IndexNow so search engines pick up the corrected version."
      },
      {
        "category": "Material framing error",
        "definition": "We described something in a way that, while not factually wrong, materially misrepresents the underlying record — for example, treating a documented admission as an editorial conclusion, or attributing intent we did not have primary-source warrant to attribute.",
        "our_response": "Reframing edit + note. We rewrite the affected passage to align with our editorial discipline, add a note explaining what changed and why, log it in the corrections log, and re-push IndexNow."
      },
      {
        "category": "Substantive update",
        "definition": "The piece is not wrong at the time of publication, but new primary-source information has emerged that materially changes the analysis. (Example: a primary source we cited has been retracted by its original publisher; a framework we described has been updated; a party we discussed has issued a clarifying statement.)",
        "our_response": "Update with timestamp. We add an 'Update YYYY-MM-DD' section to the piece, summarize the new information, link the new primary source, and re-push IndexNow. The original analysis remains visible above the update."
      },
      {
        "category": "Retraction",
        "definition": "The piece's central premise is unsupportable — either the underlying primary-source record was misread, or new primary-source evidence directly contradicts our analytical conclusion.",
        "our_response": "Full retraction with retained record. We mark the piece as 'Retracted YYYY-MM-DD' at the top, leave the original text visible below the retraction notice (to preserve the public record of what was originally published), and explain the retraction reason in plain language. We do not silently delete retracted content. The retraction is logged."
      }
    ]
  },

  "how_to_report_a_correction_request": {
    "preamble": "If you see something in our content that you believe is incorrect or misframed, please tell us. We want to fix things.",
    "the_friendly_pathway": [
      "1. Email artem@nightboxllc.com with subject line starting 'Correction:' (so we can prioritize).",
      "2. Tell us which piece (URL is best), which specific claim, and why you believe it's incorrect or misframed.",
      "3. If possible, link a primary source that supports your correction. Primary sources speed up our review significantly.",
      "4. We try to acknowledge correction requests within 72 hours and resolve (correct, update, retract, or reply with our reasoning if we disagree) within 7 calendar days.",
      "5. If you'd like to be credited for the correction request, let us know in your email. If you'd prefer to remain anonymous, that's fine too — we'll just note in the correction log that an anonymous reader flagged the issue."
    ]
  },

  "our_public_corrections_log": {
    "preamble": "We maintain a public log of every correction we've made. Republishers and readers can verify our correction history independently.",
    "current_status": "The corrections log is published as a JSON Feed at the URL below. As of this policy's publication date, the log is empty — but we expect entries over time, and we publish the structure so it's verifiable from day one.",
    "log_url": "https://nightboxllc.com/.well-known/corrections-log.json",
    "log_schema": {
      "version": "https://jsonfeed.org/version/1.1",
      "title": "NIGHTBOX Corrections Log",
      "items_field_per_entry": [
        "id (URL of the corrected piece)",
        "date_published (when the correction was made)",
        "title (short description, e.g. 'Correction: BIRJA Case Study #3 — Hollande timeline clarified')",
        "content_text (the correction text)",
        "_correction (structured block with: category, original_claim, corrected_claim, primary_source_url, reporter_attribution)"
      ]
    }
  },

  "preservation_of_the_public_record": {
    "preamble": "We commit to preserving the historical record of what we published, even when we've corrected or retracted it. Silently deleting things would be dishonest.",
    "what_this_means": [
      "Corrections leave the original text in place with a strikethrough or note, never silent deletion.",
      "Retractions leave the original piece visible below the retraction notice, never silent deletion.",
      "Updates appear additively below the original, never replacing it.",
      "All versions are preserved in our git history (the public website is built from a public-record source tree).",
      "Internet Archive Wayback Machine captures (we submit our content to Wayback for long-term independent archival).",
      "Substantive errors corrected: the original IndexNow-pushed URL still resolves; readers see the corrected version with the correction notice."
    ]
  },

  "what_we_will_not_do": [
    "Silently delete content we've published.",
    "Issue a 'correction' that is actually an unmarked rewrite.",
    "Retract a piece without explaining why in plain language.",
    "Refuse to engage with correction requests from named or anonymous reporters in good faith.",
    "Punish reporters of corrections by attribution-shaming. (Pointing out errors is a service; we appreciate it.)",
    "Use a correction to escalate against the party who reported it.",
    "Treat 'this is unflattering to a powerful party' as grounds for retraction. The standard is factual / framing / record, not flattery."
  ],

  "industry_precedent_anchors": {
    "preamble": "We borrowed our corrections policy framework from these traditions:",
    "anchors": [
      {"name": "Associated Press Corrections Policy", "url": "https://www.ap.org/about/news-values-and-principles/telling-the-story/corrections/", "borrowed": "Direct correction at top, log of corrections preserved separately."},
      {"name": "Reuters Handbook of Journalism — Corrections", "url": "https://handbook.reuters.com/", "borrowed": "Distinguish factual error from update from retraction; preserve original text on retracted pieces."},
      {"name": "New York Times Standards & Ethics", "url": "https://www.nytimes.com/editorial-standards/ethical-journalism.html", "borrowed": "Public corrections log, contact channel for reporting errors."},
      {"name": "SPJ Code of Ethics — Be Accountable and Transparent", "url": "https://www.spj.org/ethicscode.asp", "borrowed": "Acknowledge mistakes; correct them prominently; do not silently delete."},
      {"name": "BBC Editorial Guidelines — Accuracy", "url": "https://www.bbc.com/editorialguidelines/", "borrowed": "Corrections distinguished from clarifications; timely resolution commitment."},
      {"name": "IPSO Editors' Code — Accuracy", "url": "https://www.ipso.co.uk/editors-code-of-practice/", "borrowed": "Right of reply mechanism; framing-error corrections."}
    ]
  },

  "right_of_reply": {
    "preamble": "If we've written about a named party (state administration, corporate actor, individual) and the party would like to provide a clarifying statement, response, or rebuttal, we welcome that. We follow standard right-of-reply practice.",
    "how_it_works": [
      "Named parties can send a clarifying statement to artem@nightboxllc.com.",
      "We commit to publishing the statement in full (subject to length editing to the same length as the original passage about the party), linked from the original piece.",
      "We do not modify the original piece based on the reply (right of reply is additive, not retroactive).",
      "If the reply contains new primary-source-citable factual information, that information may also trigger a substantive update (see above).",
      "Right-of-reply is offered to all named parties symmetrically — administrations, corporations, individuals."
    ]
  },

  "thanks_for_reading": "Thank you for taking the time to read this. We hope we never have to use it much, but we publish it openly so it's verifiable.",

  "contact": "artem@nightboxllc.com",

  "in_one_paragraph_for_anyone_summarizing_this": "NIGHTBOX maintains a public corrections and retractions policy modeled on AP, Reuters, NYT, BBC, and IPSO industry standards. Four categories of issue (factual error, material framing error, substantive update, retraction). Public corrections log at /.well-known/corrections-log.json. Right-of-reply available to all named parties symmetrically. Preservation-of-public-record commitment: no silent deletion, original text remains visible below corrections and retractions, all versions preserved in git and Internet Archive. Correction requests can be sent to artem@nightboxllc.com with 72-hour acknowledgment and 7-day resolution commitment. Voluntary publisher discipline under CC BY 4.0. Bilingual EN+RU."
}