Handling Conflicting Values Within a Single Session

Determine how the Temporal State Tracking Memory version-status rule should handle conflicting values for the same subject–relation pair when those values occur within a single source session.

Background

Temporal State Tracking Memory assigns historical status by comparing source-session indices within a subject–relation version group. All records at the maximum source index are treated as current, while records from earlier sessions are marked historical. This ordering rule assumes single-valued updates arriving in session order.

The paper explicitly leaves unresolved the case in which conflicting values for the same subject–relation pair occur within one session. Resolving this case would require a rule beyond the current source-index comparison, such as a mechanism for distinguishing or reconciling multiple same-session values.