QS4 · RECURRING MAINTENANCE · ONE WEEK

Put a low-risk maintenance loop on a weekly schedule.

Use a conservative link audit as a recurring one-pass loop: every firing writes a report, appends a full pass-log entry, and escalates source-replacement decisions instead of guessing.

Verified 2026-07-10 · read the logTwo real report-only firings were run from this repo. Both appended full-format pass entries; the second included a synthetic dead-link probe to exercise the escalation path without public or destructive changes.

All quick starts Run log

COPY-PASTE COMMANDS

Start from a clean clone or a report-only run-now firing.

1. Run one firing before you schedule it

git clone https://github.com/chrismaddern/loopmaster.ai.git loopmaster-qs4
cd loopmaster-qs4
uv run --with pyyaml python tools/link_audit.py --report examples/quick-starts/qs4/reports/YYYY-MM-DD-firing-1-link-audit.md --today YYYY-MM-DD

2. Exercise the escalation path safely

uv run --with pyyaml python tools/link_audit.py --report examples/quick-starts/qs4/reports/YYYY-MM-DD-firing-2-escalation-probe.md --today YYYY-MM-DD --extra-url https://example.com/__loopmaster_dead_link_probe__
# exit 1 is expected for this probe; append a blocked pass entry with one specific maintainer question.

3. Schedule it only after the run-now evidence exists

cat examples/quick-starts/qs4/schedule.md
# Choose GitHub Actions, Hermes cron, or your own scheduler. Keep each firing to one pass and review weekly.

AGENT PROMPT

Paste this after the first red check.

Read `examples/quick-starts/qs4/recurring-contract.yaml` and `examples/quick-starts/qs4/schedule.md`. Run exactly one report-only link-audit firing, append exactly one full-format pass-log entry, and stop. Do not replace sources, publish public content changes, change credentials, or spend money. If dead links or review-only URLs appear, stop blocked with one specific maintainer question and link the report.

ARTIFACTS

Templates, examples, and logs this page depends on.

Recurring contractexamples/quick-starts/qs4/recurring-contract.yaml
QS4 pass logexamples/quick-starts/qs4/2026-07-10-pass-log.md
Schedule instructionsexamples/quick-starts/qs4/schedule.md
Firing 1 reportexamples/quick-starts/qs4/reports/2026-07-10-firing-1-link-audit.md
Escalation probe reportexamples/quick-starts/qs4/reports/2026-07-10-firing-2-escalation-probe.md

DONE WHEN

The stop is evidence-based.

A run-now firing wrote a dated report and one full pass-log entry.
The schedule is explicit, but the weekly-review ritual is equally explicit.
Dead links or source-replacement choices stop as blocked escalations; no steering-loop operation is claimed.

After several recurring loops, learn why steering still needs its own evidence. →