Maintain a registry of active research snapshots — what should the operator record?
Operators often duplicate work because nobody knows which snapshot is current. A small registry can point to the approved table and its lineage without centralizing all evidence in a broadly visible spreadsheet. Treat this index as navigation metadata and keep sensitive record details within their authorized location.
Keep active, superseded and access-blocked snapshot pointers in one operational index.
Start with snapshot_key, purpose, owner, state and internal_manifest_ref; avoid putting names or excerpts into a general project index. A registry entry should point to a manifest, not duplicate every source URL; otherwise the navigation layer becomes another uncontrolled identifying evidence store.
Assign an owner to review registry pointers and permitted retention. Remove obsolete identifying metadata through the team's existing approved process. During review, check that owner_role still exists and that approved pointers resolve to artifacts whose actual manifest revisions match the registry's recorded values.Choose registry fields
Start with snapshot_key, purpose, owner, state and internal_manifest_ref; avoid putting names or excerpts into a general project index. A registry entry should point to a manifest, not duplicate every source URL; otherwise the navigation layer becomes another uncontrolled identifying evidence store.
Define state transitions
Separate draft, approved, superseded and access-blocked states. Superseded means another revision is preferred, not that its sources became false. Use superseded_by only when an actual successor is approved; access-blocked has no implied replacement and should not redirect readers to a different dataset.
Test a missing pointer
Open every approved manifest reference using the receiving role. Mark inaccessible entries blocked rather than copying evidence into the registry. A missing internal file is a broken pointer; a denied file is an access issue. Preserve that distinction when assigning the repair task.
Resolve competing approvals
When two snapshots claim current status for one purpose, compare their scope and obtain an accountable choice instead of selecting by filename. Compare purpose and window first: a table approved for a November review does not supersede an October audit merely because its timestamp is newer.
Schedule bounded review
Assign an owner to review registry pointers and permitted retention. Remove obsolete identifying metadata through the team's existing approved process. During review, check that owner_role still exists and that approved pointers resolve to artifacts whose actual manifest revisions match the registry's recorded values.
Keep the boundaries clear.
- Keep active, superseded and access-blocked snapshot pointers in one operational index.
- Operational record: Choose registry fields. Context badges do not certify access.
Start with a read-only check: ask your agent to report actual source coverage before collecting records or exporting an audience.
Primary references
Documentation reviewed 2026-11-15. Product capabilities, client availability and plans can change. Third-party marks identify their products, not an affiliation.