pgw#1653: bind contract census hardcut - #1193
Draft
PaulFidika wants to merge 9 commits into
Draft
Conversation
PaulFidika
force-pushed
the
1653-bind-contract-census
branch
from
August 21, 2026 23:50
07b2cc1 to
1d648a9
Compare
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.
Companion to tensorhub th#2290 / PR #1598.
Hardcut in progress: derive emits one construction census for every distinct config tree; the worker fetches the exact resolved Bind Contract and replays that census at serve time; mismatch is a typed bind-attributed refusal. The singular primary-only census field is deleted with no fallback.
Path fence: pgw#1648 owns streaming engine/fill/source/staging and checkpoint_juggle. This branch currently touches only release/derive and its targeted tests; any required engine hook will be coordinated before edit.
Draft remains unmergeable until the Tensorhub protocol/storage side and targeted cross-repo red/green evidence are coherent.