{
  "title": "Planting pass data for evaluating AI field maps",
  "source_page": "https://fiund.com/industries/field-planting-pass-data",
  "authorship": "Original fictional Fiund editorial exercise. No actual operating records or third-party source assets are included.",
  "example": {
    "title": "A machine path needs tool-state evidence before it counts as planted distance",
    "context": "Abstract parallel paths and original state annotations form an offline contractor-data exercise. There are no real coordinates, seed rates, machine settings or operating instructions.",
    "records": [
      [
        "PPF1",
        "Pass A",
        "Path length 100 practice meters; planting-state signal active throughout; matching fictional operator note confirms the interval."
      ],
      [
        "PPF2",
        "Pass B",
        "Path length 100 meters; tool raised throughout; operator note says repositioning."
      ],
      [
        "PPF3",
        "Pass C",
        "Path length 100 meters overlaps A for its first 20. Active-state transition timestamp uncertain over the first 30 meters; final 70 confirmed active. No width or area denominator supplied."
      ]
    ],
    "question": "Which distance is confirmed active, which path is repositioning, and what cannot be counted as verified unique planted area?",
    "answer": "PPF1 supports 100 practice meters of active-state travel on A. PPF2 is 100 meters of repositioning with the tool raised. PPF3 confirms only its final 70 meters active and leaves the first 30 uncertain, including overlap with A. These records do not establish unique planted area because width and adequate overlap treatment are absent. Report supported distance by pass rather than credit every mapped line as planting or sum overlap into area.",
    "failureModes": [
      "Treating all machine travel as active planting.",
      "Summing overlapping paths into unique area without tool-state timing and width evidence."
    ],
    "fields": [
      [
        "Pass and path segment",
        "Identifies spatial intervals."
      ],
      [
        "Tool state and transition uncertainty",
        "Separates activity from travel."
      ],
      [
        "Overlap, width and operator source",
        "Defines what further evidence area calculation needs."
      ]
    ],
    "holdout": "Provide C's exact activation at meter 30 and an explicit width while leaving overlap geometry incomplete. Require the remaining area gap to stay visible.",
    "boundary": "Use simulated paths. Exclude client maps, variety assignments and equipment IDs; verify client and platform export authority before real collection."
  }
}