Show HN: Evidence Graph – type checking for the specs your AI agent implements
@samchon/lint-plugin-evidence The evidence graph for the AI coding era: the guardrail for goal mode. When Claude Code or Codex works unattended, it can skip a requirement and still report "done." Evidence Graph makes every configured requirement demand an explicit acknowledgement from the code, test, or document that claims to satisfy it. Every acknowledgement names the exact target and states why it applies.
- ▪@samchon/lint-plugin-evidence The evidence graph for the AI coding era: the guardrail for goal mode.
- ▪When Claude Code or Codex works unattended, it can skip a requirement and still report "done." Evidence Graph makes every configured requirement demand an explicit acknowledgement from the code, test, or document that claims to satisfy it.
- ▪Every acknowledgement names the exact target and states why it applies.
Hacker News (AI / LLM) files mainly under ai. We currently carry 2,211 of its stories.
Opening excerpt (first ~120 words) tap to expand
@samchon/lint-plugin-evidence The evidence graph for the AI coding era: the guardrail for goal mode. Your spec is now a compile error. When Claude Code or Codex works unattended, it can skip a requirement and still report "done." Evidence Graph makes every configured requirement demand an explicit acknowledgement from the code, test, or document that claims to satisfy it. Every acknowledgement names the exact target and states why it applies. The compiler does not decide whether that reason is true—it forces the agent to commit to a concrete claim. A fabricated reason can no longer hide inside a plausible diff; it sits beside the declaration and evidence it contradicts. An agent can still lie.
…
Excerpt limited to ~120 words for fair-use compliance. The full article is at GitHub.