Current evidence and gaps

Use this index to find the component, source version and scope behind a claim. This is a current reading guide, not a replacement for the dated audit records.

Question	Evidence route	Boundary
What does the Node gate promise?	Current guarantees and limits	Selected routes only; not a sandbox
What was checked for these tutorials?	Sources and captures	Linux examples at listed revisions
Which dependencies are shared?	Verification dependencies	Separate execution does not eliminate common defects
Which model statements exist?	Proof/source index	Model properties have named assumptions
Does the model match the runtime?	Correspondence	Current authorization correspondence gap remains
What do corpus passes cover?	Finite conformance	Tested inputs and pinned artifacts only
Can kernel bytes be rebuilt?	Kernel reproduction	Reproduction and authority are separate
What release was delivered?	Release provenance	Artifact/source identity is not full runtime correctness
Was a real client exercised?	Claude Code evidence	Scripted fixtures do not close real-client acceptance

The evaluator investigation and archive remain dated history. Old hashes, scratch paths and stop-ship observations are not automatically current product facts.

Previous: Scope glossary. Up: Documentation map. Next: Verification dependencies.