# win-loops catalog proof

This file documents the WIP loop catalog referenced by the article "Agentic Loops vs Cron Jobs for Background AI Agents".

The catalog uses readable Markdown loop packs. Each pack is meant to be inspectable by a human owner and executable by an AI assistant under a bounded contract.

## Loop pack format

Each loop pack contains:

- `LOOP.md`: business contract, trigger policy, authority rules, verification policy, and adaptive scheduling rules
- `SKILL.md`: scoped executor workflow for Codex, Claude Code, or win.sh Cloud
- `journal.md`: append-only memory for prior runs, approvals, refusals, and outcomes
- `examples/`: sample inputs and generated run briefs
- `evals/`: contract checks that validate the loop can be run safely

## Production candidates

The first production candidates are:

1. `bug-autofix`: diagnose production error groups, create scoped repair briefs, request approval for risky changes, and verify after deploy.
2. `seo-growth`: watch search performance signals, avoid thin content, choose the smallest useful SEO action, and verify after the search window.
3. `feedback-to-fix`: turn repeated customer feedback into a docs update, reply draft, issue, fix brief, roadmap evidence, or no action.

## Catalog inventory

The WIP catalog currently contains these 50 loop packs:

- `abuse-fraud-watch`
- `activation-optimizer`
- `ads-budget-guard`
- `analytics-tracking-qa`
- `backup-restore-drill`
- `broken-flow-repair`
- `bug-autofix`
- `churn-reason-mining`
- `competitor-watch`
- `compliance-watch`
- `content-refresh`
- `conversion-optimizer`
- `creative-testing`
- `crm-hygiene`
- `decision-outcome-review`
- `dependency-risk`
- `docs-support-gap`
- `email-deliverability`
- `email-outreach`
- `failed-job-recovery`
- `failed-payment-recovery`
- `feature-request-scoring`
- `feedback-to-fix`
- `gsc-rank-growth`
- `integration-health`
- `internal-linking`
- `knowledge-hygiene`
- `landing-page-match`
- `lead-followup`
- `lifecycle-nurture`
- `margin-watch`
- `mrr-anomaly`
- `new-page-opportunity`
- `performance-fix`
- `pricing-experiment`
- `programmatic-seo-qa`
- `quality-regression`
- `refund-dispute-defense`
- `regression-watch`
- `release-note-loop`
- `review-testimonial`
- `roadmap-reality-check`
- `security-scan-response`
- `seo-growth`
- `support-quality`
- `technical-seo`
- `traffic-growth-optimizer`
- `usage-drop-watch`
- `weekly-business-review`
- `winback`

## Hosted win.sh bridge

Local loop packs are files. win.sh Cloud adds the product layer:

- connector access
- hosted scheduling
- manual enable and disable controls
- approval requests
- durable traces
- artifacts
- journals
- adaptive next run scheduling
- loop suggestions from the assistant

The design goal is simple: a loop should be visible, reversible, and owned by the founder.
