Prove & send

Naro treats “done” as evidence, not as a confident sentence in chat.

---

1. Read what must be true

After your request, the work summary lists items that must hold before send.
Read them before you ask the agent to keep coding.

Human-only steps (consoles, secrets, real devices) are yours. The agent must not mark those done for you.

2. Prove each agent-owned item

For each open item, run a real command that exits successfully, then record it with the project’s prove command (install places this under scripts/).

Example shape:

python3 scripts/naro.py prove --criterion 1 --by "bun test"

Use the command named in the checklist for this repository — not a guess from another project.

3. Acknowledge human tasks (you only)

When a step requires you (OAuth console, secret placement, device check):

python3 scripts/naro.py ack-human --task <id> --evidence path/to/redacted-note.md

Put only redacted evidence in the repo.

4. Run the project seal

bash scripts/dod_mark.sh

Pass: clean result after your last edit.
Fail: named gaps — fix, re-prove, seal again. Evidence older than the current tree does not count.

5. Send

git push

If refused, the message names what is still open. Close those items; do not force-push around the gate.

Pull requests: include ship language in the request (open a PR, ship it) or use your agent’s ship skill when available. Authenticate your git host’s CLI if the flow opens remote PRs.

6. Checklist before you leave

• [ ] Work summary matched what you intended
• [ ] Board / checklist shows no surprise open items
• [ ] Agent-owned items proved with exit 0
• [ ] Human tasks acknowledged by you
• [ ] Project seal clean after last edit
• [ ] Push succeeded without bypassing the gate