engine-loop

engine-loop

Not an engine. Seo, social, video, outreach (and any custom engine) are the engines. engine-loop is the framework underneath them: it turns their runs into learning so those engines grow and compound over time.

Four jobs; run them in this order, because each depends on the one before.

Job	Cadence	Command
fetch metrics	daily	due_metrics.py → read → runlog.py metric
score + challenge	weekly	score_arms.py, then act on the verdict
generate inputs	weekly	see What to make next
report	weekly	render_report.py

Call them by full path — python3 ~/.agents/skills/engine-loop/scripts/<script>.py — from anywhere. That's the canonical store every install writes to, so the path is the same on every machine. Two shorter forms look tempting and both fail: scripts/… only resolves if the cwd is the skill folder, which is the one place the home isn't found from, and skills/… needs the home symlink, which is optional. The scripts locate the home from the current directory, so run them from the home or anywhere inside it — or pass --home <path> from outside. weekly.sh chains the deterministic ones and resolves its own paths.

The home is one folder per engine, plus shared/. Each engine folder is self-contained — its own engine.json (type, goal, primary metric), experiments.json, sources.json, templates/, inputs/, runs/, reports/. The loop scripts operate per folder and default to all of them; --engine <folder> scopes to one. Nothing is pooled across engines, so an agent rewriting one engine cannot break another — and two engines of the same type (outreach/ and outreach-investors/) are just two folders.

Starting fresh in a home you don't know? Read each engine's reports/latest.json first (and shared/insights.md for what the engines have learned from each other). It gives you the last period's runs, what shipped, the metric totals and their sources, every live experiment with its verdict, and how many runs are still owed a number — as data. Don't reconstruct that by reading CSVs.

---

Paths in this file: shared/… means the gtm home (~/gtm by default, or $GTM_HOME); templates/, inputs/, runs/ and reports/ mean the engine folder you're running, wherever it lives. The scripts resolve both through ~/gtm/engines.json, so read them as names rather than literal paths.