Version. v0.1 Date. June 10, 2026 Purpose. Answer the open questions blocking amendment v0.2 (renumbering, supersession targets, AC convention). Run against the live Ova spec repository. Report answers by number, with file paths and matched lines pasted verbatim.
Find the highest-version Ova Forge spec file (expected name pattern OVA_PROTOCOL_SPEC_V*.md, V2 in progress per project record).
find . -iname "OVA_PROTOCOL_SPEC*"
Report: full path of the highest version, and whether V2 exists or V1 is still current.
All checks below run against that file (call it $SPEC).
grep -oE "REQ-[0-9]{3}" "$SPEC" | sort -u | tail -5
grep -oE "REQ-[0-9]{3}" "$SPEC" | sort | uniq -d
Report: (a) the highest REQ ID; (b) any duplicate IDs; (c) total count of unique IDs. This decides whether the amendment renumbers from REQ-068, REQ-069, or higher.
The amendment and Part II cite these IDs as dependencies. For each, paste the full table row:
grep -E "^\| REQ-(010|016|021|028|030|051|063) " "$SPEC"
Report: each row verbatim. Flag any ID that is missing or whose description does not match its citation: 010 = serialized-state schema/indistinguishability, 016 = key derivation/seeds, 021 = path branching fan-out, 028 = decoy rejection/decrypt-and-discard, 030 = rekeying/key handling, 051 = FORAY audit entries, 063 = key material never persisted in plaintext.
grep -nE "vProg" "$SPEC"
Report: every line mentioning vProg, with line numbers. Separately list which of these are REQ table rows (candidates for supersession/rewording) vs. Scope/prose mentions (covered by the scope amendment).
grep -nE "p\s*<|0\.02|1/N" "$SPEC"
Report: how existing adversarial ACs phrase thresholds (expected: accuracy ≤ 1/N + 0.02 style per REQ-065). Confirm whether any existing AC uses p-values. This decides the single convention for the merged batch.
grep -nE "^## Phase|^### Cycle|Total build days|^## Glossary|^## Scope|^## Exclusions|^## Tech Stack" "$SPEC"
ls scripts/patch-build-days.js
Report: (a) phase/cycle headings present (which cycle should receive the new REQ rows — new rows go at the end of their cycle's table); (b) current Total build days value; (c) Glossary section present yes/no; (d) patcher script present yes/no.
ls -1 | grep -i "OVA_PROTOCOL_SPEC"
Report: all spec file versions present, so the next upload increments correctly and never reuses a number.
With items 1–6 reported, the next step is amendment v0.2 in one pass: renumber the ten new REQs (seven from the CR batch + three from Part II) above the true highest ID, fold in the Part II rows, fix supersession targets to the actual IDs found in item 3, normalize ACs to the convention found in item 4, place rows in the cycle found in item 5, and date everything June 10.
DUNIN7 · Ova Protocol CC Brief — Ova v0.6 amendment pre-repair checks — v0.1 — June 10, 2026