Repository navigation
foundation: retain GPT-only initial model-routes sweep - #1177
Merged
seathatflowsinourveins merged 1 commit intoOct 16, 2026
Merged
Conversation
This was referenced Oct 15, 2026
seathatflowsinourveins
added a commit
that referenced
this pull request
Oct 16, 2026
Single-family (Claude) initial sweep of foundation/model-routes under the CC's 2026-10-15T19:52Z ruling (A). Three landscape-sweep-worker stages ran on Claude Opus 5.5 at effort max, staged by the harness's own build_args.py, with a hand-built layer input because the layer is unregistered at 8053f14. 19 proposals (14 carried + 5 new), facts refuted 0, Claude fit refuted 8, 0 survivors in this half (the GPT fit vote is missing by design, so 11 are refuted only by absence). The critic's flagged follow-up was not run under the $40 cap and is recorded as a retained failure. No catalog, convergence or ledger file is edited; the merge with the GPT half (#1177) follows MERGE-PLAN.md and supports TRIAL labels only. Corrections from the CC's full read (verdict MICRO-full-afcc08cb.md): - No digest of unpublished bytes remains (correction #161). The digests of the unmasked layer input, the three stage scripts as run, the merged proposal list and the CC direction record are removed. hashes.json keeps only published or recomputable values and names the private originals under unpublished_originals without any digest. The direction record and the Muse re-qualification receipt are cited by name only, and no abbreviated digest is left. - The published decision_ref names the direction record without its digest, so requirement_sha256 is recomputed over the published fields with scripts/saturation_ledger.py requirement_sha256 (deviation 7). - returns.json is reconverted with convert.py --usage over the three stage usage records, which join_usage.py joins unchanged into usage-joined.json (deviation 8). All 38 Claude votes now carry the measured claude-opus-5-5 at effort max, and no effort_deviation or web_search_capped failure is retained. The counts are unchanged. - The cost estimate states the 1-hour cache TTL as its assumption (prompt-caching.md:144 gives the rate for each TTL). MERGE-PLAN.md cites recipes/saturation-sweep.md:99 and :174-175 and labels the vendor-document capture a PROPOSAL. - tests/test_provenance_digest_custody.py adds ModelRoutesClaudeHalfCustodyTests. Every 64-hex value in the record's two directories must hash a tracked file (as checked out or at 8053f14) or be prompts_sha256, requirement_sha256 or platform_profiles_sha256 recomputed with the harness's own code at 8053f14. Private records are cited by name, and no abbreviated digest stands in for a value. The class fails on the first head's tree and passes here. Co-Authored-By: Claude Opus 5.5 <[email protected]>
seathatflowsinourveins
added a commit
that referenced
this pull request
Oct 16, 2026
Single-family (Claude) initial sweep of foundation/model-routes under the CC's 2026-10-15T19:52Z ruling (A). Three landscape-sweep-worker stages ran on Claude Opus 5.5 at effort max, staged by the harness's own build_args.py, with a hand-built layer input because the layer is unregistered at 8053f14. 19 proposals (14 carried + 5 new), facts refuted 0, Claude fit refuted 8, 0 survivors in this half (the GPT fit vote is missing by design, so 11 are refuted only by absence). The critic's flagged follow-up was not run under the $40 cap and is recorded as a retained failure. No catalog, convergence or ledger file is edited; the merge with the GPT half (#1177) follows MERGE-PLAN.md and supports TRIAL labels only. Corrections from the CC's full read (verdict MICRO-full-afcc08cb.md): - No digest of unpublished bytes remains (correction #161). The digests of the unmasked layer input, the three stage scripts as run, the merged proposal list and the CC direction record are removed. hashes.json keeps only published or recomputable values and names the private originals under unpublished_originals without any digest. The direction record and the Muse re-qualification receipt are cited by name only, and no abbreviated digest is left. - The published decision_ref names the direction record without its digest, so requirement_sha256 is recomputed over the published fields with scripts/saturation_ledger.py requirement_sha256 (deviation 7). - returns.json is reconverted with convert.py --usage over the three stage usage records, which join_usage.py joins unchanged into usage-joined.json (deviation 8). All 38 Claude votes now carry the measured claude-opus-5-5 at effort max, and no effort_deviation or web_search_capped failure is retained. The counts are unchanged. - The cost estimate states the 1-hour cache TTL as its assumption (prompt-caching.md:144 gives the rate for each TTL). MERGE-PLAN.md cites recipes/saturation-sweep.md:99 and :174-175 and labels the vendor-document capture a PROPOSAL. - tests/test_provenance_digest_custody.py adds ModelRoutesClaudeHalfCustodyTests. Every 64-hex value in the record's two directories must hash a tracked file (as checked out or at 8053f14) or be prompts_sha256, requirement_sha256 or platform_profiles_sha256 recomputed with the harness's own code at 8053f14. Private records are cited by name, and no abbreviated digest stands in for a value. The class fails on the first head's tree and passes here. Co-authored-by: Claude Opus 5.5 <[email protected]>
5 tasks done
seathatflowsinourveins
force-pushed
the
codex/model-routes-initial-sweep-20261015
branch
from
October 16, 2026 03:41
6ecd0e7 to
5caccb3
Compare
6 tasks done
seathatflowsinourveins
deleted the
codex/model-routes-initial-sweep-20261015
branch
October 16, 2026 05:06
This was referenced Oct 16, 2026
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
Retain the SINGLE-FAMILY (GPT) initial foundation/model-routes sweep: all 14 carried candidates, one primary-sourced Fable 5.1 comparison proposal, route facts, retained GPT discovery/fit returns and named gaps. The layer stays incomplete; no winner, default or runtime change is claimed.
This rebuild carries the two publication-custody corrections and their fail-first guards. Route-to-inventory consistency is assigned to a separate PR that must land before C2 publishes; stale generations will be reported without failing validation.
5bab63233ef90260bec4a8ee0cec4f5e4431776c(main).8053f14e7e0817d2502dff2bb284bfb7e1b0152f; its retained protocol evidence remains historical.lane:foundation.evidence/artifacts/model-routes-sweep-20261015/,manifests/evidence.json, and the two approved guards intests/test_published_digest_privacy.py.SOTA sources
Read 2026-10-15 unless otherwise stated; full route-specific references are retained in sources.json and source-reviews/.
c1e30b7676975feb298b49eff6ff58923c04b89e, CHANGELOG.md and registry/control sources. Deployed source hashes are recorded separately; the local Codex registry differs and full build lineage remains unverified.unittest.TestCase.assertFalse/assertTrue, python/cpython v3.13.16, Lib/unittest/case.py, inspected 2026-10-16. New guards pass booleans to assertions so failures do not print rejected values.GPT-VERDICT-6ecd0e74d.mdand the direction record are cited by name only.Evidence-class table
Local commands run
The original seven schema/coverage/pointer checks are retained in checks.json. The privacy fix does not change role returns or their votes.
Decision record
PROTOCOL.md, ROUTES.md, checks.json, and custody-scan.json.
Required Claude discovery/facts/fit and completeness critic returns were not run in this GPT half. The same GPT session authored both roles. Formal survivors remain empty; missing votes do not retire unresolved carried candidates. The proposed ledger record remains nonappendable.
Custody residual
The superseded public head contained two unpublished-preimage digest values: one private-direction digest and one withheld-response digest. Both are removed from this rebuilt change; direction provenance is name-only and integrity registration covers only the published sanitized artifacts.
The pre-update PR body scan found zero matches for either class, including eight-character prefixes. Before this description update, the complete API-visible
userContentEditsconnection returned zero history nodes, with no unavailable or deleted nodes. The replacement description was also scanned with zero matches; a post-update history check is reported to the co-op. No value or prefix is repeated here. A lease update removes the superseded head from this PR branch's ancestry; old public commit objects, caches, notifications or external copies may persist. Their deletion is not claimed.Follow-ups
The nonblocking items in
GPT-VERDICT-6ecd0e74d.mdremain explicit: dated public captures and a retained source-correction assertion; failure/status retention in the proposed curl pipelines before executing them; and four pre-existing bare historical registry locators. These are not silently described as fixed. No proposed keyed measurement was run.The model-route/inventory consistency binding is a separately owned prerequisite for C2 publication, per the subsequent scope ruling. It will not introduce a merge gate on staleness.
Host evidence
Not applicable: no evidence/hosts/ or platform-status changes.
Checklist