Three loop run logs you can inspect.

GOAL CONTRACT + TASK VARIATION

A bounded K6 run writes a goal contract, varies tasks across passes, retries one task, drops one unsupported claim, and records the checks before publication.

Goal loop: this one bounded run varies tasks until the K6 log exists and the contract checks are ready for terminal verification.

What it teaches: A goal loop earns its layer by varying tasks under a goal-level check. The log must show what task was selected, retried, or dropped, and each varied task needs its own task-loop evidence.

Contract / check

Goal contract requires a multi-pass run, task variation, local validation/build/test checks, and PR/CI/merge evidence before the delivery task is done.

What varied

Tasks under one goal varied across passes: orient scope, write durable state, add the public log, retry stale copy, drop an unsupported broader claim, and run terminal checks.

Stop reason

Done locally: all contract checks went green; repository delivery continued through PR, CI, and merge.

Cost / budget

Budget: six bounded passes over the K6 goal contract. Monetary cost: unknown; the log does not record spend.

• What the log proves
• Checked-in run logPrimary log for this bounded goal-loop run.
• Goal contractOutcome, checks, constraints, budget, iteration policy, and state paths.
• Checklist historyTask state and task variation history.
• Goal-contract templateTemplate source; not yet promoted to a validated Reference artifact.
• Learn: Loops all the way upLesson illustrated by this log.

RECEIPT · SAVED STATE + QUIET STOP

A supervised content-audit pass scanned configured files, wrote a report and state file, found no findings, and stopped without mutating public copy.

Task loop: the checked pass varied actions inside one bounded audit job — scan, report, save state, stop.

What it teaches: Use this when a schedule is only the trigger: the loop is the source-backed check, carried state, approval gate, and quiet stop when no review work exists.

Contract / check

Runner must exit 0, print report and state paths, separate findings from audit errors, and avoid rewriting public content.

What varied

Actions inside a single content-audit task: read configured targets, inspect files, write a report, write state.

Stop reason

Done: zero source-backed findings, zero audit errors, and no follow-up task required.

Cost / budget

Budget: one supervised pass over two configured files with max five link checks. Monetary cost: unknown; the log does not record spend.

• What the log proves
• Checked-in run logPrimary log for this example.
• Template guideReusable content-freshness template.
• Template sourceContract fields, permissions, checks, gates, and backend notes.
• Learn: Verify one runLesson illustrated by this log.

RECEIPT · DEDUPE STATE + SOURCE LINKS

A supervised landscape-watch pass read a fixture source, wrote a cited report, saved seen-source state, then reran to prove duplicate suppression.

Task loop: the checked pass varied actions inside one bounded watch job — fetch, dedupe, report, stop.

What it teaches: Research loops need carried state and source evidence; otherwise a scheduled search becomes a noisy repeated prompt.

Contract / check

First pass must record new source items; second pass with the same state must suppress duplicates; fetch errors must stay at zero.

What varied

Actions inside a single research-watch task: read sources, compare seen state, write report, update duplicate-suppression state.

Stop reason

Done: duplicate-suppression check succeeded and the fixture required no human escalation.

Cost / budget

Budget: one supervised dry run plus one duplicate-suppression check, max five items. Monetary cost: unknown; the log does not record spend.

• What the log proves
• Checked-in run logPrimary log for this example.
• Template guideReusable research-watch template.
• Template sourceContract fields, permissions, checks, gates, and backend notes.
• Learn: Loops all the way upLesson illustrated by this log.