Which fields preserve the difference between policy effect and policy discovery?

A generated release can represent two different clocks. `effective_from` and `effective_to` describe when a policy governs work. `recorded_at` and `withdrawn_at` describe when a particular policy record is present in the operational information system. These clocks can differ when publication arrives late or a recorded notice is corrected.

A policy table could include `policy_id`, `version_id`, both time pairs and `supersedes_version_id`. Decision records could link through `applied_version_id` and include `decision_at`. The schema should specify timestamp zones and whether interval boundaries are inclusive or exclusive.

Parquet can preserve typed timestamps for analytical use, while a JSONL export needs an explicit timestamp convention. A reseller should preserve both clocks when converting between formats instead of replacing them with one generic update date.

An environment query such as `get_policy(as_of, known_at)` could return the rule applicable at one moment using only information recorded by another. This supports tasks where agents must distinguish an operational error from a decision made before the relevant notice became accessible.