Preserve semantic time in source mapping - #170
Merged
Merged
Conversation
eamirian
force-pushed
the
codex/v1-bitemporal-source-mapping
branch
from
August 14, 2026 01:33
52e8d24 to
9014e27
Compare
eamirian
marked this pull request as ready for review
August 14, 2026 01:41
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What changed
Observationtime validation so semanticas_ofmay precede, but never follow, ingestion availabilityevent_effective_at, thensource_published_at, thenobserved_atWhy
Recorded materials admitted together previously gave every mapped Entity Snapshot the batch ingestion time as
as_of. Baseline and current snapshots therefore appeared simultaneous even when the source carried distinct effective times, and the strict numeric/categorical detectors correctly rejected them. This correction preserves the bitemporal distinction instead of weakening detector ordering or fabricating timestamps.Historical source state may legitimately predate activation. The detector and routing follow-up therefore rejects pre-activation projection/detection, not historical
as_of; exact activation revision binding and current processing-time gates remain unchanged.Identity and compatibility impact
The canonical source snapshot and its ingestion availability contract are unchanged. Mapped Observation and Entity Snapshot identities intentionally change whenever semantic state time differs from ingestion because
as_ofis content-addressed material. PREPARED and LIVE mapping use the same corrected interpreter; LIVE ingress and projection coverage remains green. There is no fallback to legacy mapped identities.Verification
test_forget_by_hash_erases_all_duplicates, which passed immediately when rerun in isolationNo authority, UI, domain-pack, MCP, provider, or release surface changes are included.