Why this matters
In hardware programs, language can become misleading long before code or layout does. The repo’s truth-policy work is a defense against that failure mode.
Back to atlas
Evidence
Truth boundary
Verification Discipline
This discipline is one of the most credible parts of the repository. Rather than exaggerating progress, the project now treats proof quality as something that must be versioned and displayed.
Key points
The public narrative should emphasize that rigor, not hide it.
A weaker project would smooth over these distinctions; NeuroEtch benefits from naming them directly.
This discipline also makes the admin dashboards more meaningful because status actually means something.
Evidence model
Three execution modes
Synthetic, external-unverified, physical-validated.
Current practice
Truth policy docs
Fab handoff and confidence docs are part of the work.
Project payoff
Claim hygiene
Reduces drift between demos and actual signoff.
Operational consequences
Evidence discipline affects how runs are displayed, how benchmarks are framed, and which outputs are allowed to count as fab-ready statements.
Tag claims by evidence quality.
Keep reports tied to concrete runs.
Avoid promoting synthetic artifacts as physical signoff.