WALLET / Code, builds & verification
What a verification badge means
Each badge answers one question and links to its own evidence.
A badge is a link to a result
A record must identify the product, version, source, tested set, environment, date, executor, result and limitations. It needs an accessible, hash-bound report. “Verified” without a stated scope is insufficient.
Three different levels
Internal tests check selected scenarios. An independent audit covers a defined external scope. A reproducible build links source and an artifact. These are distinct forms of evidence and none guarantees the absence of defects.
When a badge is withdrawn
When relevant code changes, evidence becomes outdated or contradictory results appear, a badge must stop endorsing the current release. Preserve the historical result. Failed or unrun cases must not be hidden behind a green aggregate count.