Merged
Conversation
moapacha
added a commit
that referenced
this pull request
May 4, 2026
#135) Follow-up to #134 — the maintainer pair agreed offline that the 4-row + Demos compromise still leaves audit-flagged claims visible. This PR removes the Demos section entirely and trims Receipts to the three rows that share one theme: each is a byte-precise CI gate that came out of an audit-named gap. What changes vs #134: - Receipts becomes 3 rows: sensor parity (#125), audio parity (#121), training-data lock (#130). All three are CI-gated, all three respond directly to a specific finding in the 2026-05-03 staff audit. - Demos section deleted. The hackathon-phase claims (BCE 0.7698, 5/5 spot checks, sub-2 ms sensor latency) are NOT demoted; they are removed. Auditing them as "illustrative" still left the audit-flagged numbers on the front page; deletion is honest. - New "Engineering" subsection holds the diagnostic-but-not-strict-receipt facts: workspace gates green from clean checkout (#127), codec independence enforced by lint:deps (#126), self-contained loupe HTML ~ 117 KB. Why: per the audit memo + the maintainer-pair review on PR #103, four of the original six receipts were misleading or unsupported. The right shape is "every Receipts row is a byte-precise CI gate" — anything diagnostic goes elsewhere or doesn't appear at all. Loupe HTML's 117 KB is a real reproducible measurement but not a CI-gated parity check, so it lives under Engineering rather than Receipts. Validated: - pnpm exec prettier --check README.md → green - git diff --check → clean - All four PR cross-links resolve to merged PRs (#121, #125, #126, #130). Per ADR-0013: README.md is doctrine-bearing per §1; this is drift correction tightening the gap between what's claimed and what CI gates prove. Cannot self-merge — needs an independent review pass.
This was referenced May 6, 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.
Closes #110.\n\n## Summary\n- adds a small repo-local codec boundary checker instead of introducing a new external dependency\n- fails when one codec package imports another codec package, including relative path escapes\n- wires the check into CI via a new root
Codec boundary check passed for 6 codec packages. command\n\n## Why this shape\nThe issue goal is to make the existing hard constraint executable. A small Node/TypeScript-based script keeps the surface tiny and avoids adding or just for one rule.\n\n## Validation\n- pnpm lint:deps\n- pnpm exec prettier --check scripts/check-codec-boundaries.mjs package.json .github/workflows/ci.yml\n- pnpm lint\n- pnpm typecheck\n- pnpm test\n- git diff --check