net(586 PR 3, redo): the wake budget is spent in guest execution; extensions only on measured starvation; verdict=dispatch stays red - #956
Draft
ryanbreen wants to merge 18 commits into
Conversation
Measure each spent window independently, refuse initial dispatch and wake failures, and preserve terminal classification. Count finite grants on the budget marker and require its fields in the strict scorer. Add production policy ratchets and a host-contention loop. Re-record the strict fixture from the corrected worktree's direct recording boot. Guest acceptance proofs remain outstanding at this commit. Co-authored-by: Ryan Breen <ryan@ryanbreen.com> Co-authored-by: Claude Code <noreply@anthropic.com>
… source Keep field fragments separate from the bracketed profile marker census. Pin the rustfmt-produced PASS arm braces in the tracing-provider ratchet. The two affected structure suites pass after strict preflight exposed them. Co-authored-by: Ryan Breen <ryan@ryanbreen.com> Co-authored-by: Claude Code <noreply@anthropic.com>
Preserve strict 3, service sequence 2+2, beast x86 and final production receipts; re-record both R182 fixtures and verify their replay suites. Record permanent wake suppression and always-extend boot failures, the red production-guard ratchet, and unsuccessful starvation reproduction attempts. The 64-hog retry exposed armed=0 in the UDP oracle; track it as issue 955. Issue 954 tracks the unresolved always-extend control contract. Acceptance and issue 586 closure are not claimed. Co-authored-by: Ryan Breen <ryan@ryanbreen.com> Co-authored-by: Claude Code <noreply@anthropic.com>
…nance Co-authored-by: Ryan Breen <ryan@ryanbreen.com> Co-authored-by: Claude Code <noreply@anthropic.com>
Co-authored-by: Ryan Breen <ryan@ryanbreen.com> Co-authored-by: Claude Code <noreply@anthropic.com>
Co-authored-by: Ryan Breen <ryan@ryanbreen.com> Co-authored-by: Claude Code <noreply@anthropic.com>
ryanbreen
changed the title
Co-authored-by: Ryan Breen <ryan@breen.com> Co-authored-by: Claude Code <noreply@anthropic.com>
Co-authored-by: Ryan Breen <ryan@ryanbreen.com> Co-authored-by: Claude Code <noreply@anthropic.com>
Preserve integration-revision transcripts and scoped process cleanup. Retain issue 586 and its roster line, and defer 954 closure until merge. Co-authored-by: Ryan Breen <ryan@ryanbreen.com> Co-authored-by: Claude Code <noreply@anthropic.com>
Co-authored-by: Ryan Breen <ryan@ryanbreen.com> Co-authored-by: Claude Code <noreply@anthropic.com>
Resolve the captured-serial fixture conflict with a fresh boot of the merged code, retaining both softirq deferral and wake-budget fields. The first recording failed the UDP oracle; retain that failed evidence. Adapt the softirq status ratchet to mutate the complete green fixture, with a green baseline check. No manual kernel changes. Co-authored-by: Ryan Breen <ryan@ryanbreen.com> Co-authored-by: Claude Code <noreply@anthropic.com>
Use the unedited serial from the successful strict gate at f6f7414. Retain the bootstrap captures and the first UDP-oracle failure as evidence. Co-authored-by: Ryan Breen <ryan@ryanbreen.com> Co-authored-by: Claude Code <noreply@anthropic.com>
Preserve the strict boot, two service boots per CPU profile, both kernel builds, production checks, and fixture provenance. Record the max-profile UDP oracle failure and the production EXIT-status defect tracked by 978. Retain the absent genuine starvation receipt and the LAND-slot x86 deferral. Co-authored-by: Ryan Breen <ryan@ryanbreen.com> Co-authored-by: Claude Code <noreply@anthropic.com>
Integrate e664e4b and resolve the serial fixture with a real merged-source capture. No kernel source changed. Co-authored-by: Ryan Breen <ryan@ryanbreen.com> Co-authored-by: Claude Code <noreply@anthropic.com>
Copy the real strict-gate serial at e91d71e verbatim. Keep bootstrap attempts and their input corrections in the round receipts. Co-authored-by: Ryan Breen <ryan@ryanbreen.com> Co-authored-by: Claude Code <noreply@anthropic.com>
Preserve build, structure, strict, service, and production receipts. Record input-preparation failures and retain the starvation non-claim. Co-authored-by: Ryan Breen <ryan@ryanbreen.com> Co-authored-by: Claude Code <noreply@anthropic.com>
Co-authored-by: Ryan Breen <ryan@breen.io> Co-authored-by: Claude Code <noreply@anthropic.com>
Co-authored-by: Ryan Breen <ryan@breen.io> Co-authored-by: Claude Code <noreply@anthropic.com>
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
1 participant
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.
Current status: NOT LANDED. Fresh strict at b5f11b3 exited 1 (0/1), ending by hard timeout. The failure line contains an interleaved SOFTIRQ marker; the next line reports the BSSH publickey oracle missing, duplicated, or failed. Standalone structure and strict preflight passed 70/70. Both wake budgets were verdict=ok with extensions=0, but strict was RED. Per the stop rule, service, x86, production, merge, and issue closure were not performed. Full gate log: docs/planning/green-program/network/serials/586-pr3/landing-20260908/strict.txt; full serial: docs/planning/green-program/network/serials/586-pr3/landing-20260908/strict/serial.txt.
Earlier preparation status: READY for LAND verification at 240e0e8, with strict 1/1, service max 2/2, cortex-a72 2/2, and production green. These are historical preparation results.
The redo spends the wake budget in guest execution and permits bounded extensions only for measured starvation in the window just spent. Initial wake/dispatch failures remain failures, and the strict scorer requires the budget fields and rejects loopback FAIL.
R233 accepts this implementation for LANDING, subject to the requested merged-tip gates. Issue 586 stays OPEN and its battery roster line does NOT retire on this merge. Issue 954 closes on this merge: R232 replaces the impossible green permanent-suppression requirement with the recorded delayed-wake control.
The delayed-wake triad in docs/planning/green-program/network/586-PR3-2026-09-07.md is: measured guard, wake FAIL with 0 extensions; unconditional grants, PASS with 3 extensions and 600 ms; production-guard ratchet, red with exit 101. Permanent suppression remains red under both policies. The mutated PASS is not a genuine starvation receipt.
NOT-CLAIMED: No genuine verdict=starved extensions>0 PASS receipt was obtained.
The extension-deleted starvation red also remains unreproduced. Issue 955 tracks the separate UDP oracle failure; issues 945 and 559 retain the stock-toolchain work. Historical gates, raw serials, the lane-local core patch, both R182 recordings, and limitations are recorded in docs/planning/green-program/network/586-PR3-2026-09-07.md. Earlier blocked-landing history: NOT LANDED at integration revision 8674c93. Structure passed 105/105 and the ARM64 build was warning-free. Strict ARM64 stopped before boot at 65/66 preflight suites: gate_capture_drain_structure timed out at 300 seconds and again on the one authorized 900-second retry (issue 957). Service-sequence boots were not run. Beast initially timed out in context_restore_structure; its one 900-second retry passed 66/66, built warning-free, and booted, but was stopped with exit 143 after the ARM64 failure without a terminal guest verdict. Full logs are in docs/planning/green-program/network/serials/586-pr3/landing/. PR 956 and issues 586 and 954 remain open; the closure-on-merge condition for 954 was not reached.