Repository navigation
Retain distinct same-time events with stable identity and honest order semantics - #4
Merged
Merged
Conversation
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.
Real comparable calls can share an exact completion timestamp. Schema 1.1 now accepts optional aligned event_ids under event_index, retaining each original measurement and rejecting duplicate logical identities instead of jittering, aggregating or counting retry deliveries.
Timestamp-only cohorts share frozen references from earlier timestamps, finish reference stages as whole cohorts and break change/Nelson/CUSUM continuity. An explicit trusted_sequence contract requires validated aligned ordinals. Assessments, cases, corrections and MCP drilldowns retain event identity and original timestamp lineage; exact relationships require matching identities. Calendar and legacy unique-timestamp numerical behavior and schema 1.0 are unchanged.
Prepare 0.3.0 with six reproducible fixtures, README progression chapters 23–24, two inspected charts and the exact API/replay limits. Add installed-consumer coverage and a 1,344-event tied-timestamp benchmark. Release staging retries reads after draft creation to tolerate GitHub's observed visibility delay.
Validation: 252 tests pass locally, including Python/schema/CLI/MCP parity, duplicate rejection, trusted/untrusted order, reordering, prefix/as-of/corrections, independent entity scopes and bounded result growth. Wheel/sdist build, archive completeness, Twine metadata, worked examples, documentation export and CapabilityKit checks pass. Hosted CI covers Python 3.11–3.13, clean wheel/sdist consumers and the offline Linux/Python 3.12 Lambda-compatible bundle. No UsageTap changes or deployment.