Define what a frozen evidence table actually freezes — what should the operator record?
Calling a table frozen can imply more than the team intends. Usually the useful promise is that a chosen row set and ordering will not be silently replaced. Source content, access decisions and retention obligations still require separate handling when the table is opened later.
Separate fixed row membership from mutable source availability and later permission checks.
List frozen fields such as row_key, selection_rank and selected_at; identify source availability as a separate current-state field rather than frozen truth. For example, freeze the local row keys and their ranks while allowing current_visibility to change from visible to withheld after a supported access decision.
Allow a new visibility annotation or approved correction revision, but require a distinct snapshot for new membership rather than quietly refilling gaps. A different set of members needs a new selection revision even if its total size equals the old one and its displayed title stays unchanged.Write the freeze contract
List frozen fields such as row_key, selection_rank and selected_at; identify source availability as a separate current-state field rather than frozen truth. For example, freeze the local row keys and their ranks while allowing current_visibility to change from visible to withheld after a supported access decision.
Capture the chosen order
Persist selection_rank explicitly so sorting a display cannot silently change the approved membership sequence or who appears first. Test two rows with the same display title but different selection_rank values; reopening the file should not swap their historical positions unpredictably.
Probe an unavailable row
Use a local test row whose source cannot be read and ensure the table shows unavailable instead of substituting a different record. The test should inspect downloads as well as the screen, ensuring a withheld display does not leave the original identity exposed in exported fields.
Compare reopening behavior
Check that current access failures affect the visibility state while the historical selection slot remains explainable without exposing withdrawn identifying details. An exception entry can say slot withheld without carrying the old handle or URL into a broadly visible change log when that disclosure is prohibited.
Document permitted changes
Allow a new visibility annotation or approved correction revision, but require a distinct snapshot for new membership rather than quietly refilling gaps. A different set of members needs a new selection revision even if its total size equals the old one and its displayed title stays unchanged.
Keep the boundaries clear.
- Separate fixed row membership from mutable source availability and later permission checks.
- Operational record: Write the freeze contract. 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.