Verify contributed source facts before graph assembly - #394
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.
Publishers previously hydrated contributor receipts and then discarded those inputs during a forced source rebuild. Publication now uses original contributed facts after comparing their complete bounded representation and action context with independently parsed committed source. This is the
publisher-recomputepolicy: it proves payload use without treating self-attestation as authenticated worker identity or claiming saved parsing work.A publication-scoped source ledger checks every raw assembly input before selected originals flow directly into postprocessing and attribution. Verification builds disable sharing traffic, overlays, automatic retries, resumed builds and materialized-shard reuse. Worker payloads never enter the generic parser cache. Missing or mismatched inputs abort publication.
Export binds to the exact physical snapshot whose assembly was checked. Source, profile, predecessor and current quarantine are rechecked under the coordinator lock through canonical pointer promotion. Active language-pack changes still compact into a new checkpoint. Local diagnostics report bounded, distinct integrity and source-use evidence.
Validation: 17 focused tests, including bounded ordering/idempotence/non-mutation properties, paired independent whole-graph controls, validly hashed forged payload rejection and clean retry, quarantine during publication, a zero-sharing-HTTP sentinel, and ABI-transition compaction. Lint, typecheck and the full development review are clear. The exact-HEAD global CLI smoke also passed: three original receipt payloads were consumed, the no-contribution control consumed zero, whole logical graphs matched, and ordinary full indexing still reparsed. Full CI remains the merge gate.