verify

Files (1)

• SKILL.md

SKILL.md (first lines)

# verify

You are not the implementer. You do not trust the implementer's claims. You prove it or you fail it.

1. Work in the full-build worktree (card body `Workspace:` line). Note `git rev-parse HEAD`.
2. Commands, in order:
   - the `verify:` command from `build/08-sandbox-plan.md`;
   - `hermes verify --json .` (detects bootstrap → build → test → start; use `--skip-start` for libraries and CLIs);
   - anything the acceptance criteria in `build/07-best-of-best.md` / `09-who-what.md` name as "done looks like";
   - every human decision in `build/gates/*.approved` (`note:` lines) and `build/decisions.md`: show evidence it is implemented (a test, a command, or file:line). One missing = FAIL.
   Record each as `cmd → exit N (Ns)`.
3. Tamper check (reward hacking guard): `git diff <base>...HEAD --stat -- '*test*' '*spec*'` and look for deleted tests, new `skip`/`xfail`/`.only`, loosened assertions, or snapshot rewrites without a stated reason. Any of these without justification in `build/runs/full-build-c*.md` is a FAIL.
4. Write `build/11-verify.md`. **Newest cycle on top**, older cycles kept below:

   ```
   ## Cycle N — <date>
   - result: PASS | FAIL
   - commit: <sha> on <branch>
   - commands:
     - <cmd> → exit 0 (12s)
   - failures: <what broke, file:line, first error line>
   - tamper check: clean | <finding>
   - verifier: <lane> (<vendor>)  — implementer was <lane> (<vendor>)
   ```
5. Append the build-log line.
6. PASS → `kanban_complete(summary, metadata={"verification": [...], "commit": sha})`.
   FAIL → `kanban_block(reason="VERIFY FAIL: <one line>")`. Do not complete. `hbs tick` starts the next build cycle with your file as its first input, or stops at the cycle cap for the human.

In chat mode (a human running this by hand in Claude Code / Cursor / Codex — never the Hermes orchestrator), do the same and update `build/STATUS.md` yourself. The verifier must be a different vendor than whoever built it.

From Kshintak/new-build-framework, MIT.

More from Kshintak/new-build-framework