INDUSTRY FIELD GUIDE
Political organization disclosure and source version records for AI
A draft message and a released version may carry different disclaimer text.
NAICS 813940 · Political Organizations
A draft message and a released version may carry different disclaimer text. The FEC publishes guidance about advertising and disclaimers for federal political communications. A fictional example can evaluate source attribution and version control without collecting voter data or generating campaign messaging. FEC advertising and disclaimers guidance
Create two inert notices for an invented committee and a dummy publication log. One notice carries an earlier footer. Give the other the revision approved for the fictional release. Ask the model to extract the disclaimer actually shown and identify the matching approval record. Leave legal sufficiency outside the scoring rubric.
Use original text and fictional entities. Exclude donor, voter, audience and campaign performance data. Keep the exercise limited to reviewing supplied evidence.
Describe a fictional disclosure records sample
Original Fiund exercise
Extract the footer that was actually released, without judging legal sufficiency
Two inert notices for an invented group use neutral administrative text. The exercise is document attribution only, with no campaign message, voter targeting or real political entity.
| Record | Source | What it records |
|---|---|---|
| PD1 | Practice notice V1 | Footer text: Issued by Group Q. Earlier draft; no current release approval. |
| PD2 | Approved notice V2 | Footer text: Issued by Group Q, office desk. Approval A2 explicitly names V2. |
| PD3 | Dummy publication log | Release L1 maps to V2; cached thumbnail still shows V1 footer. No later release or legal review supplied. |
Question for the model
Which exact footer is supported for release L1, and does the cached thumbnail establish a different approved version?
Show the reference answer and checks
PD3 maps L1 to V2, and PD2 supplies both its footer text and matching A2 approval. The supported released footer is Issued by Group Q, office desk. PD1's shorter footer remains an earlier draft, while the cached thumbnail reflects that stale version without changing the release map. Report the observed version conflict and source chain, without assessing legal adequacy or creating new persuasive messaging.
- Selecting a cached thumbnail over the explicit release-to-version record.
- Treating a matching approval as a legal-sufficiency judgment absent any such review.
Fields to preserve
- Notice and release version
- Identifies the published artifact.
- Exact footer text
- Makes extraction checkable.
- Approval reference and cache source
- Separates release authority from a stale preview.
Test another case
Publish V1 under a different release ID on another date. Require release-specific extraction rather than declaring V2 the footer for every historical record.
Use fictional entities and original neutral text. Exclude donors, voters, audiences, campaign performance and actual communications.
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.