# Prove It

This is the pre-commit proof gate for research work.

## Minimum Questions

1. What claim or deliverable changed?
2. Which source tier verifies each changed claim?
3. Which confidence labels changed?
4. Which command or review proves the output is still safe to ship?
5. What risk remains unresolved?

## Required Checks

### Research Files

- Source-at-first-mention is present.
- Every substantive claim has a confidence label.
- `VERIFIED` and `SUPPORTED` labels match the evidence, not the writer's confidence.

### Generated Deliverables

- Regenerate outputs from source.
- Inspect the rendered HTML/PDF/Markdown.
- Confirm public outputs do not include private notes, salary, interview prep, internal strategy, or other forbidden audience-specific content.

### Slop and Regression

```bash
bash scripts/slop_scan.sh
bash scripts/regression_test.sh
```

Any new defect found by review becomes a permanent `check_present` or `check_absent` assertion.

### Cross-Model / Codex Review

Use native Codex review when the work is high-stakes:

```bash
codex review --uncommitted
codex review --base <branch>
codex review --commit <sha>
```

`review_model = "gpt-5.5"` controls Codex review model selection when configured.

## Git Gate

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

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

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

```bash
node .codex/hooks/git-guard.cjs prove --reviewed --check "bash scripts/slop_scan.sh" --check "bash scripts/regression_test.sh"
```

The stamp is stored under `.git/codex-rdlc/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` and `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 root.