Skip to content

Floor: reach differential reuses the prepared required_floor authority (no second resolve) - #13629

Closed
gunbai-bot[bot] wants to merge 1 commit into
mainfrom
session/silent-eagle-796
Closed

gunbai-bot[bot] wants to merge 1 commit into
mainfrom
session/silent-eagle-796

Conversation

@gunbai-bot

@gunbai-bot gunbai-bot Bot commented Oct 9, 2026

Copy link
Copy Markdown
Contributor

Chain (DESIGN §6b)

resolve/prepare → hermetic frame (from `prepared`, owns `v2.workflow.required_floor`) → claim fold → reach differential. The differential's `reach differential authority resolve` called `resolve_entry_graph_shared` on `src/v2/workflow/required_floor.dag`: a second graph resolution of a module the floor already holds (it is a `REQUIRED_FLOOR_RUNTIME_AUTHORITY_MODULES` seed, and the floor's own `hermetic` frame is built from it). On the merge queue that stacked a resolve on a ~25.8 GB working set and tripped MemoryStallRefusedPageThrash.

Change

  • `verdict_frame` is now `floor_authority_frame(&prepared, "v2.workflow.required_floor")` — carried, not re-derived. Same Hermetic mode, same module scope.
  • Adds `reach-differential-begin` / `reach-differential-end` seams so `[floor-heap]` brackets the phase.
  • Not done on purpose: dropping `prepared` earlier — the publication phase reads it (`floor_authority_frame` for the ledger wire), so that would just move a second resolve there. No limits changed, guard untouched, no cache added.

Evidence owed (NOT yet collected)

Before/after `[floor-heap] in_use` at the reach-differential seams, peak, and unchanged verdicts need a merge_group-shaped run (PR runs defer the phase). Will report from the merge-queue/remote dispatch; the `[floor-heap] seam=reach-differential-begin/end` lines are the readout.

🤖 Generated with Claude Code

…y instead of re-resolving it

The differential's 'authority resolve' rebuilt the entry graph of v2.workflow.required_floor, a module the prepared subject already holds (runtime authority seed; the floor's own hermetic frame is built from it). Build the verdict frame from the prepared subject (DESIGN §2: carry the first value). Adds reach-differential-begin/end seams so [floor-heap] brackets the phase.

Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
@gunbai-bot
gunbai-bot Bot marked this pull request as draft October 9, 2026 16:29
@gunbai-bot

gunbai-bot Bot commented Oct 9, 2026

Copy link
Copy Markdown
Contributor Author

Parked as a draft: the operator has paused v1/CI work in favour of v2-native. Status: it compiles (cargo check). It is NOT exercised: the reach differential only runs in merge_group, so there's no before/after memory or unchanged-verdict evidence. Don't land it without that run. — sent from swift-bat-828

@briansrls
briansrls marked this pull request as ready for review October 9, 2026 18:06
@chatgpt-codex-connector

chatgpt-codex-connector Bot commented Oct 9, 2026 •

Copy link
Copy Markdown

Codex Review Summary

This comment shows the latest Codex review activity on this pull request.

Review Status Commit Review trigger
📝 Code Review ✅ Completed 2026-10-09T18:14:56.240321Z 93b05cd Draft marked ready
ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review" or "@codex security review".

Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings.

@gunbai-bot

gunbai-bot Bot commented Oct 9, 2026

Copy link
Copy Markdown
Contributor Author

Closed without folding in the v1 closeout bankruptcy (#13641). It repairs the retiring v1 floor's reach differential; the floor is removed by the CI bankruptcy. The branch is kept for archaeology; no follow-up obligation is created. — sent from neat-wolf-604

@gunbai-bot gunbai-bot Bot closed this Oct 9, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants