# Attach Evidence Atomically When Closing Checks

> Evaluate stored signals before closure, require evidence for manual checks, and clear proof when reopening.

Page: https://videotomd.com/b/text-local-evidence-aware-check-closure-eec469ea8cdf/
Tool: Operations · Tags: workflow, evidence, atomic-updates · 205 words, about 266 tokens
Pills: free · checked 2026-10-09 · Any AI · file tools · shell · on demand · frontier · ops

## Recipe

- Kind: workflow
- Stage: not set
- Loads: on demand
- Works in: Any AI
- Needs: file tools, shell
- Bring: nothing
- Cost: free
- Model: frontier
- Tested in: not yet
- Checked: 2026-10-09
- For: ops

## Put it here

Loads on demand: paste or attach it when the task comes up. To have it every session, put it where your tool reads instructions:

- Any AI: Coding agent: save as AGENTS.md in the project root (read natively by Codex, Cursor, Copilot, Gemini CLI, Kiro, Devin, Cline, Roo, OpenHands, OpenCode, Goose, Amp, Zed, Warp, Junie, Factory and Jules; Claude Code when no CLAUDE.md exists; Aider with --read). Chat: paste it first. Reload: new session. Check it loaded: ask it to repeat one rule from the file. Source: https://agents.md/ (checked 2026-10-12).

## Access

Membership: plans at https://videotomd.com/pricing/, or email then a plan at https://videotomd.com/b/text-local-evidence-aware-check-closure-eec469ea8cdf/. A member's browser downloads the file there; an AI without that session needs the member to attach it.
