Research NNN — [Feature name]

Status: open Step 1.5 output, written between the spec draft and the approval gate. open until every [NEEDS VERIFICATION] marker in spec.md has a verdict here; complete once they do. One entry per [NEEDS VERIFICATION] marker in spec.md, plus anything that turned up alongside.

Evidence is cited, not recalled. A claim about this repo cites a file and line; a claim about the outside world cites a response, a measurement, or a document. "I believe" is not evidence.

State up front what everything was verified against and when — a version, a commit, a date — so a later reader knows when these findings went stale.

V1 — [the question, as a question]

Question. [What the spec assumes, and what would have to be true for it to hold.]

Verdict. Confirmed | Refuted | Open — [one line of what that means for the spec.]

Evidence. [File and line, endpoint and response, measured number. Enough that someone else could re-run it and get the same answer.]

Caveat. [Optional. What this evidence does not establish — especially where a claim is confirmed on paper but not in practice.]

F2 — [an unprompted finding]

Findings that were not asked about but matter. Number them separately from the verification entries so the two are not confused: V for a spec claim being checked, F for something discovered on the way.

Why it matters. [Which requirement, criterion, or plan decision this touches.]

Refuted claims

A refuted claim sends the spec back to step 1 rather than being patched in place — a spec built on a false premise usually has more wrong with it than the one line that failed. Record what was believed, what is true, and what changed in the spec as a result.

Graduation

Findings that outlive this feature move to docs/architecture/ at step 6. List the candidates here so step 6 has a checklist rather than a memory test. A finding left only in this file will be re-discovered by the next spec.