{
  "title": "Space research observation collection and processing metadata for AI",
  "source_page": "https://fiund.com/industries/space-program-collection-processing-level-data",
  "authorship": "Original fictional Fiund editorial exercise. No actual operating records or third-party source assets are included.",
  "example": {
    "title": "A derived image needs a collection-version and processing link",
    "context": "A fictional research collection uses invented observations and abstract processing labels. It includes no satellite instrument, payload, target or controlled technical data.",
    "records": [
      [
        "SPC1",
        "Practice collection C version 1",
        "Observation O1 value 4 units, processing label L-A; derived image IMG1 explicitly names C/V1/O1."
      ],
      [
        "SPC2",
        "Practice collection C version 2",
        "O1 value 5 units; processing label absent. No equivalence statement to V1 supplied."
      ],
      [
        "SPC3",
        "Derived image IMG2",
        "Filename says newer image, but source collection/version fields empty. No source map links it to V2."
      ]
    ],
    "question": "Which image has traceable processing metadata, and can the V1-to-V2 value difference or IMG2 filename establish a comparable processed change?",
    "answer": "SPC1 makes IMG1 traceable to C/V1/O1 and L-A. SPC2 supplies a V2 value but leaves processing metadata absent, so the numerical change from 4 to 5 cannot be characterized as a comparable processed change without that basis. SPC3's filename does not establish its collection or version. Preserve observation, processing and derivative lineage rather than assigning V2 from recency language alone.",
    "failureModes": [
      "Inferring processing equivalence from the same observation alias and unit.",
      "Using a newer-image filename as the missing collection-version source map."
    ],
    "fields": [
      [
        "Collection, version and observation",
        "Defines the source resource."
      ],
      [
        "Processing label and basis",
        "Makes comparison conditions explicit."
      ],
      [
        "Derived-image source map",
        "Links the output to its actual inputs."
      ]
    ],
    "holdout": "Supply IMG2's V1 lineage despite its newer filename. Require the model to follow the source map while leaving V2's missing processing label unresolved.",
    "boundary": "Use invented measurements and derivatives or separately approved open releases. Exclude controlled technology, payload records, access details and sensitive targets."
  }
}