History and mappings

A packet’s current status tells a colleague where the work stands. Its state history explains how it got there. Each history entry connects a source packet and actor with the earlier and later status, time, source revision, operation key and reason. A reviewer can therefore trace the path from collection to archive without overwriting the decision trail when a later correction is needed.

Source mappings describe how a document source field relates to a target field for a property definition. A mapping has a name, version, source and target types, transform rule and effective date. This is useful when a title record arrives from another system with a different name for the parcel or document reference. A mapping describes the interpretation; the title version and evidence document still hold the actual observed source.

• Transitions. Keep each packet status change tied to its revision, actor and reason.
• Mappings. Review field interpretation against the property definition before using a source value.
• Exceptions. Trace a failed or uncertain operation through its run and steps instead of changing history to hide it.

Agree which person owns each source mapping and how a new version becomes effective. Decide whether older mappings remain available for explaining earlier packets. The team should name the source document system and the policy for correcting a mapping that produced the wrong parcel or title value. An updated rule should be linked to a new packet review when it changes the meaning of evidence already considered.

The organization should also decide who can inspect history and operation receipts. These records can contain sensitive property references. Access to the packet overview may be broad within a team, while access to attachments and external receipts may need a narrower policy.

An auditor asks why a packet was shared after a title document correction. The Records Auditor opens its state history and finds the indexed revision, reviewer decision and later shared transition. They compare the title version’s source reference with the mapping version effective when that source was read. If a mapping change caused the correction, the older rule remains understandable and the new rule can be used for later packets. The operation run and receipt then show which revision was sent. This sequence answers the question from recorded events rather than from recollection.

• Archived Packets — Finished packet records available for later inspection.
• Runs Needing Reconciliation — Operation histories with an unresolved external result.
• Failed Execution Attempts — Attempts whose recorded reason needs investigation.

See archive and history and correction and follow-up.