feat(evidence): bind node outcome provenance to target origin - #80
Draft
seonghobae wants to merge 4 commits into
Draft
feat(evidence): bind node outcome provenance to target origin#80seonghobae wants to merge 4 commits into
seonghobae wants to merge 4 commits into
Conversation
|
Important Review skippedDraft detected. Please check the settings in the CodeRabbit UI or the ⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Plus Run ID: You can disable this status message by setting the Use the checkbox below for a quick retry:
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
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.
Partial implementation of #28, stacked on PR #64.
Buyer/correctness gap
PR #64 correctly refuses to treat command acknowledgement or pre-dispatch provenance as action success, but its constructor previously accepted independently verified
NodeStateChangedprovenance whose source URL belonged to a different origin than the governed action target. That could let an unrelated document prove the wrong page's node post-condition.Dependency
This Draft is stacked on unchanged exact PR #64 head
2c45411ed9aa0eecca2d06c85659db9f4bb85e4dand remains Draft while #64 is active.Test-first implementation
Exact test-only head
367554a1470f173aac978d0549aa0468a7427cd0established the missing origin-binding contract. Exact current head55b1421e25c5b68ca5f3b05fab37db8f4f1e22benow retains canonical source origin inProvenanceRecordand makesVerifiedActionOutcomeEvidence::newreturn the stablePostConditionOriginMismatcherror whenNodeStateChangedprovenance does not match the canonical governed target origin.The restriction is deliberately specific to
NodeStateChanged;UrlChanged,DialogStateChanged, andNetworkMutationObservedare not forced to use the action target origin because legitimate observed outcomes can involve another origin. Canonical-equivalent URLs such ashttps://APP.EXAMPLE:443/...remain accepted through the existingOriginnormalization.Exact-head verification
CI run
31485218503completed successfully on exact head55b1421e25c5b68ca5f3b05fab37db8f4f1e22be. The branch is directly ahead of unchanged live base2c45411ed9aa0eecca2d06c85659db9f4bb85e4dwith no base drift, and no formal reviews or inline review threads are currently returned for this head.Truth boundary
This is a credential-safe evidence-construction invariant only. It does not prove browser dispatch, document/node identity, frame identity, clock provenance, a real post-condition observer, redirect authority, network attribution, or complete the Chromium vertical slice. It remains Draft because prerequisite #64 is still active.