This repository publishes a bounded evidence-gaps layer so external readers can see which important public-facing signals are still intentionally incomplete.
The machine-readable form lives in ../PUBLIC_EVIDENCE_GAPS_REGISTER.json.
- which public evidence gaps still remain today
- why those gaps exist without pretending they are already closed
- which stronger current surfaces still bound the claim set while a gap remains
- which manual review steps or future hardening moves would reduce those gaps
A serious public specs repository should not imply maturity it cannot yet prove.
This layer makes that posture explicit:
- it distinguishes between strong current evidence and missing future evidence
- it shows where public review is already possible and where only bounded claims are warranted
- it keeps reviewer, contributor, and program expectations aligned with the current public surface
The strongest related surfaces include ../PUBLIC_LIMITATIONS_REGISTER.json, ../PUBLIC_ADOPTION_READINESS.json, ../PUBLIC_FRESHNESS_MODEL.json, ../PUBLIC_ECOSYSTEM_VALUE_MAP.json, ../PUBLIC_RELEASE_METADATA.json, and ../PUBLIC_EVIDENCE_GAPS_REGISTER.json.
The evidence-gaps layer is a bounded honesty surface. It does not claim that every possible future gap is listed, and it does not replace stronger contracts, provenance, release evidence, or live validator behavior.