Repository navigation
foundation: register the pending current model-routes scope - #1179
Open
seathatflowsinourveins wants to merge 3 commits into
Open
seathatflowsinourveins wants to merge 3 commits into
seathatflowsinourveins wants to merge 3 commits into
Conversation
5 tasks done
5 tasks done
This branch has not been deployed
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
Register foundation/model-routes as an explicit pending-empty scope so the documented two-family landscape sweep can address it. The catalog, taxonomy, research and quality coverage use the CC's exact 19:19Z sentence; native generated views retain status unswept, zero winners, no terminal state and no wave.
8053f14e7e0817d2502dff2bb284bfb7e1b0152f(current main).92c95deff39b8106534407e0b75f5c94f53504bd, one commit directly after reviewed headeedd595e06833706d6d7b5b1b3f4855786ee19ce; no rebase or history rewrite.2bda440abd751d9b8e9cb5bbc747a1071d1a5f72, one commit directly after92c95deff39b8106534407e0b75f5c94f53504bd; the CC FULL's three P3s are recorded in Follow-ups below.lane:foundation.0f9e90b1a31f10c213857b36a6d4aa5d5ee4290a. Rules prerequisite: Prepare rules for unrun pending scope registrations #1130, landed asf165498aa6340860ef52de3a720ca2981eced062. This PR rebuilds registration data on main and carries no stale rule code from the predecessor.The exact requirement is:
Scope: current model ids and routes for the Anthropic API (vendor docs and the claude-api skill), OpenAI through OmniRoute, and Meta's Muse through the muse-code provider (Wonder Full; the Muse fence rules hold).
SOTA sources
v3.13.16, Lib/unittest/case.py and loader.py: the repository's existing regression harness.eedd595e06833706d6d7b5b1b3f4855786ee19ce: build_ecosystem.py:293 requires exact taxonomy/surface coverage and supports empty bindings; build_new_wsl_handbook.py:187 binds input bytes; audit_reports.py:26 preserves canonical decisions and dated synthesis pointers; shared unrun admission distinguishes new pending registrations from selected, sealed or previously swept layers.Evidence-class table
Initial publication checks at eedd595
All checks used the existing idle-class scope wrapper.
All 12 changed/new published-file registrations match. Whitespace checks and installed gitleaks with redaction pass; staged scan found zero leaks. No new scripts or source-policy grants are needed. The normal pre-push privacy/history, registry and digest checks run without override.
Normal pre-push checks passed: 13,001 files scanned with zero privacy matches, three registry inventory tests passed, and the published-digest privacy guard passed. The no-reply author identity was checked before the normal push. Main stayed at the stated base through publication; no rebase was needed.
Decision record
docs/decisions/2026-10-15-model-routes-catalog-registration.md.evidence/artifacts/model-routes-registration-20261015/controls.jsonretains fail-first and pass-after counts.Review-wave corrections
The initial six catalog checks omitted additional publication consumers. The local review and GPT full read at
eedd595eidentified six consequences of adding the 21st foundation scope. Private reads are cited aspr1179-eedd595e/review_output.jsonandGPT-VERDICT-eedd595e0.md, without digests of unpublished bytes.build_dataregression and ecosystem publication check first failed with the exact layer-coverage error; four registration tests and the ecosystem check now pass.The initial targeted correction run passed 19 tests. The broader affected-suite run executed 496 tests with one failure, no errors and no skips: the publication control caught stale evidence registrations for the edits. After refreshing all 13 edited-file bindings through
scripts.host_receipts.register_file, that exact test passed in 62.735 seconds. This is 495 passing first-run tests plus the resolved one-test rerun, rather than a claim that the whole selection ran again. After release, the final fail-first recheck reproduced all six mechanisms on a clean reviewed-head export (24 tests, 16 assertion failures, one surface-join error, zero skips); the final-tree targeted selection then passed all 24 tests with zero failures, errors or skips. Finalpython3 scripts/validate.pypasses: 71 components, 12,144 hashed files, four profiles and 240 receipts. All 13 edited-file registrations match and whitespace checks pass. Native ecosystem/new-WSL/blind-audit/frozen-wave checks and the base-trusted gate pass; the gate reports no trust-path, rule-input or wave changes.The fold's normal pre-push checks also passed: 13,001 committed files scanned with zero privacy matches, three registry tests passed, and the published-digest privacy guard passed. No-reply author and committer identities were verified without printing them. The push was a fast-forward from the exact expected reviewed head, with no rebase or history rewrite. Staged gitleaks scanned 36,307 bytes with zero leaks.
Dated gap-ledger review correction
The GPT delta at
92c95deffdispositions the prior six blockers as closed. Its historical gap-ledger coverage correction now names the 2026-09-22/32-row scope and exempts only shared, history-aware admitted unrun registrations. The historical ledger and all source/receipt bindings stay byte-identical. Primary sources at92c95deff39b8106534407e0b75f5c94f53504bd:scripts/landscape.py:67-95,tests/test_gap_resolution_ledger.py:22-28,catalogs/landscape/gap-resolution-20260922.json:3-11, andblueprints/blind-catalog-convergence/audit_reports.py:43-46. Original seven tests first had one failure; nine tests with added winner/sealed/prior-sweep controls first had four failures. After correction, 21 gap-ledger/blind-audit/registration tests pass with no failures, errors or skips. Unmarked extra rows and missing dated rows still fail coverage. The CC FULL at that same reviewed head,MICRO-full-92c95def.md, passes; both verdicts are received, and the co-op authorized one P2 fold commit. Review records are cited by name only.The review's environment-limited execution counts (head: 92 modules/4,602 tests; supplied merged overlay: 100 modules/4,832 tests) are counts, not blanket passing claims. Its genuine-worktree receipt reports 13 modules/1,017 git-dependent tests at base and head with rc 0 and disclosed skips; that does not establish later-merge results. Missing source captures and historical pins remain gaps.
Local P2 verification also passes full
scripts/validate.py(71 components, 12,144 hashed files, four profiles, 240 receipts) and the base-trusted gate (no trust-path/rule-input/wave changes or violations). All three edited-file evidence bindings match. This fold changes only the gap-ledger test, decision, controls and evidence registry. The final recheck again passed 21 targeted tests, and the pre-correction row collection again produced the expected four failures across nine tests. Staged redacted gitleaks scanned 11,266 bytes with zero leaks. No-reply author/committer and expected remote-head lease were checked; the normal fast-forward push passed the 13,001-file privacy scan, three registry tests and the published-digest guard, without overrides.Follow-ups
The CC FULL's three P3s, retained by
GPT-VERDICT-2bda440ab.md, remain follow-ups. The round-three disposition is recorded by name inadjudication-pr1179-2bda440a-20261015.md:newest verdict checked_atsummary includes the registration date (docs/component-evidence-matrix.md:3,174and its JSON at reviewed line 9409). A follow-up in the owning generator should distinguish registration dates from completed-verdict dates; this timestamp does not establish a completed model-routes verdict.The inherited owner-chat P1 identified by
GPT-VERDICT-2bda440ab.mdbelongs to the separate scrub PR #1161 under the CC adjudication above. #1179 adds no paraphrase or synthetic-quote work. Its head remains held at2bda440abd751d9b8e9cb5bbc747a1071d1a5f72until #1191 and then #1161 land and the co-op relays#1161 MERGED. Then #1179 rebases onto the resulting main and regenerates the handbook throughpython3 scripts/build_new_wsl_handbook.py --write, with only forced binding refreshes. The resulting delta requires one GPT read and the CC delta before landing; no history rewrite of main is involved.Named gaps and next inputs
landscape-sweep --slots 2; later covering-sweep publication and candidate/taxonomy promotion remain separately owned admission/lifecycle work. No guard is relaxed here.Host evidence
No host receipt or platform-status change.
Checklist
92c95deffhead passed; its three P3s are retained above.#1161 MERGED, and the authorized rebase/regenerate-only delta passes GPT and CC reads plus green CI before landing; any later sweep keeps its own authorization and readiness requirements.