feat: bind complete raw cohorts to immutable publication - #673
Merged
Merged
Conversation
…ped-rows # Conflicts: # data_plane/src/precompute_engine/maintenance_runtime.rs
…ntenance-complete-population-cohort
…lete-population-cohort
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
1 participant
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
A requested immutable read set does not prove that every raw population was included. Global maintenance reduction needs stronger evidence before reserving an output.
What
Add a store-issued, non-serializable complete raw cohort capability and publication/recovery entry points that consume it.
How
Build the capability from the exact input definition set and every durable population at one common window. Reuse the existing frozen inputs and transaction. Under the same admission and instance guards, recheck finite closure, all source lifetimes, the complete durable/live SID set, and output window before target registration or reservation.
Before this PR
The frozen read-set API could validate the requested inputs but could not attest that no population was omitted.
After this PR
If one source lacks the requested window, or another raw SID appears after proof capture, complete publication rejects without a target record or part. A fresh store can rebuild the proof from durable inputs after restart and recover the already committed output.
Verification
Limits
Installed source/window alignment remains the plan consumer's responsibility. The capability currently requires finite raw closure; it does not provide continuous watermark semantics. Automatic multi-group routing and reduction are not enabled here.
Stacked on #672.