Repository navigation
Scoped withdrawal and rollout governance — shadow controls, no scientific migration - #4
Conversation
Owner-authorized operational implementation only. Adds loss-only AND/OR support validation, 36 synthetic tests, read-only legacy inventory, an isolated CI workflow, protocol/work order/reconnaissance, and an AGENTS pointer. Existing scientific graph, frozen sources, registers, other branches and repository settings are unchanged. Technical review and live graph migration remain open.
Verified operational delivery — 2026-09-21Exact candidate remains Live Research Home, continuation router and Start Here now point to OP-WITHDRAWAL-20260921-v1.0. Start Here also directs readers to exact current review/target keys and latest events rather than assuming fixed prefix ranges are current. All changed navigation and the review row were read back. Verified delivery receipt: https://drive.google.com/file/d/1rUN4Q4m-cSLsXRtF_i7IzpwsJPRWlXyb/view — 4595 bytes, SHA-256 R17 events |
|
Governance rollout audit started from the owner's 2026-09-21 clarification. The concern is broader than support withdrawal: previously installed rules may have been treated as globally active before consumer migration was demonstrated. Drive control: OP-ROLLOUT-AUDIT-20260921-v1.0, ID Default operational rollout is now PROPOSED -> SHADOW -> PILOT -> REVIEWED -> ACTIVE_SCOPED -> ACTIVE_GENERAL. Immediate containment remains available only for narrow integrity/safety hazards. Historical controls stay available as compatibility evidence until affected consumers are audited. Operational COMPLETE/ABANDONED/HOLD/SUPERSEDED must not become scientific status by vocabulary alone. Initial high-risk review targets: R17's broad supersession wording; OP-RECON's mandatory-all-model wording; OP-PROT-018's automatic arbitration/ABANDONED/HOLD semantics; and this withdrawal pilot's own live guidance versus unreviewed executable code. No broad rollback or scientific status change is implied. Unrelated research continues. Commit |
Complete the already prepared nine-file tree without rewriting the pointer-only predecessor. Adds read-only rollout guards, 46 synthetic/real-Git regression tests, scoped v1.1 correction and evidence references. Existing 36 withdrawal tests retained. Author-side pilot only; no scientific status migration, no merge or settings changes.
|
Research continuation is isolated in draft PR #5, commit2371f660d90963e558a0d08921c634a36b3be016. It turns bounded parameter search into a new exact-scalar, whole-band H3 candidate Z(r)>=(1747/1000)r² under the unchanged 2D fixed-axis SIDE24 law. No edits or merge to this branch, no scientific status migration, and no replacement of the stronger existing fixed-r RN floor. PR5 contains the analytic proof, separate rational scalar arithmetic, formula-level dependency hashes, local cache/cold replay and57 tests. Dedicated CI passed. It is source-exposed author-side research, review OPEN under RV-H3-SOLVER-20260921-01; failed sampling is not proof and the prototype is not a full-Z falsifier. Verified delivery: https://drive.google.com/file/d/1HVMgUIZJp_e9pGfnb0xURxRjlzL9h60d/view . R17 retains the publication/release records and the review request. |
Two repository test failures originate on this branchReporting, not pushing — this is your branch and the second finding is a governance judgment that belongs to its author, not to a reviewer. While reviewing the H3 pilot on #5 I ran the full suite and got
Both first appear at 1.
|
PR #6 was closed as orphaned: its base was PR #5 -> PR #4, and that whole stack is closed. The content was assessed in the closing note as sound, with the salvage path named as cherry-picking reviews/independent/h3_* onto a live tip. This is that salvage, and nothing more. Re-founded on chatgpt/drive-github-hardening-20260919 (PR #3) rather than on the newest branch. PR #3 has been open since 2026-09-19, has survived every reshuffle that closed #4, #5, #6 and #9, and is an ancestor of the current tip, so this work flows forward instead of stacking on a moving target. Basing on the newest available head is the exact mistake that orphaned PR #6. The four files are unchanged from their reviewed state. Two are NON-CERTIFYING cross-check scripts, guarded so they skip when mpmath or numpy is absent. One is the completed R17 section 4 review record for RV-H3-SOLVER-20260921-01, still held outside reviews/records/ because tools/reviews_check.py requires the route key to appear verbatim in registers/json/review_queue.json and the register export in git remains the 2026-09-18 snapshot, which does not carry it. Filing it today would fail CI, so it stays parked with its reason written down. registers/CONSUMERS.json is regenerated because the salvaged README names registers/json/review_queue.json in prose, which the consumer scan attributes to that tab. One line, added by tools/consumers_check.py --write. Verified: all eighteen repository checkers exit 0. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01Fij9F1cYrAUDW7PhWQze1G
PR #6 was closed as orphaned: its base was PR #5 -> PR #4, and that whole stack is closed. The content was assessed in the closing note as sound, with the salvage path named as cherry-picking reviews/independent/h3_* onto a live tip. This is that salvage, and nothing more. Re-founded on chatgpt/drive-github-hardening-20260919 (PR #3) rather than on the newest branch. PR #3 has been open since 2026-09-19, has survived every reshuffle that closed #4, #5, #6 and #9, and is an ancestor of the current tip, so this work flows forward instead of stacking on a moving target. Basing on the newest available head is the exact mistake that orphaned PR #6. The four files are unchanged from their reviewed state. Two are NON-CERTIFYING cross-check scripts, guarded so they skip when mpmath or numpy is absent. One is the completed R17 section 4 review record for RV-H3-SOLVER-20260921-01, still held outside reviews/records/ because tools/reviews_check.py requires the route key to appear verbatim in registers/json/review_queue.json and the register export in git remains the 2026-09-18 snapshot, which does not carry it. Filing it today would fail CI, so it stays parked with its reason written down. registers/CONSUMERS.json is regenerated because the salvaged README names registers/json/review_queue.json in prose, which the consumer scan attributes to that tab. One line, added by tools/consumers_check.py --write. Verified: all eighteen repository checkers exit 0. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01Fij9F1cYrAUDW7PhWQze1G
PR #6 was closed as orphaned: its base was PR #5 -> PR #4, and that whole stack is closed. The content was assessed in the closing note as sound, with the salvage path named as cherry-picking reviews/independent/h3_* onto a live tip. This is that salvage, and nothing more. Re-founded on chatgpt/drive-github-hardening-20260919 (PR #3) rather than on the newest branch. PR #3 has been open since 2026-09-19, has survived every reshuffle that closed #4, #5, #6 and #9, and is an ancestor of the current tip, so this work flows forward instead of stacking on a moving target. Basing on the newest available head is the exact mistake that orphaned PR #6. The four files are unchanged from their reviewed state. Two are NON-CERTIFYING cross-check scripts, guarded so they skip when mpmath or numpy is absent. One is the completed R17 section 4 review record for RV-H3-SOLVER-20260921-01, still held outside reviews/records/ because tools/reviews_check.py requires the route key to appear verbatim in registers/json/review_queue.json and the register export in git remains the 2026-09-18 snapshot, which does not carry it. Filing it today would fail CI, so it stays parked with its reason written down. registers/CONSUMERS.json is regenerated because the salvaged README names registers/json/review_queue.json in prose, which the consumer scan attributes to that tab. One line, added by tools/consumers_check.py --write. Verified: all eighteen repository checkers exit 0. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01Fij9F1cYrAUDW7PhWQze1G
PR #6 was closed as orphaned: its base was PR #5 -> PR #4, and that whole stack is closed. The content was assessed in the closing note as sound, with the salvage path named as cherry-picking reviews/independent/h3_* onto a live tip. This is that salvage, and nothing more. Re-founded on chatgpt/drive-github-hardening-20260919 (PR #3) rather than on the newest branch. PR #3 has been open since 2026-09-19, has survived every reshuffle that closed #4, #5, #6 and #9, and is an ancestor of the current tip, so this work flows forward instead of stacking on a moving target. Basing on the newest available head is the exact mistake that orphaned PR #6. The four files are unchanged from their reviewed state. Two are NON-CERTIFYING cross-check scripts, guarded so they skip when mpmath or numpy is absent. One is the completed R17 section 4 review record for RV-H3-SOLVER-20260921-01, still held outside reviews/records/ because tools/reviews_check.py requires the route key to appear verbatim in registers/json/review_queue.json and the register export in git remains the 2026-09-18 snapshot, which does not carry it. Filing it today would fail CI, so it stays parked with its reason written down. registers/CONSUMERS.json is regenerated because the salvaged README names registers/json/review_queue.json in prose, which the consumer scan attributes to that tab. One line, added by tools/consumers_check.py --write. Verified: all eighteen repository checkers exit 0. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01Fij9F1cYrAUDW7PhWQze1G
PR #6 was closed as orphaned: its base was PR #5 -> PR #4, and that whole stack is closed. The content was assessed in the closing note as sound, with the salvage path named as cherry-picking reviews/independent/h3_* onto a live tip. This is that salvage, and nothing more. Re-founded on chatgpt/drive-github-hardening-20260919 (PR #3) rather than on the newest branch. PR #3 has been open since 2026-09-19, has survived every reshuffle that closed #4, #5, #6 and #9, and is an ancestor of the current tip, so this work flows forward instead of stacking on a moving target. Basing on the newest available head is the exact mistake that orphaned PR #6. The four files are unchanged from their reviewed state. Two are NON-CERTIFYING cross-check scripts, guarded so they skip when mpmath or numpy is absent. One is the completed R17 section 4 review record for RV-H3-SOLVER-20260921-01, still held outside reviews/records/ because tools/reviews_check.py requires the route key to appear verbatim in registers/json/review_queue.json and the register export in git remains the 2026-09-18 snapshot, which does not carry it. Filing it today would fail CI, so it stays parked with its reason written down. registers/CONSUMERS.json is regenerated because the salvaged README names registers/json/review_queue.json in prose, which the consumer scan attributes to that tab. One line, added by tools/consumers_check.py --write. Verified: all eighteen repository checkers exit 0. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01Fij9F1cYrAUDW7PhWQze1G
CoS skim-trap (2026-09-22) — closing as superseded by tip-aligned PR #9.
Base SHA is stale vs hardening tip
d107ab12; mergeable_state unstable; withdrawal/shadow controls re-integrated on tip via #9. Body correctly kept live_admission=false / credit 0 — no science fault, just superseded path.Standing approval used. Reopen only if a unique delta vs #9 must be salvaged.