PASS
Evidence sufficient
Before code reaches production, check for hallucination, hidden complexity, and long-term maintenance risk.
It does not decide for you. It makes decisions have evidence.
AI raw output
// “looks fine” — 9 deps, no proof
class UserService {
constructor(repo, logger, cache,
bus, metrics, retry, breaker,
validator, config) { /* … */ }
async getUser(id) {
// intent buried under ceremony
}
}
Maintainable result
class UserService {
constructor(
private repo: UserRepo
) {}
async getUser(id: string) {
return this.repo.find(id)
}
}
Confidence is not evidence.
先证据,后结论。
How it works
Challenge every “looks fine.”
Find structure that will rot later.
Decide: fix, record debt, or delete.
The receipt
Evidence sufficient
May continue — debt recorded
Not allowed to the next stage
Sign-off only. Does not deploy or trade for you. PASS / PASS_WITH_DEBT / BLOCK.
Evidence
Each case looked green on the surface. Each failed when claim met evidence.
Where it lands
AVAILABLE · OSS
Locally question every “looks fine” — terminal, review, receipt.
AVAILABLE · OSS
Automation continues only when evidence is sufficient — gate, sign, chain.
IN THE WORKS
High-risk work does not ship on feeling — pack, kill-shot, verdict.
ON THE ROADMAP
Wire into systems where a wrong pass costs real money.
Install the GitHub Action. Keep the receipt — PASS, PASS_WITH_DEBT, or BLOCK.
Partner with the founder
Chris Shi
Design partnerships, integrations, research — reach Chris directly.
Email: [email protected]