Reconcile document histories and conflicting versions

Inventory the record and define precedence

Record document identity, effective date, author, version and supersession links. Distinguish when an event occurred from when a note about it was written. Identify missing intervals and inaccessible records before generating a chronology.

Have the record owner define precedence: which source controls when two records disagree, and when a newer record actually supersedes an older one. Recency alone is not an authority rule.

Choose context and retrieval deliberately

Check the selected lane’s current context limit. An advertised context window does not prove that every relevant passage will be used correctly. Use retrieval or bounded partitions when the record cannot be reviewed together.

Keep a manifest of the documents actually included. Ask Bee to preserve citations while separating events, claims, decisions and unresolved discrepancies. Review documents omitted by a retrieval step so absence from the answer is not mistaken for absence from the record.

Classify differences instead of erasing them

Distinguish a direct contradiction, a later correction, a superseded instruction, a change in scope and a missing source. For each unresolved item, preserve both passages and state which authority decision is still needed.

Verify and maintain the chronology

Trace material events and conclusions back to the originals. Retain document coverage, unsupported claims, unresolved gaps and reviewer decisions. When new records arrive, reconcile them against the retained history rather than replacing it with an unreviewed summary.