cassidyrice Automation Safe Cycle
One idempotent loop: observe → two candidates → human gate → act or discard.
When to Use
- Recurring monitor/cron where mistakes are costly
- You want A/B candidates before retention
Process
- Define idempotency key (date, repo, URL…).
- Observe signal (watcher, scrape, API).
- Build candidate A and candidate B (not one hidden path).
- Score with explicit checklist; do not auto-promote.
- Human or high-bar gate: retain / promote / discard.
- Log cycle report; skip if idempotency key already completed.
NEVER
- Single-path automation without a discard option
- Write trusted memory without commit ritual
- Re-run side effects when key already done
Collision parents
verified-brain-commit-ritual, watchers, ai-skills-episode-factory