Prove It

May 6, 2026 ยท View on GitHub

This is the pre-commit proof gate.

Minimum Questions

  1. What changed?
  2. What exact check proves it?
  3. What command or action produced the proof?
  4. What risk still remains?

By Task Type

Code changes

  • Targeted test added or updated
  • Test run completed
  • Relevant command output captured

Setup or environment repair

  • Bootstrap or health check re-run
  • Versions and paths confirmed
  • Broken state is gone

Auth or tenant work

  • Correct account used
  • Intended scopes requested
  • Connection state confirmed

Browser workflow

  • Use Playwright or a manual browser check
  • Capture the visible outcome

Desktop-only workflow

  • Run the desktop/manual validation
  • Do not claim browser E2E covers it if it does not

Commit Gate

Do not commit until you can answer:

  • The failing state is real
  • The passing state is real
  • The proof is recent
  • The diff matches the proof

After the checks and self-review are complete, stamp local proof for the git gate:

node .codex/hooks/git-guard.cjs prove --reviewed

If setup has not detected proof commands yet, pass them explicitly:

node .codex/hooks/git-guard.cjs prove --reviewed --check "npm test"

The stamp is stored under .git/codex-sdlc/proof.json, expires after four hours, and is tied to the current repo content so it does not dirty the worktree. Run guarded git commit / git push commands from the target repo root; repo context overrides such as cd, git -C, --git-dir, --work-tree, GIT_DIR, and GIT_WORK_TREE must be stamped in that target repo.