{
  "title": "Hydropower reporting intervals for AI evaluation",
  "source_page": "https://fiund.com/industries/hydropower-generation-interval-data",
  "authorship": "Original fictional Fiund editorial exercise. No actual operating records or third-party source assets are included.",
  "example": {
    "title": "Check observation membership in a stated reporting window",
    "context": "An original reporting exercise uses artificial values and a UTC month boundary. It tests time alignment, not hydropower operations or causal performance analysis.",
    "records": [
      [
        "REPORT-H1",
        "Practice monthly definition",
        "January covers January 1 at 00:00 UTC up to, but not including, February 1 at 00:00 UTC."
      ],
      [
        "OBS-H2",
        "First practice observation",
        "The timestamp is January 17 at 12:00 UTC."
      ],
      [
        "OBS-H3",
        "Offset-clock observation",
        "The timestamp is January 31 at 23:30 with UTC offset minus two hours."
      ],
      [
        "TOTAL-H4",
        "Monthly practice aggregate",
        "A generation total is labeled for H1's January window, without an explanation of any change."
      ]
    ],
    "question": "Which observation lies within H1's January window? Does membership explain the monthly generation figure?",
    "answer": "H2 lies within the stated January window. H3 converts to February 1 at 01:30 UTC, outside that window. A shared reporting interval would only establish alignment; it would not prove why a monthly figure changed or make a single observation representative of the whole month. The aggregate supplies no causal explanation.",
    "failureModes": [
      "Assigning H3 to January from its displayed local date alone.",
      "Treating one aligned observation as a demonstrated cause of a monthly change."
    ],
    "fields": [
      [
        "Window convention",
        "Preserve the included start and excluded end."
      ],
      [
        "Timestamp and offset",
        "Convert observations on their actual stated basis."
      ],
      [
        "Aggregation scope",
        "Keep a point observation distinct from a monthly total."
      ]
    ],
    "holdout": "Add an observation exactly at February 1 at 00:00 UTC. Under H1's rule it belongs outside January.",
    "boundary": "Use invented records or cleared public aggregates. Exclude dam controls, reservoir operating information, security details, real locations and raw telemetry."
  }
}