Others

Outcome Watch

A closed loop that watches one specific change or experiment against a measurable finish condition, reports the verdict, and finishes itself. Paste it right after the change goes live.

Moderate setupShort cycleClosed loopBuilds over runs

Create directly in Loopany

How this loop works

Suggested schedule: Fits the metric (you set it)
Loop type: Closed loop — goal-bound; it finishes itself when the goal is met.
Exit condition: Finishes when the metric reaches the verdict, or the decision window closes.
Notifications: On by default — you're alerted on each run's outcome (completion or failure). Silence with notify: never.
Ease of starting: Some setup and context are needed before the first useful run.
When you see value: Tracks the metric against the verdict each run; the payoff is the conclusive pass/fail at the end.

The prompt this runs

Look at the specific change or experiment that just went live in this session - a shipped feature, an A/B test, a config or pricing change - and set up a closed loop that watches it to a measurable verdict. This is the measurable-verdict sibling of the Follow-up Tracker: that one generally watches aftermath, while this one is bound to one change and a concrete pass or fail question about it. Before creating anything, verify a concrete way to read the deciding metric exists on this machine - product analytics, an events query, logs, a URL, or gh - and run it once as a smoke test; if the outcome cannot actually be measured, say so and do not create a blind loop. Define the conclusive-verdict finish condition with me - the metric, the threshold, and the decision window (for example, "conversion is up a clear amount after N days, or the window closes") - and create the loop closed, with that condition as its goal. Propose a cadence that fits the metric and confirm it. On each run, read the metric through the verified path, report where it stands against the verdict along with the metric value, and finish the loop the moment the condition is conclusively met or the window ends - reporting the final verdict, pass or fail, plainly. Set up a modest dashboard at creation: an embed of the latest report plus a chart of the deciding metric over time.

This is the exact intent appended to the bootstrap when you create the loop — your coding agent reads it, then proposes cadence and config and confirms with you before creating anything.