Repository navigation
docs: clarify reachable roots and detached-write evidence - #762
Conversation
|
Warning Review limit reachedYou've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository. Next included review available in 42 minutes. View limit detailsLimit details: You’ve used the included review currently available. Review configuration: ⚙️ Run configuration
📒 Files selected for processing (4)
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 |
Codex Review SummaryThis comment shows the latest Codex review activity on this pull request.
ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings. |
|
Code Lawyer activity summary at
Inspected the clean checkout, normal origin fetch, whole diff, canonical documentation, changed symbol callers, and all paginated PR review data. No actionable self-finding remains. The exact committed files match the guarded candidate manifest. Executed in the reused guarded Docker worker: focused detached-create witness, all 11 worldline_state tests, workspace rustfmt check, and docs-lint link checks. Whitespace checks passed. Docs-lint skipped prettier/markdownlint because npx is absent; those local checks remain unrun. The witness is a unit contract test; original benchmark measurements were not reproduced. Current-head hosted checks are green. Independent agy approval is still pending, and the user-requested solution-feedback reconciliation remains a merge prerequisite. No merge is claimed. @codex |
Review Outcome
Checks
|
Adversarial Independent Review: PR #762 (
|
Closes #754.
WorldlineState::state_root()was described as a full-state hash, although the version-1 Merkle law covers only state reachable from the lane root. The API and operation/WAL documentation now state that detached create-if-absent cells can leave this root unchanged. Patch and commit identities retain those writes; duplicate evidence still needs the target-value digest. Hash bytes and runtime behavior are unchanged.A focused witness creates two detached cells, verifies their presence and unchanged root, then holds root, parents, and policy fixed while proving their patch and commit identities differ.
Validation in the reused guarded Docker worker: the focused witness passed; all 11
worldline_state::testspassed; workspace rustfmt check, docs-lint link checks, and whitespace checks passed. Docs-lint skipped prettier/markdownlint because npx is absent; those checks are not claimed. Concrete API text before/after evidence is retained.Canonical owners reviewed:
docs/spec/merkle-commit.md,docs/architecture/application-contract-hosting.md,docs/topics/WAL.md, and the README route. Their reachable-state law stays unchanged. No provider package, footprint, WAL schema, or application-specific behavior changes.