{
  "title": "Crushed granite stockpile transfer records for AI",
  "source_page": "https://fiund.com/industries/granite-stockpile-transfer-data",
  "authorship": "Original fictional Fiund editorial exercise. No actual operating records or third-party source assets are included.",
  "example": {
    "title": "Distinguish a pile rename from a material movement",
    "context": "Two abstract inventory piles appear on a fictional dispatch board. Planned movements, confirmed transfers and alias updates are separate event types.",
    "records": [
      [
        "GT1",
        "Practice transfer proposal",
        "Plan P-4 would move 6 tokens from pile North to pile South."
      ],
      [
        "GT2",
        "Confirmed fictional receipt",
        "Transfer T-8 received 4 tokens from North into South; no P-4 completion is recorded."
      ],
      [
        "GT3",
        "Alias register",
        "South is renamed Amber at 14:00. A 14:20 summary still uses South; no further transfer is listed."
      ]
    ],
    "question": "How many tokens have a confirmed North-to-South transfer, and does the later Amber alias establish another movement?",
    "answer": "GT2 supports one completed transfer of 4 tokens from North to South. GT1 remains a proposal for 6 tokens, so it cannot be added to completed movement. GT3 changes South's alias to Amber without recording a physical transfer. The stale 14:20 name may need reconciliation, but it does not establish another movement or a new inventory quantity.",
    "failureModes": [
      "Counting the proposed 6 tokens alongside the received 4 as 10 completed tokens.",
      "Recording South-to-Amber as a physical transfer rather than an alias change."
    ],
    "fields": [
      [
        "Event type",
        "Distinguishes rename, proposal and verified transfer."
      ],
      [
        "Stable pile identifier",
        "Survives changes in the display alias."
      ],
      [
        "Proposed and received quantities",
        "Prevents planned amounts from becoming actual inventory."
      ],
      [
        "Alias effective time",
        "Explains why later records can contain an older name."
      ]
    ],
    "holdout": "Add a partial cancellation of P-4 and a separately confirmed transfer to a third pile. Require the answer to preserve each transaction rather than netting unrelated movements under a reused alias.",
    "boundary": "Represent quantities with tokens on paper. Exclude actual stockpile volumes, yards, machinery, customers, access details and proprietary dispatch exports."
  }
}