Skip to content

Commit 9c80b0a

Browse files
noahgiftclaude
andauthored
docs(M88): record trace-ffn-sub-block-gguf-v1 v1.0.0 PROPOSED scaffold — SHIP-007 layer-3 H1/H2 unblock (#75)
Cross-repo M88 record for aprender PR #1532 (squash ca033610a, 2026-05-06). First parallel-track autonomous work post M-GPU-MOE-1.x cascade closure. Authors the GGUF-side sub-FFN telemetry contract that pins the SHIP-007 layer-3 ffn_swigl bisection cascade architecture (4 stages, 4 falsifiers) and retro-records prior-work PRs that already shipped the dense-path forward_traced. Authoring discovery (lesson #2 of session): I initially claimed M-FFN-GGUF-1 (LayerActivation struct) and M-FFN-GGUF-2 (forward_traced) were PENDING. They're actually SHIPPED via prior PRs: - PR #1081 (squash 108f8f71c) — PR A scaffold (6 non-FFN fields) - PR #1082 (squash 30edfd357) — PR B sub-FFN populate (4 SwiGLU fields) Force-pushed to correct the contract before merge. Implementation stages (corrected): - M-FFN-GGUF-0: SHIPPED (this contract scaffold) - M-FFN-GGUF-1: SHIPPED (LayerActivation re-exported from apr_transformer) - M-FFN-GGUF-2: SHIPPED (PRs #1081 + #1082) - M-FFN-GGUF-3: PENDING (heavy comparison harness APR vs GGUF layer-3) - M-FFN-GGUF-4: PENDING (SHIP-007 fix PR cites H1 or H2) Methodology lesson: research existing implementation state via git log + grep BEFORE authoring contract scaffolds for "next work". Discharge potential per ship-two-models-spec.md §17.5: M-FFN-GGUF-3 → M-FFN-GGUF-4 cascade closure transitively discharges 5 MODEL-1 PARTIALs (SHIP-002, SHIP-005, SHIP-006, SHIP-007, SHIP-008). Cross-references bumped M87 → M88: - spec status header (line 5) - spec status snapshot (line 311) - spec Run 1 end-M - README:24 - CONTRIBUTING:258 `bash scripts/check-doc-drift.sh` green at M88. Co-authored-by: Claude Opus 4.7 <noreply@anthropic.com>
1 parent f65e4be commit 9c80b0a

3 files changed

Lines changed: 14 additions & 5 deletions

File tree

CONTRIBUTING.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -255,7 +255,7 @@ is the project blueprint. Major behavioral changes update both:
255255
1. The contract's `status_history` (factual, machine-readable record).
256256
2. The spec markdown (narrative + milestone roll-up).
257257

258-
Status as of v1.23.0 (2026-05-06): M0–M87 all SHIPPED; corpus complete
258+
Status as of v1.23.0 (2026-05-06): M0–M88 all SHIPPED; corpus complete
259259
(30/30); 13/13 gates green; companion ↔ aprender round-trip
260260
mechanically guarded. **M32d numerical-parity FUNCTIONALLY DISCHARGED**
261261
2026-05-02 (aprender PR #1228 squash 5235aaeb9): output transition

README.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -21,7 +21,7 @@ walks the two traces, applies per-tool semantic-equivalence rules,
2121
and emits a falsifiable parity score plus a closed-enum drift
2222
category for any mismatch.
2323

24-
**Status (2026-05-06)**: M0–M87 all SHIPPED. Contract at v1.23.0
24+
**Status (2026-05-06)**: M0–M88 all SHIPPED. Contract at v1.23.0
2525
ACTIVE_RUNTIME. Corpus complete at the spec-prescribed 30 fixtures
2626
(all score 1.0). Parity-matrix coverage 15/15 reachable
2727
(2 OOS at trace boundary). FALSIFY-CCPA-007 hard-blocking on every PR

0 commit comments

Comments
 (0)