Repository navigation
Journal exact protocol epoch publication - #165
Merged
Merged
Conversation
Tim55667757
commented
Nov 7, 2026
Tim55667757
left a comment
Contributor
Author
There was a problem hiding this comment.
Independent AI static review completed for exact head 5b26c43 against 9e5a715. The separate reviewer found no remaining actionable findings after fixes for durable post-unlink admission, complete immutable snapshot pinning through all later barriers and final context exit, exact expected-old mutable authority, and protective-journal restoration after late snapshot drift. EN/RU/ZH semantics and all four source/translation provenance pairs agree. Static review did not execute tests. Proceeding remains conditional on all three exact-head CI gates passing. This COMMENT records independent AI review, not a human APPROVE.
Tim55667757
marked this pull request as ready for review
November 7, 2026 09:53
Contributor
Author
|
Reviewed |
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.
A completed guest transition must become one durable local protocol epoch without losing its closed peer history when the controller stops. Add a private journaled publisher: retain the full expected public candidate before requesting completion; require a separately supplied exact authenticated response before recording observed, publishing the next empty peer namespace/head, and retiring known terminal ingress metadata and the publication journal last.
Recovery preserves source files and prior peer segments, finishes only ordered exact immutable file prefixes, and refuses lost authority, unknown dispatch, stale pointers, gaps, replacement inodes, membership ABA and reappearing metadata. Complete immutable descriptors remain pinned across segment/head/cleanup, final traversal and context exit. Late drift preserves/restores the same observed protection; mutating project admission synchronizes final namespace absence before any subsequent peer/guest write. Read-only coordination does not repair or synchronize.
Continues #128; does not close it. This backend performs no real cloud/guest attestation or dispatch. Protocol RPC, a concrete non-target-service observer, full coordinator and public CLI remain integration work. No production, desktop VPN, WSL, credentials, keys or local network changes.
Validation on exact head 5b26c43:
Added 64 deterministic cases covering codec/consent, publication interruption, ordered/partial prefixes, repeated native epochs, private-source loss, expected-old authority, replacement/ABA, lifetime pins and failed directory barriers. All new POSIX cases ran in Linux CI. ADR/engineering and reviewed RU/ZH catalogs updated. Independent exact-head AI static review found no remaining actionable findings; see the review COMMENT.