Retire a local table contract without breaking historical references — what should the operator record?
A local schema or identifier contract may become unsuitable for current work. Retire it deliberately rather than silently changing the meaning of its existing columns. Current consumers need a migration path, while historical artifacts need enough permitted metadata to remain interpretable without keeping source evidence longer than policy allows or pretending unsupported migrations can be completed safely.
Move current consumers to a checked mapping while preserving permitted interpretation metadata for older artifacts.
Inventory manifest references, adapters and exports that still name the old contract revision within known ownership. Record unknown references as unresolved rather than claiming no dependencies exist simply because a text search or one team's file index did not reveal any additional active user of the old representation.
Record deprecated_for_new_use separately from historical-unreadable and migration-complete. Explain remaining consumers and owners, avoiding a blanket claim that every artifact was converted or can still be reproduced when input availability, current authorization or semantic incompatibility prevents that conclusion for some known cases.Identify affected consumers
Inventory manifest references, adapters and exports that still name the old contract revision within known ownership. Record unknown references as unresolved rather than claiming no dependencies exist simply because a text search or one team's file index did not reveal any additional active user of the old representation.
Define the replacement boundary
State which old meanings map faithfully to the new contract and which require manual review or remain unsupported. A semantic change is not a harmless column rename; preserve differences in identity grain, null handling and source context rather than forcing old values into newly mandatory fields with fabricated defaults.
Test migration and refusal
Use labeled fixtures for a valid mapping and an incompatible historical input. The adapter should produce a checked new candidate for the former and a clear unsupported state for the latter, demonstrating that deprecation does not simply widen types until every old file appears compatible with the latest workflow.
Update current pointers deliberately
Move approved consumers only after validating their actual candidate artifacts and intended access boundary. Retain a permitted contract description for older references, but avoid copying expired or withheld evidence into migration logs solely to make the historical representation available to people who cannot currently inspect its content.
Publish retirement status
Record deprecated_for_new_use separately from historical-unreadable and migration-complete. Explain remaining consumers and owners, avoiding a blanket claim that every artifact was converted or can still be reproduced when input availability, current authorization or semantic incompatibility prevents that conclusion for some known cases.
Keep the boundaries clear.
- Move current consumers to a checked mapping while preserving permitted interpretation metadata for older artifacts.
- Operational record: Identify affected consumers. 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.