Which fields make generated overdue records useful for temporal reasoning?

A generated package can separate obligations, account arrangements, contact events and policy versions into linked tables. Stable identifiers such as `obligation_id`, `arrangement_id` and `policy_version_id` allow the same relationships to survive export into JSONL or Parquet.

For temporal reasoning, include both `effective_at` and `recorded_at` where they have different meanings. An approved deadline extension can become effective before the case system records it. A task must specify whether the agent is judging the obligation using currently known facts or reconstructing what was knowable at an earlier decision point.

MirrorFirm could generate snapshots with an explicit `as_of` value and versioned changes between snapshots. The schema can also define timestamp offsets, null semantics and whether an end date is inclusive. Those details affect whether a record qualifies for follow-up at a boundary.

An integration check should confirm that each relationship resolves within the intended snapshot and that future versions are not exposed accidentally. This gives developers a controlled way to train historical reasoning without allowing later information to answer an earlier task.