Repository navigation
Codex layer lane and adjudication judge default to effort max (standing GPT-6 rule); rules-only PR - #505
Merged
seathatflowsinourveins merged 1 commit intoSep 29, 2026
Conversation
… standing GPT-6 rule requires codex_lane.py's DEFAULT_EFFORT and `adjudicate.py codex --effort` were "high", and recipes/sota-convergence-practice.md step 4 and the tools/sota-convergence/README.md blind-wave example passed --effort high, so a caller who followed them ran the lanes below the recorded rule (docs/decisions/2026-09-27-model-currency.md, 2026-09-26-codex-worker-lane.md). Both defaults, the recipe, the README example and the --effort help now say max. Five tests that asserted the old lane default (three default-run model assertions, the dry-run command, one resume fixture) assert max. The append-only lane-provenance.json gains an entry in the codex and adjudication lists for the new bytes. With TMPDIR outside /tmp the lane suite passes 76 of 76 before the change and 5 tests needed updating after it; the 49-of-76 reported in the hand-off comes from the Codex sandbox's empty /tmp/.git, not from the flip. Its own pull request: codex_lane.py is a verdict_review_gate TRUST_PATHS file; no verdict row, wave or sealed artifact is touched. Co-Authored-By: Claude Sonnet 5.5 <[email protected]>
seathatflowsinourveins
deleted the
claude/codex-lane-default-effort-max-20260929
branch
September 29, 2026 14:46
seathatflowsinourveins
pushed a commit
that referenced
this pull request
Sep 29, 2026
…lure count #505 (7a95cf4, native-agent-stack-76) set the Codex lane and adjudication default effort to max, so the item leaves the "Unresolved" list and a short "Resolved since" paragraph names the change. The record said the flip fails 49 of the 76 tests in tests/test_codex_lane.py. That count came from one scratch run with no unmodified control and did not reproduce: two clean runs on the tree before #505 fail 5 tests from the constant alone (TMPDIR under /tmp and outside it) and the unmodified tree passes 76 of 76. The mistake goes in the anti-pattern log with its rule (run the same command on the unmodified tree first). Both files' hashes are registered on main's manifest in the same commit. Co-Authored-By: Claude Sonnet 5.5 <[email protected]>
5 tasks done
seathatflowsinourveins
pushed a commit
that referenced
this pull request
Sep 29, 2026
…lure count #505 (7a95cf4, native-agent-stack-76) set the Codex lane and adjudication default effort to max, so the item leaves the "Unresolved" list and a short "Resolved since" paragraph names the change. The record said the flip fails 49 of the 76 tests in tests/test_codex_lane.py. That count came from one scratch run with no unmodified control and did not reproduce: two clean runs on the tree before #505 fail 5 tests from the constant alone (TMPDIR under /tmp and outside it) and the unmodified tree passes 76 of 76. The mistake goes in the anti-pattern log with its rule (run the same command on the unmodified tree first). Both files' hashes are registered on main's manifest in the same commit. Co-Authored-By: Claude Sonnet 5.5 <[email protected]>
seathatflowsinourveins
added a commit
that referenced
this pull request
Sep 29, 2026
…its failure count (#507) * Dispatch record: close the GPT-6 lane effort item and correct its failure count #505 (7a95cf4, native-agent-stack-76) set the Codex lane and adjudication default effort to max, so the item leaves the "Unresolved" list and a short "Resolved since" paragraph names the change. The record said the flip fails 49 of the 76 tests in tests/test_codex_lane.py. That count came from one scratch run with no unmodified control and did not reproduce: two clean runs on the tree before #505 fail 5 tests from the constant alone (TMPDIR under /tmp and outside it) and the unmodified tree passes 76 of 76. The mistake goes in the anti-pattern log with its rule (run the same command on the unmodified tree first). Both files' hashes are registered on main's manifest in the same commit. Co-Authored-By: Claude Sonnet 5.5 <[email protected]> * Dispatch record: add the tool owner's control evidence to the correction native-agent-stack-76 reports that its own unmodified control, run in a clean worktree with the default TMPDIR while an empty /tmp/.git existed on the host (gone since), failed the same 49 tests with the error "--export ... is inside the git repository /tmp". The record and the anti-pattern row now say that the equal count suggests the earlier scratch run measured that environment, not the flip, and that this record did not reproduce it or keep its own error text. Hashes re-registered in the same commit. Co-Authored-By: Claude Sonnet 5.5 <[email protected]> * Dispatch record: attribute each fact of the correction to its source An automated review of #507 noted that the correction said the 49-test count "came from a scratch run with no unmodified control" while the owner's record shows the same 49 on unmodified main under the default TMPDIR while an empty /tmp/.git existed. The paragraph now states what the owner's record shows (49 failures from that environment, 76 of 76 with TMPDIR outside /tmp, 5 after the flip alone), that this section's 49 matched it from an uncontrolled scratch run whose error text was not kept, that /tmp/.git no longer existed when this was checked and clean runs show 5 failures, and the check to make before trusting a test count from a worktree under /tmp. Hashes re-registered in the same commit. Co-Authored-By: Claude Sonnet 5.5 <[email protected]> --------- Co-authored-by: Scout <scout@local> Co-authored-by: Claude Sonnet 5.5 <[email protected]>
8 of 10 tasks
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.
Scope
tools/sota-convergence/codex_lane.py) and the Codex judge/refuter (adjudicate.py codex) default to--effort max, the standing GPT-6 rule, instead ofhigh. It updates the recipe step 4 and the README blind-wave example that passed--effort high, five tests that asserted the old lane default, two resume-test fixtures that would otherwise have hidden their own rule, the append-onlylane-provenance.jsonregistry, and adds a decision record. It touches no verdict row, wave or sealed artifact (codex_lane.pyis aTRUST_PATHSfile ofscripts/verdict_review_gate.py, so it travels alone).5cfa2400lane:foundation(tools/,recipes/,tests/,docs/;manifests/evidence.jsonchanges only file hashes).tools/sota-convergence/codex_lane.py,tools/sota-convergence/adjudicate.py,tools/sota-convergence/lane-provenance.json,tools/sota-convergence/README.md,recipes/sota-convergence-practice.md,tests/test_codex_lane.py,docs/decisions/2026-09-29-codex-lane-default-effort.md(new),manifests/evidence.json.SOTA sources
docs/decisions/2026-09-27-model-currency.md(Codex CLI 0.157.1 row:gpt-6-astraatmodel_reasoning_effort=max),docs/decisions/2026-09-26-codex-worker-lane.md("maxis what every GPT-6 step here runs at") andrecipes/README.md("max, not the user defaultultra";ultrasendsxhighforgpt-6-astraper the bundled model catalog).codex exec -c model_reasoning_effort=<effort>(openai/codex, the installed 0.157.1): the lane passes the value through unchanged, so the change is the default only.tools/sota-convergence/lane-provenance.json, append-only;tests/test_verdict_lane_vendoring.py).Evidence-class table
tests.test_codex_lanepasses 76 of 76 on unmodifiedorigin/mainand fails 5 after the default flip alone (TMPDIRoutside/tmp); the hand-off's 49 of 76 is what the suite gives on unmodified main with the defaultTMPDIRbecause an empty/tmp/.gitexists on this hostlocal_integrationTMPDIR=/dev/shm/effort-tmp python3 -m unittest tests.test_codex_lane(main: OK 76; flipped: FAILED failures=5); the same command withoutTMPDIRon main: FAILED failures=49, each--export ... is inside the git repository /tmplocal_integration(mutation check on a scratch copy, restored)test_a_return_with_an_unknown_or_other_model_reruns_...; removing the provenance rule failstest_a_return_from_older_lane_code_or_prompt_reruns_...and others; removing the effort rule failsEffortResumeTests.test_a_return_made_at_another_effort_is_not_resumedlocal_integrationtest_codex_lane76,test_verdict_lane_vendoring14,test_adjudicate116,test_verdict_review_gate167,test_landscape95,test_record_verdicts125, all OKlocal_integrationTMPDIR=/dev/shm/effort-tmp python3 -m unittest discover -s tests -t .: 7563 tests, 16 failures and 2 errors, 783 skipped. 12 of the 18 (test_adoption_launchd6,test_adoption_bootstrap_macos3,test_adoption_version_probes2,test_adaptive_paper_metrics1: signal, interrupt and timing tests) pass in isolation on this tree and on unmodifiedorigin/main, so they failed only under the full run's machine load. The other 6 (test_codex_worker_lane:codex app-server, initialize: the server exited with code 1) fail with an identical set on unmodifiedorigin/mainlocal_integration,source_reviewcodex_lane_py_sha256andadjudicate_py_sha256equal the sha256 of the files (5662227f8c51…,81645780e37d…); an independent review compared every prior entry with the base filelocal_integrationpython3 scripts/verdict_review_gate.py --base origin/main --head HEAD: "no verdict rows changed"maxnot_measuredmaxGPT-6 jobs of another lane ran over the lane's 900 s default (maximum 977 s)Local commands run
Decision record
docs/decisions/2026-09-29-codex-lane-default-effort.md: the defect, the decision, the evidence, alternatives, the consequence and what would overturn it. An independent review of the first commit found one test-isolation defect (two resume fixtures built athighwould have let the effort mismatch hide the model and provenance rules) and four record defects (the consequence was understated as effort-only, the adjudication registry entry was described incompletely, some claims had no supporting measurement, the timeout risk atmaxwas unrecorded); this head repairs them.Consequence for other sessions, in one line: any Codex lane return or adjudication produced with the previous
codex_lane.py/adjudicate.pybytes, at any effort, cannot be recorded from a checkout with the new bytes (record_verdicts.pyrefuses other lane code) and is not resumed; finish an in-flight wave before this merges or rerun it after.flag:DEFAULT_TIMEOUTstays 900 s; pass--timeoutfor a layer that needs longer atmax, or raise the default in a follow-up once the layer lane's own durations are measured.flag:docs/grand-catalog-handbook.mdstill says the 2026-09-22 wave ran athigh; that is a dated fact about that wave and stays.Host evidence
Not applicable (no
evidence/hosts/files).Checklist
permissions: contents: read(none changed).🤖 Generated with Claude Code