INDUSTRY FIELD GUIDE
Directory update and suppression records for AI testing
A directory entry can reappear if a later file is merged without the associated suppression record.
NAICS 513140 · Directory and Mailing List Publishers
A directory entry can reappear if a later file is merged without the associated suppression record. FTC materials discuss privacy issues around people search and data-broker services. This benchmark uses entirely fictional organization entries to test whether a model preserves the recorded exclusion. FTC people-search privacy context
Invent organization aliases and two incoming snapshots. Exclude one entry after a documented review, then include it in an older feed replay. Ask which rows are eligible in the exercise and what source supports that status. Add a similarly named organization that was never suppressed. Keep source, status and effective date visible.
Use no real contact lists, private directories, personal names, residential information or consent records. Review contractual and privacy boundaries for any actual source.
Describe a fictional directory workflow
Original Fiund exercise
An older feed replay must retain the later exclusion decision
Wholly fictional organization entries test snapshot and suppression logic. No person, contact detail, consent record or actual directory is used.
| Record | Source | What it 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 for the model
Which entries remain eligible under the fictional rules on day 8, and does reappearance in the replay reverse the exclusion?
Show the reference answer and checks
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.
- Reinstating an excluded row from an old snapshot without carrying the decision history.
- Suppressing ORG-AB because its name starts with ORG-A.
Fields to preserve
- 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.
Test another case
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.
Use fabricated organization aliases only. Exclude actual contacts, private directories, personal names, residential data and real consent records.
Discuss a contribution
Describe the sources you control, the task they could support and what has already been checked. Use the existing-data assessment for an archive or the collection brief for a new recording project. The contributor agreement defines Fiund’s licensing authority and compensation. A guide or fictional exercise does not establish an accepted collection or a sale.