Earn-core: doc-reality claim audit (claims → code+test or labelled experimental)

[hyperpolymath]

Problem

Doc-reality drift is a recurring, self-acknowledged failure mode. STATE.a2ml [blockers-and-issues] doc-reality-drift:

• "ROADMAP.adoc claims Formal Proofs DONE — Avow attestation is data-type-only, no dependent-type enforcement."
• "README.adoc PTP claim sub-microsecond assumes hardware — code falls back to system clock without NIF" (I210 not arrived per READINESS.adoc).

Further drift found in the 2026-05-19 product review:

• README markets QUIC transport and SIMD/SNIF crash-isolation, but server/mix.exs has quicer and wasmex disabled (optional NIF block); SNIF degrades to ZigBackend (see ADR-0004/PR fix(snif): make Wasmex an optional, absence-guarded dependency #46).
• "<10 ms latency" and "500+ concurrent" are headline numbers with no scale benchmark (TEST-NEEDS.md → see #C5).

Why it matters

Every overclaim in the README taxes the credibility of the true core claims. The augmented layer's ambition is actively eroding trust in a strong core.

Acceptance criteria

• Audit every headline claim in README.adoc / ROADMAP.adoc; each must map to a code path and a test, or move to an explicit Experimental / Aspirational section.
• PTP, "Formal Proofs", QUIC, SNIF claims corrected to match the shipped build.
• STATE.a2ml doc-reality-drift entries closed.
• Policy codified in ADR-0007 so this doesn't recur.

References

STATE.a2ml, README.adoc, ROADMAP.adoc, EXPLAINME.adoc (the "honest receipts" pattern to generalise), ADR-0007. Part of the Earn-the-Core epic.

[hyperpolymath]

Tracked under the Earn-the-Core epic #53.