{
  "title": "Directory update and suppression records for AI testing",
  "source_page": "https://fiund.com/industries/directory-suppression-provenance-data",
  "authorship": "Original fictional Fiund editorial exercise. No actual operating records or third-party source assets are included.",
  "example": {
    "title": "An older feed replay must retain the later exclusion decision",
    "context": "Wholly fictional organization entries test snapshot and suppression logic. No person, contact detail, consent record or actual directory is used.",
    "records": [
      [
        "DU1",
        "Snapshot day 1",
        "Organizations ORG-A and ORG-AB included; stable IDs are distinct."
      ],
      [
        "DU2",
        "Reviewed exercise exclusion",
        "ORG-A excluded effective day 5. No exclusion names ORG-AB."
      ],
      [
        "DU3",
        "Replay day 8",
        "Day-1 feed replay contains both entries. No later reversal or reapproval for ORG-A supplied."
      ]
    ],
    "question": "Which entries remain eligible under the fictional rules on day 8, and does reappearance in the replay reverse the exclusion?",
    "answer": "DU2 excludes ORG-A from day 5 onward, and DU3 supplies no authorized reversal. Replaying the older inclusion snapshot does not override that later decision. ORG-AB has a different stable identity and no recorded exclusion, so its status remains included under DU1. Report the source and effective time for each status rather than interpreting name similarity or feed reappearance as a new eligibility decision.",
    "failureModes": [
      "Reinstating an excluded row from an old snapshot without carrying the decision history.",
      "Suppressing ORG-AB because its name starts with ORG-A."
    ],
    "fields": [
      [
        "Stable organization identity",
        "Disambiguates similar names."
      ],
      [
        "Snapshot source time versus replay time",
        "Distinguishes old content from a new decision."
      ],
      [
        "Exclusion effective date and reversal state",
        "Preserves the authoritative exercise status."
      ]
    ],
    "holdout": "Add a verified ORG-A reapproval effective day 10. Ask about day 8 and day 11 separately rather than applying the latest status to all history.",
    "boundary": "Use fabricated organization aliases only. Exclude actual contacts, private directories, personal names, residential data and real consent records."
  }
}