Skip to content

spec(ship-two-models): v2.97 → v2.98 — §53 §50.4 cascade INTEGRATION-COMPLETE; contract v1.1 → v1.2 FUNCTIONAL#1495

Merged
noahgift merged 1 commit into
mainfrom
spec/section-53-step-5f4-landed
May 5, 2026
Merged

spec(ship-two-models): v2.97 → v2.98 — §53 §50.4 cascade INTEGRATION-COMPLETE; contract v1.1 → v1.2 FUNCTIONAL#1495
noahgift merged 1 commit into
mainfrom
spec/section-53-step-5f4-landed

Conversation

@noahgift

@noahgift noahgift commented May 5, 2026

Copy link
Copy Markdown
Contributor

Summary

§50.4 cascade is INTEGRATION-COMPLETE on main following PR #1494 (5f.4 CLI wireup) merging at 2026-05-05T01:48:14Z (commit 9afca16). The apr pretrain --init <PATH> flow is now end-to-end functional on CPU; the legacy "not yet wired" Err is RETIRED; step 5g LIVE is the only remaining gate before MODEL-2 ship-% can move from 57% → ≥58%.

This PR records the cascade-completion milestone in the spec (§53) and bumps the contract from PARTIAL_ALGORITHM_LEVEL to FUNCTIONAL.

Spec amendment §53

Contract bump v1.1.0 → v1.2.0 FUNCTIONAL

  • All 8 falsifiers PASS on main; 6/8 reach INTEGRATION via the user-facing apr pretrain --init flow.
  • verification_summary updated: tested 7 → 8; status partial → functional.
  • Added §52 + §53 references.
  • Promotion to DISCHARGED still requires §50.4 step 5g LIVE empirical 500-step fine-tune on canonical Qwen2.5-Coder-0.5B-Instruct.apr producing val_loss < 9.38.

Five Whys

  1. Why is §53 a separate amendment from §52? §52 identified the wireup gap; §53 records its closure. Same-day spec hygiene per feedback_falsifier_first_cascade_pattern.md.
  2. Why bump to FUNCTIONAL rather than DISCHARGED? FUNCTIONAL means "all falsifiers pass and the integration path is live"; DISCHARGED requires LIVE evidence on the canonical model+corpus combination (step 5g).
  3. Why call out 6/8 INTEGRATION rather than 8/8? Two falsifiers are inherently algorithm-level: FALSIFY-004 (forward-pass smoke is a unit test, not a CLI flow) and FALSIFY-008 (contract validation is a pv smoke).
  4. Why didn't §52 include the FUNCTIONAL bump? §52 was authored before 5f.4 landed. The contract was at v1.1.0 PARTIAL because 5f.3 was the last merge at that point.
  5. Why is the cascade 11 PRs and not 1 mega-PR? Per feedback_falsifier_first_cascade_pattern.md: one PR ≈ one falsifier discharge or one author-step. The cascade discipline keeps each merge auditable and bisectable.

Test plan

  • pv validate contracts/apr-pretrain-arch-polymorphic-v1.yaml exits 0
  • PMAT pre-commit quality gates pass
  • CI gate green (workspace-test, ci/gate)
  • Auto-merge fires on green CI

🤖 Generated with Claude Code

…ION-COMPLETE; contract v1.1.0 → v1.2.0 FUNCTIONAL

§50.4 cascade INTEGRATION-COMPLETE on main with PR #1494 merging at
2026-05-05T01:48:14Z. The `apr pretrain --init <PATH>` flow is now
end-to-end functional on CPU; the legacy "not yet wired" Err is
RETIRED; step 5g LIVE is the only remaining gate before MODEL-2 ship-%
can move from 57% → ≥58%.

Spec amendment §53:
- Updated falsifier scoreboard: 6/8 INTEGRATION (001/002/003/005/006/007
  via live CLI dispatch); 2/8 PARTIAL_ALGORITHM_LEVEL (004 forward-pass
  smoke + 008 contract validation are inherently algorithm-level).
- Step roadmap: 5a-5f.4 ✅ MERGED; 5f.5 (CUDA wireup) NOT YET STARTED;
  5g (LIVE 500-step fine-tune) operator-dispatchable on RTX 4090.
- Cascade ships statistics: 11 PRs over 2 days
  (#1471/#1472/#1473/#1474/#1475/#1476/#1478/#1479/#1481/#1482/#1483/#1486/#1494).
- MODEL-1 ship % unchanged at 91%; MODEL-2 ship % unchanged at 57%
  (gated on 5g empirical val_loss < 9.38 evidence).
- 3 CI andon classes documented as feedback memories during cascade
  (workspace-test missing-binary, trueno SIGSEGV-on-cleanup, auto-merge
  behind-state).

Contract apr-pretrain-arch-polymorphic-v1 v1.1.0 → v1.2.0 FUNCTIONAL:
- All 8 falsifiers PASS on main; 6/8 reach INTEGRATION via the
  user-facing `apr pretrain --init` flow.
- verification_summary updated: tested 7 → 8; status partial →
  functional.
- Added §52 + §53 references.
- Promotion to DISCHARGED still requires §50.4 step 5g LIVE empirical
  500-step fine-tune on canonical Qwen2.5-Coder-0.5B-Instruct.apr
  producing val_loss < 9.38.

`pv validate contracts/apr-pretrain-arch-polymorphic-v1.yaml` exits 0.

Refs: SPEC-SHIP-TWO-001 §50.4 cascade, PR #1494 merge commit 9afca16

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
@noahgift noahgift enabled auto-merge (squash) May 5, 2026 01:59
@noahgift noahgift merged commit 92c7e23 into main May 5, 2026
11 checks passed
@noahgift noahgift deleted the spec/section-53-step-5f4-landed branch May 5, 2026 02:22
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant