EvidenceGate checks what a repository proves, what authoritative sources currently support, and where those two domains disagree before AI-generated code ships.
Open each self-contained report, follow its official citations, and download the canonical JSON bundle behind the deterministic decision.
The happy-path test passes, but required web-search, provenance, citation rendering, and negative-test evidence is missing.
3f7f66bef1f853761c629bfce3f86f60fbb5fcb8ee220fcaf25e12eef5c868a5Repository checks verify the implementation while validated official sources support the current external requirements.
6b11bd8461f8a5da2166d1dc2f863ca71ab3d6915257c549801d8b6c7fff1cf9No installation, account, API key, or source rebuild is required for this path.
See why a passing happy-path test cannot prove web search, source provenance, or safe clickable citations.
Inspect verified repository evidence beside supported external-source evidence for all fourteen required criteria.
Compare the stored decision, source registry, assessments, model-run metadata, and canonical SHA-256 hash.
Diffs, source analysis, commands, tests, and runtime probes establish implementation facts—but cannot establish whether an external API remains current.
Allowed official documentation establishes current requirements—but never proves that this repository implemented them.