Repository navigation
feat(reporting): support definition-driven official finality - #1925
Open
rachitm022 wants to merge 39 commits into
Open
rachitm022 wants to merge 39 commits into
rachitm022 wants to merge 39 commits into
Conversation
rachitm022
requested review from
KonstantinMirin and
bokelley
as code owners
November 18, 2026 18:02
This branch has not been deployed
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.
Why
Reliable Reporting definitions can select one of three official-finality policies, but the Python SDK previously synthesized official closes from source timing metadata. That made policy ownership ambiguous and allowed scheduled rereads to create revisions even when content had not changed.
This implements AI-22659.
What changed
source_final,contractual_cutoff, orstabilized. The SDK never selects or defaults a policy.source_final, and verified full-period snapshots for cutoff/stabilized promotion.Verification
make lint typecheck-all, configured Pyright, mypy, Black, generated-code, schema, packaging, installed-wheel, and Python↔TypeScript storage interoperability checks passed.Known custom-store limitations
Native memory and PostgreSQL stores retain the required evidence and are covered by restart, concurrency, migration, and replay tests.