Skip to content

fix(tdg): CB-200 two over the baseline — one Rust fn refactored to A+, evidence/** excluded as reference harness, baseline lowered 602 → 601 - #3411

Merged
noahgift merged 4 commits into
mainfrom
PMAT-1098-cb200-two-over
Sep 17, 2026
Merged

noahgift merged 4 commits into
mainfrom
PMAT-1098-cb200-two-over

Conversation

@noahgift

@noahgift noahgift commented Sep 17, 2026 •

Copy link
Copy Markdown
Member

T-2 of the 0.68.0 train (release commit 27f070324) went NO-GO on pmat-comply: CB-200 TDG Grade Gate 604 below B vs baseline 602. The gate says raising the baseline is not the fix, so the roster was derived on both sides from pmat's own index (docs/audits/cb200-0.68-roster.md): baseline commit 7ee0ecaad reads 602 under the same pmat 3.40.2 (not a version delta), head 604 — three additions, one removal.

  • crates/aprender-serve/src/gguf/inference/forward/forward_qwen35.rs::from_model_and_layers (C+, cyc 15, from feat(qwen35): Qwen3.5 / Qwen3.8 hybrid GGUFs run on the CPU — apr run + apr chat (#3091) #3114) → A+ (cyc 4) by pure extraction; every helper A/A+; 4 tests pin the extracted qwen35_ssm_meta seam; aprender-serve --lib 15814/15814 green.
  • The other two additions are the mains of the vendored llama.cpp d1d3c3396 reference harness under evidence/parity/l0-1/…/producer/*.cpp, which exists to reproduce a cited measurement bit-for-bit. evidence/** is now excluded from [tdg] (not shipped code; refactoring it would invalidate the evidence). Re-measured with the exclusion: 601. Baseline 602 → 601, lowered.

pmat comply check --checks CB-200 is green on this tree.

no-close: #3114 — the PR that added the refactored function; referenced as history.

🤖 Generated with Claude Code

ont-delta: none — this PR adds a measurement note under docs/audits/ (the CB-200 roster) and touches no ontology row; no type, shape or anchor changes.

noahgift and others added 2 commits September 17, 2026 05:43
… in scope (#PMAT-1098)

`pmat comply check` read 604 against a baseline of 602 on the release commit. The box had
moved 3.40.1 -> 3.40.2, so the first question was whether the instrument moved rather than
the tree. It did not: the last main commit of 2026-09-15 (7ee0eca, the commit the 602 was
measured on) reads 602 under 3.40.2 as well, in its own detached worktree and its own index.
The +2 is code that landed on 2026-09-16.

The baseline is a count, not a roster, so the two definitions the report names are the
worst-graded survivors, not the new ones. Diffing the two rosters out of pmat's own
context.db (the derivation reproduces 602/481 files and 604 exactly) gives 3 added and 1
removed:

  + forward_qwen35.rs from_model_and_layers   C+ (15)  #3114
  + evidence/.../apr_raw_logits.cpp main       F (48)  #3354
  + evidence/.../raw_logits_compare.cpp main  C+ (21)  #3355
  - infer/inference_result.rs validate_gpu_first_token  B- (17)

Only the first is inside this ticket's scope. It is fixed by extraction, no behaviour
change: the qwen2/qwen35 metadata fallback chain becomes qwen35_ssm_meta, and the two
per-layer struct literals become own_deltanet_layer / own_attention_layer. C+ (15) -> A+
(4), every helper A or A+, and forward_qwen35.rs now has no definition below B. Reading
604 -> 603.

The function had no test, because it needs a real hybrid GGUF. The extraction leaves one
that does not: qwen35_ssm_meta takes a metadata map, so four tests now pin the defaults,
the qwen2-wins-over-qwen35 precedence, non-integer-falls-through, and the per-section RoPE
defaulting — behaviours the inline closure chain encoded and nothing asserted.

The remaining 1 over is the vendored llama.cpp reference harness under evidence/, which is
outside scope_paths and is a policy call (refactor the artefact / exclude evidence/ /
re-baseline to 603) rather than this ticket's. docs/audits/cb200-0.68-roster.md records both
measurements, the roster diff, the before/after grades, and the three ways to close it.

Pmat-Ticket: PMAT-1098
Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
…lude it and lower the CB-200 baseline 602 → 601

0.68.0 train T-2: pmat-comply RED on CB-200 (604 vs 602). Roster diff (worker, docs/audits/cb200-0.68-roster.md): three additions since the 09-15 baseline — forward_qwen35.rs::from_model_and_layers (C+, refactored to A+ in the previous commit) and two C++ mains of the vendored llama.cpp reference harness under evidence/. Excluding evidence/** and re-measuring gives 601; the baseline is lowered to that, never raised.

Pmat-Ticket: PMAT-1098

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
@noahgift noahgift added this to the 0.68.0 milestone Sep 17, 2026
@github-actions

github-actions Bot commented Sep 17, 2026 •

Copy link
Copy Markdown

§13.11 rung 1 — quorum shadow verdict

S13-SHADOW pr=3411 head=c3c7ea997bfa6970c3914c69b7723d33b708accf verdict=REFUSE class=Q1 arm_rc=1

Shadow mode: this records a verdict and merges nothing. A refusal
to arm is not a block (§13 adds zero rows to §7) — the pull request is
exactly as green as it was.

noahgift and others added 2 commits September 17, 2026 06:30
check_complexity_ratchet.sh pairs the two: '[tdg] baseline = 601 but scripts/cb200_baseline.txt says 602; the two move together'.

Pmat-Ticket: PMAT-1098

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
Pmat-Ticket: PMAT-1098

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
@noahgift
noahgift enabled auto-merge September 17, 2026 04:57
@noahgift
noahgift added this pull request to the merge queue Sep 17, 2026
Merged via the queue into main with commit 5d95ed5 Sep 17, 2026
18 of 19 checks passed
@noahgift
noahgift deleted the PMAT-1098-cb200-two-over branch September 17, 2026 05:45
guyernest pushed a commit to guyernest/aprender that referenced this pull request Sep 29, 2026
paiml#3411 paiml#3412), autopilot on paiml#3411 (paiml#3414)

Pmat-Ticket: PMAT-1098

Co-authored-by: Claude Fable 5.1 <noreply@anthropic.com>
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