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.
Summary
Connects the accepted-ref data plane to the production-shaped Gitoxide Write/Edit owner.
Primary invariant: one managed Write/Edit derives from one accepted base and can publish only one operation-bound candidate proof.
Owner: Gitoxide managed Write/Edit owner.
Atomic boundary: candidate publication and durable proof adoption.
Failure state: ambiguous execution remains unsettled; no generic T2 fallback is allowed.
Rollback: deterministic no-effect failures settle without advancing the accepted head.
中文说明
本切片把 accepted-ref 数据面接入 Gitoxide Write/Edit owner。一次 managed Write/Edit 只能从一个 accepted base 派生,并且只能发布一个与 operation 绑定的 candidate proof;不确定状态保持 unsettled,禁止回退 generic T2。