# Evidence Bound Closeout

> Use when the user explicitly asks for evidence-bound-closeout, exact-byte artifact fingerprinting, or QA evidence bound to unchanged final file bytes.

- Skill: `gaofeng21cn/evidence-bound-closeout` (Agent Skill, multi-file: 3 files)
- Install (CLI): `npx skillmds@latest add gaofeng21cn/evidence-bound-closeout`
- Raw SKILL.md: https://api.skillmd.com/api/skills/gaofeng21cn/evidence-bound-closeout/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Coding & Dev Tools
- Author: gaofeng21cn (https://skillmd.com/u/gaofeng21cn)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/gaofeng21cn/evidence-bound-closeout

---


# Evidence-Bound Artifact Closeout

1. Finish the final build or export.
2. Fingerprint the final artifact.
3. Run QA after fingerprinting and confirm the artifact did not change during QA.
4. If QA changes the file, rerun QA against the new fingerprint.

```bash
python3 ~/.codex/skills/evidence-bound-closeout/scripts/fresh_artifact_closeout.py fingerprint <artifact>
python3 ~/.codex/skills/evidence-bound-closeout/scripts/fresh_artifact_closeout.py verify --artifact <artifact> -- <qa command...>
```

Report the exact path, size, SHA-256, QA command, exit code, and whether the fingerprint stayed unchanged.

This proves only that QA ran against unchanged bytes. It does not prove semantic correctness, source authority, owner acceptance, runtime readiness, release readiness, or Git lane absorption.