feat: add exact overlay target tracking contract#10
Merged
Conversation
abrichr
marked this pull request as ready for review
July 25, 2026 22:56
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
ControlOverlayFrameV2/ControlOverlayTimelineV2contract while leaving V1 unchanged.Why
The V1 overlay contract intentionally carries control state but no target geometry. Browser and cross-surface viewers need a shared way to render honest target tracking without injecting into the target application, replaying selectors, or inferring motion/timing the runtime did not retain.
The observation HMAC is preferable to a raw frame SHA because raw hashes can link a private observation across evidence boundaries. Immutable sanitized/public media already has an explicit digest boundary, so its exact digest and decoded-frame index are the appropriate binding there.
Consumer impact
V1 behavior and generated V1 schema bytes do not change. Consumers opt into V2 for browser geometry. A V2 renderer must omit target geometry unless its observation HMAC or exact decoded media frame matches; it must not replay a selector, interpolate missing tracking, or trust a producer-authored transform for a future viewer surface.
The conventional
feat:title makes this eligible for the repository's next minor semantic release, but this draft does not authorize merge or publication.Validation
uv run pytest -q— 132 passed