The question turned out not to be binary. Three distinct reference shapes are
already in use across the specs, with different binding force:
A artifact-name-as-ground-truth method-spec §7 :332-333
B directory convention + entries ingest-spec §11 :259-267
C informative catalogue link README :19
nav-golden has none of them. Verified: 0 hits in all five normative files
(method-spec, ingest-spec, CONCEPT, README, SKILL).
Two findings that constrain the option space:
- method-spec never names a repo path at all (`grep -c 'examples/'` -> 0; the
ten `/`-bearing tokens are in-bundle link syntax). A shape-B reference would
be the first one in that document.
- Elevating to §7 ground truth (O3) means rewriting two counting claims, not
adding a sentence: §7 "two JSON files ... the only ground truth" and the §1
conformance clause 2 "on the shared example bundle" (singular).
Also surfaced: nav-golden's serialization is not byte-pinned
(nav-golden-hierarchy/README.md:31-33 says MAY) while the sister class
ingest-golden is (:267, :280). Two conforming gates can disagree on the same
fixture today, independent of whether the spec names the class.
No normative text changed; no new text proposed. Ratification is the operator's.
Amendment-underlag §8: corrected the verification-log check, which cited
`grep -rn 'nav-golden' *.md` -> 0 hits. That command now returns 3 (all in the
gitignored, non-normative STATE.md). The claim holds; the check was too wide.
Re-aimed at the five normative files, and cross-linked to the new document.
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01XYkLsRfSBBUjULS219Fy8X
Kjell Tore Guttormsen
3f18ca7c27