Repository navigation
Recover control activation from original durable publication - #2
Merged
GTrunSec merged 1 commit intoOct 30, 2026
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.
Go bootstrap previously submitted the original authority publication on every restart, including after Rust had committed it and the response was lost. Bootstrap now inspects that exact durable decision first. A matching committed outcome activates the frozen bundle without a publication write; rejection, unavailable inspection and invalid binding fail closed. Authoritative NotFound allows one unchanged CAS submission, with no retry or parent rebasing after a lost reply.
The real mTLS relay drops every successful publication response across recovery. Tests restart Go and Rust, verify one publication submission, preserve the consumed node's canonical receipt, and reject an unused node after later revocation. Rust still owns fresh Policy/fence checks at execution; a historical receipt cannot authorize a send.
Validation:
This PR is stacked on #1 and contains only the mainline recovery changes. No dependency pins change. Remote GitHub CI is not an acceptance blocker under the requested private-project workflow.