{
  "schema": "longtermintelligence-corrections-registry-v1",
  "version": "1.6.0",
  "generatedOn": "2026-08-01",
  "policyPath": "/research/corrections/",
  "usageBoundary": "Corrections preserve the historical source wording while identifying current public language and supporting references.",
  "corrections": [
    {
      "id": "federal-ai-policy-m24-10",
      "publishedLanguage": "Earlier strategy material treated OMB M-24-10 as the active federal agency AI memorandum.",
      "correctedLanguage": "OMB M-25-21, issued April 3, 2025, rescinds and replaces M-24-10. Public federal-policy guidance should cite M-25-21 and distinguish covered agency requirements from private-sector practices.",
      "effectiveOn": "2025-04-03",
      "recordedOn": "2026-08-01",
      "status": "corrected",
      "referenceIds": [
        "omb-m25-21"
      ],
      "affectedSourceIds": [
        "brand-positioning",
        "trust-authority",
        "editorial-strategy"
      ]
    },
    {
      "id": "eu-ai-act-timetable-2026",
      "publishedLanguage": "Earlier strategy material used pre-Omnibus descriptions of the EU AI Act timetable and sometimes implied a single August 2026 high-risk enforcement date.",
      "correctedLanguage": "The July 2026 AI Omnibus amended parts of the timetable. Public content should use the Commission's current overview and Omnibus update, state specific dates only with scope, and avoid collapsing transparency, governance, and high-risk obligations into one deadline.",
      "effectiveOn": "2026-07-27",
      "recordedOn": "2026-08-01",
      "status": "corrected",
      "referenceIds": [
        "eu-ai-act-overview",
        "eu-ai-omnibus-2026"
      ],
      "affectedSourceIds": [
        "demand-generation",
        "competitive-landscape",
        "brand-positioning",
        "trust-authority",
        "go-to-market",
        "editorial-strategy"
      ]
    },
    {
      "id": "nist-ai-rmf-revision-status",
      "publishedLanguage": "Earlier copy could be read as if AI RMF 1.0 were static and final.",
      "correctedLanguage": "AI RMF 1.0 remains the published core version, but NIST's AI Resource Center states that it is being revised. Pages must show the reviewed date and avoid implying permanence.",
      "recordedOn": "2026-08-01",
      "status": "clarified",
      "referenceIds": [
        "nist-airc",
        "nist-ai-rmf-core"
      ],
      "affectedSourceIds": []
    },
    {
      "id": "mcp-version-and-scope",
      "publishedLanguage": "Earlier content discussed MCP generically and sometimes positioned it too close to a complete agent control plane.",
      "correctedLanguage": "The reviewed protocol version is dated 2026-07-28. MCP connects applications with resources, prompts, and tools; identity governance, policy enforcement, evaluation, budgeting, recovery, and human authority remain separate architectural responsibilities.",
      "recordedOn": "2026-08-01",
      "status": "clarified",
      "referenceIds": [
        "mcp-specification-2026-07-28",
        "mcp-architecture"
      ],
      "affectedSourceIds": [
        "brand-positioning",
        "trust-authority",
        "go-to-market",
        "editorial-strategy"
      ]
    },
    {
      "id": "opentelemetry-scope",
      "publishedLanguage": "Earlier content could be read as if OpenTelemetry alone delivered complete AI observability and evaluation.",
      "correctedLanguage": "OpenTelemetry provides interoperable telemetry conventions and transport. Correctness evaluation, policy decisions, redaction, retention, and incident procedures still require explicit design, and the exact semantic-convention version should be recorded.",
      "recordedOn": "2026-08-01",
      "status": "clarified",
      "referenceIds": [
        "opentelemetry-genai-observability",
        "opentelemetry-genai-semconv"
      ],
      "affectedSourceIds": [
        "brand-positioning",
        "editorial-strategy"
      ]
    },
    {
      "id": "standards-alignment-not-certification",
      "publishedLanguage": "Strategy language sometimes used strong phrases about operationalizing standards without consistently separating alignment from certification.",
      "correctedLanguage": "Mapping controls or evidence to NIST, ISO, OWASP, or policy sources is an alignment activity. Certification, legal compliance, and assurance require the applicable formal process and qualified reviewers.",
      "recordedOn": "2026-08-01",
      "status": "clarified",
      "referenceIds": [
        "iso-iec-42001",
        "iso-iec-42006",
        "nist-ai-rmf"
      ],
      "affectedSourceIds": [
        "brand-positioning",
        "trust-authority",
        "go-to-market"
      ]
    },
    {
      "id": "source-report-market-statistics",
      "publishedLanguage": "The six independent-agent reports contain numerous market statistics and event claims from mixed-quality secondary sources.",
      "correctedLanguage": "Those statistics remain preserved as source-derived strategy material but are not approved for first-party public claims without independent verification against an authoritative source and an as-of date.",
      "recordedOn": "2026-08-01",
      "status": "boundary-reinforced",
      "referenceIds": [],
      "affectedSourceIds": [
        "demand-generation",
        "competitive-landscape",
        "brand-positioning",
        "trust-authority",
        "go-to-market",
        "editorial-strategy"
      ]
    }
  ]
}