Inspect a change

Start from the current field

Retrieve the entity snapshot by ID and identify the field in question. Check the entity type and active schema. The current field is a computed result; it is not a copy of one mutable source document. Field provenance identifies the observation chosen by the applicable merge policy. If there is no field in the snapshot, inspect whether the attempted write became a raw fragment because the field was not declared.

Next list the entity's observations. Compare the candidate values, their recorded times, source kinds, and attribution. A correction contributes another observation. The old observation remains in the normal history path, so you can see both the previous claim and the new one. A source-backed observation may also lead to a source and an interpretation record; a direct structured write can have no separate file to open.

Explain the transition accurately

Avoid describing every disagreement as a later write replacing an earlier one. Policies can use source priority, recency, specificity, or array behavior. State which policy the active schema uses and which observation it selected. A recorded time and an ingestion time also answer different historical questions; do not silently substitute one for the other.

Provenance makes the recorded path inspectable. It does not certify that a source statement was factually true, nor that an AI interpretation would produce identical wording on another run. Sources and provenance explains the evidence boundary. Current snapshots explains the resulting view, while the observation reference holds implementation detail.