QS2 · CONTRACT + PASS LOG · 30 MINUTES
Put the loop on the record with task-contract.yaml and a pass log.
Move the task, check, budget, blocked rule, and log path out of the prompt and into files a reviewer can audit without replaying the transcript.
Verified 2026-07-10 · read the logThe same starter task ran under a filled task contract; its pass log records the state read, check evidence, written state, and terminal verdict.
All quick starts · Run log
COPY-PASTE COMMANDS
Start from a clean clone or a report-only run-now firing.
1. Copy the starter task and contract
git clone https://github.com/chrismaddern/loopmaster.ai.git loopmaster-qs2
cd loopmaster-qs2
rm -rf /tmp/lm-qs2
cp -R examples/quick-starts/starter-task /tmp/lm-qs2
cp examples/quick-starts/qs2/task-contract.yaml /tmp/lm-qs2/task-contract.yaml
cd /tmp/lm-qs2
bash check.sh
2. Run the contract check after the agent yields
cd /tmp/lm-qs2
bash check.sh
printf "Contract: "; grep "^loop:" task-contract.yaml
printf "Log path: "; grep "^log:" task-contract.yaml
AGENT PROMPT
Paste this after the first red check.
Read `task-contract.yaml`, do only the task it describes, and append a pass-log entry in the format shown by the template. Stop when the contract check is green, blocked with a specific question, or the budget is exhausted.
ARTIFACTS
Templates, examples, and logs this page depends on.
DONE WHEN
The stop is evidence-based.
- `task-contract.yaml` names the task, check, budget, blocked rule, and log path.
- The final pass-log entry includes check evidence and verdict `done`.
- A reviewer can understand the run from the contract and log alone.
Next: a goal loop varies tasks, not just actions. →