Skip to content

Journal exact protocol epoch publication - #165

Merged
Tim55667757 merged 1 commit into
developfrom
feature/128-epoch-publication
Nov 7, 2026
Merged

Tim55667757 merged 1 commit into
developfrom
feature/128-epoch-publication

Conversation

@Tim55667757

@Tim55667757 Tim55667757 commented Nov 7, 2026 •

Copy link
Copy Markdown
Contributor

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.

@Tim55667757 Tim55667757 added this to the release-2.1 milestone Nov 7, 2026 — with ChatGPT Codex Connector
@Tim55667757 Tim55667757 added the feature New complex feature or request label Nov 7, 2026 — with ChatGPT Codex Connector
@Tim55667757 Tim55667757 self-assigned this Nov 7, 2026

@Tim55667757 Tim55667757 left a comment

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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
Tim55667757 marked this pull request as ready for review November 7, 2026 09:53

Copy link
Copy Markdown
Contributor Author

Reviewed

@Tim55667757
Tim55667757 merged commit 0548e74 into develop Nov 7, 2026
4 checks passed
@Tim55667757
Tim55667757 deleted the feature/128-epoch-publication branch November 7, 2026 09:53
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

feature New complex feature or request

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant