{
  "title": "Farm management acreage revision data for AI",
  "source_page": "https://fiund.com/industries/farm-management-acreage-revision-data",
  "authorship": "Original fictional Fiund editorial exercise. No actual operating records or third-party source assets are included.",
  "example": {
    "title": "A boundary update and a crop-label correction change different fields",
    "context": "Two abstract parcels have original revision cards and arbitrary area units. There are no geographic coordinates, farm-program identifiers or actual filings.",
    "records": [
      [
        "AR1",
        "Initial cards",
        "Parcel A boundary v1 area 10 units, crop C. Parcel B boundary v1 area 8 units, crop D."
      ],
      [
        "AR2",
        "Approved day-5 changes",
        "A boundary v2 area 11 units, crop C unchanged. B crop corrected to E, geometry v1 and area 8 unchanged. Both effective day 5."
      ],
      [
        "AR3",
        "Draft day-6 note",
        "Proposes A crop F and area 12 but has no approval. Requested snapshot day 7."
      ]
    ],
    "question": "Which area, crop and geometry combinations are supported for A and B on day 7?",
    "answer": "AR2 supplies A's approved boundary v2 with area 11 and unchanged crop C for day 7. It supplies B's corrected crop E while retaining boundary v1 and area eight. AR3 is an unapproved proposal and does not replace those fields. Keep each amendment's scope intact rather than pairing A's new geometry with its old area, or treating B's crop correction as a geometry change. The exercise files no acreage report.",
    "failureModes": [
      "Combining a revised boundary with a superseded area value.",
      "Applying unapproved changes or changing geometry when only a crop label was corrected."
    ],
    "fields": [
      [
        "Parcel and geometry version",
        "Defines the spatial record."
      ],
      [
        "Area unit and crop label",
        "Separates independent attributes."
      ],
      [
        "Effective date, approval and changed fields",
        "Limits the revision's scope."
      ]
    ],
    "holdout": "Ask for day 4. Require the original combinations from AR1, before either approved change takes effect.",
    "boundary": "Use abstract shapes and exercise-specific approvals. Exclude real boundaries, ownership, lender details and private field histories."
  }
}