Methodology
What “verified” means here.
A Proof claim is verified only within a stated scope, against stated requirements, with evidence you can rerun.
01 / Scope
A claim is only as strong as its scope.
Every claim here names three things before it says anything else: the scope it holds inside, the requirements it was judged against, and the evidence you can run yourself. Take one of the three away and the word “verified” carries no information.
When paperwork can be generated faster than it can be read, the artifact stops being evidence. So here is the working definition. A claim is verified when you can re-run it: the requirement it traces to, the check that enforces it, and the reproducer that pins the break, all executable by you, on your tree, without us in the room.
Scope is the load-bearing word. A verified claim holds for one declared component, at one code and graph version, against requirements a person approved. It says nothing about the module beside it, the release after it, or a behavior nobody wrote down. Every status published here carries the version it belongs to for that reason, and section 09 says what becomes of a claim once that version moves.
That is also why every claim is published with the route to its evidence attached. A requirement you cannot open, a check you cannot run, and a reproducer you cannot execute are three ways of saying the same thing: take our word for it.