The exceptions table gains the calibration's own near-duplicate dedup.
It is not a close call in either direction: at 1 - 1e-7 it tests vector
identity rather than similarity, and it runs on the fit's input, so a
calibrated comparison there would have to be calibrated by the fit it is
feeding.
More importantly, the invariant now has the enforcement its register row
always claimed. check_raw_cosine.py blocks in CI, and it caught a live
violation on its first run -- the identity matcher's no-calibration
fallback, which thresholded raw cosine distance and then fed
max(0, cosine) into the Bayesian accumulation as a posterior, past a
contract that says in terms it cannot be handed an uncalibrated number.
The note is explicit about what a pass does not prove: the check cannot
follow a cosine through a variable across statements, and says nothing
about the GEMM similarity matrix. Both remain conventions backed by
review. Writing that down is the point -- a checker trusted for more
than it does is how the raw-cosine fallback survived being read past.
TRACES: AR-024 | SR-002
Commits that implement, change, or withdraw a requirement carry a TRACES
trailer using the same token and syntax as the code tags, so one grep pattern
serves both.
This is the last link. Code tags say where a requirement lives; commit trailers
say when and why it changed, and `git log --grep=AR-012` then reconstructs a
requirement's whole history — which no other artifact provides.
A commit serving no requirement omits the trailer: absence is meaningful, and
inventing a tag to satisfy the form is how orphan tags get created. Withdrawing
a requirement counts as changing it, so the withdrawal stays findable.
Also updates the chain diagram, which still referenced the retired @implements
tag and the thematic A1..E8 IDs.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Gives the system specification an owner. It defines the PR-nnn project
requirements and SR-nnn cross-component contracts that every component spec
traces up to, and until now it lived in no repository at all.
The three component repositories are linked from the README and gitignored
here rather than added as submodules. A submodule pins a commit, so with
feature branches and worktrees in flight across the components, every
component commit would leave this repository's pointer stale. The dependency
is meant to run the other way: components pull this repository in for the
shared tooling and system spec, both of which change rarely.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
dtourolle
