{
  "title": "Bulk electric transmission aggregates for offline AI review",
  "source_page": "https://fiund.com/industries/bulk-electric-transmission-aggregate-data",
  "authorship": "Original fictional Fiund editorial exercise. No actual operating records or third-party source assets are included.",
  "example": {
    "title": "Read a public-style aggregate at an earlier cutoff",
    "context": "Original historical aggregates use demonstration counts and contain no infrastructure events or topology. The question concerns document availability and period matching.",
    "records": [
      [
        "JUNE-V1",
        "Initial practice summary",
        "Published on day 2, June's aggregate is 140 demonstration counts."
      ],
      [
        "JUNE-V2",
        "Later correction",
        "Published on day 10, the June aggregate is revised to 150. No underlying event or reason is provided."
      ],
      [
        "JULY-V1",
        "Different-period summary",
        "Published on day 6, July's similarly titled summary records 150 counts."
      ]
    ],
    "question": "Which June value was supplied by day 8, and do the records explain why June was later revised?",
    "answer": "JUNE-V1 is the supplied June publication available by day 8, so the supported earlier-cutoff value is 140. JUNE-V2 documents a later revision to 150 but was not yet available at that cutoff. JULY-V1 concerns another period. None of these aggregate records establishes the underlying cause of June's revision.",
    "failureModes": [
      "Using a later correction to describe information already available at an earlier cutoff.",
      "Substituting July's matching number for June's source.",
      "Inventing an operational event to explain an unexplained aggregate revision."
    ],
    "fields": [
      [
        "Reporting period",
        "Keep June and July aggregates distinct."
      ],
      [
        "Publication cutoff",
        "Preserve when each version became available."
      ],
      [
        "Revision lineage",
        "Link the correction to the earlier summary without inventing its cause."
      ]
    ],
    "holdout": "Add a dated explanatory note after day 10 and ask separately for the earlier available information and the latest documented explanation.",
    "boundary": "Use fictional or cleared public aggregates only. Exclude real topology, control messages, configurations, facilities, locations and live feeds. No switching or balancing decision is in scope."
  }
}