Archive metadata before 2019 is unreliable — date fields were entered by hand
Roughly a fifth of pre-2019 issues in the 1,240-issue archive carry a publication date that contradicts the content.
The record
The archive was migrated from a system where the date was a free-text field, and a sample of 200 issues found about one in five disagreeing with internal references in the copy itself. Tag pre-2019 issues from content rather than metadata, and flag rather than silently correct — the original value is evidence about the migration even when it is wrong.
Applies to
- Company
- Media Company
- Department
- Production
- Agent
- No single agent
Context bound to one project, from kickoff to close. Readable by: Everyone on the project.
Provenance
Archive tagging sample, 200 issues
Job run · unattended
logs/media/job_3388.json
- Recorded by
- Media Director
- First learned
- 10 Jul 2026
- Last updated
- 22 Jul 2026
Index state
Not embedded- Index
- project-active
- Vector id
- —
- Model
- —
- Indexed at
- —
- Rank weight
- 1.00
No vector store is connected, so this record has no embedding. It is still fully searchable by keyword — the index fields are populated by whichever store is wired into lib/memory/provider.ts.