Plan-time corpus verification surfaced a third distinct gap the
brainstorm-sample missed: data-model.md:38/66/79/206/226 are 'see §"..."'
annotations inside fenced jsonc code blocks (verified: fences at
30-87 and 203-228; the 5 refs fall inside), where a Markdown link is
literal text — not a navigable link on any renderer.
Per the "two+ surfaced ⇒ ground the spec properly once, don't iter-patch"
discipline: amendment 2 is the definitive corpus-grounded pass, not a
fourth-patch returning later. Every convert-set ref's prose-vs-fence
status + exact bytes personally verified before amending.
- clause-5 (Concrete a): adds a strip_fences helper toggling on
triple-backtick / tilde lines; the per-file scan runs
targets(&strip_fences(&raw)); the RED-first synthetic vector gains
two fence-skip assertions (identity-stub of strip_fences ⇒ first
assert fails ⇒ genuine RED). Contract grows from 3 to 4 predicates
(+ fenced-code-not-scanned).
- Scope section: third out-of-scope carve-out — a 'see §"..."' inside
a fenced code block is schema-example documentation = the inline-
annotation analog of the nominal-mention carve-out (a // comment in
a code example is code documentation, not a 'go browse there'
pointer). Clean extension of the converged navigational-vs-nominal
principle.
- Acceptance 3: convert-set CLOSED and exhaustive — 8 prose refs
(float-semantics:69/100, embedding-abi:45, memory-model:44/105,
scope-boundaries:48/88), 2 disposition-(b) homeless removals
(pipeline:61, authoring-surface:180), 6 stay-prose (data-model
in-fence x5, embedding-abi:51). Iter-provenance suffixes stripped
on conversion. scope-boundaries:88 splits into a source link plus a
Pipeline cross-file link.
grounding-check third dispatch on the amended bytes: PASS, all 8
assumptions ratified (incl. corpus-state-verified A4-A7 per the
rolesplit precedent for text-enumeration claims).
Brummel
42ff44adf6