™Fini Proof · CLI 0.6.4
The writer of the change is not the verifier.
How fini-proof 0.6.4 sits next to Claude Code, Codex and an MCP client. The agent that wrote the change does not get to call the verdict a pass.
The 0.6.4 README describes three integrations that ship with the CLI. A Claude Code Stop hook can keep the agent from finishing while the verdict is FAIL and can hand it the findings. A PostToolUse hook can check a file as it is written. fini-proof mcp exposes check, explain_finding and list_rules to an MCP client, on the same licence path as the CLI. Codex and other agents are covered by an AGENTS.md section plus the CI gate. The gate is also described as failing a pull request that changes the checker’s own config or baseline without human approval.
Evidence records a maker (a person, an agent, or unknown) and a verifier. The product rule on the marketing page is the same one in the CLI comments: a verifier does not attest its own change.
The GitHub App that posts check runs is marked early, not generally available. An IDE extension is planned and is not in this package. Nothing on this page describes a Phase 2 schema, a corpus upload of source, or an online entitlement service. Those exist only on an unreleased candidate and are not the npm package 0.6.4.
Privacy Policy §23.5 describes an optional check-reliability contribution. The policy says it does not exist for any workspace until the company gives fifteen days’ notice. The published CLI does not turn that contribution on.