ar-loop

Topics in the source

• /ar-loop — Autonomous Experiment Loop
• Usage
• What It Does
• Step 1: Resolve experiment
• Step 2: Select interval
• Step 3: Create the recurring job
• Step 4: Store loop metadata
• Step 5: Confirm to user

Start a recurring experiment loop that runs at a user-selected interval. If no experiment specified, list experiments and let user pick. If interval not provided as argument, present options: Map to cron expressions: | Interval | Cron Expression | Shorthand | |----------|----------------|-----------| | 10 minutes | /10 | 10m | | 1 hour | 7 | 1h | | Daily | 57 8 | daily | | Weekly | 57 8 1 | weekly | | Monthly | 57 8 1 | monthly | Use CronCreate with this prompt (fill in the experiment details): Write to .autoresearch/{domain}/{name}/loop.json: When user runs /ar-loop stop {experiment}: 1. Read .autoresearch/{domain}/{name}/loop.json to get the cron ID 2. Call CronDelete with that ID 3. Delete loop.json 4. Confirm: "Loop stopped for {experiment}. {n} experiments completed." 3-day auto-expiry: CronCreate jobs expire after 3 days. For longer experiments, the user must re-run /ar-loop to restart. Results persist — the new loop picks up where the old one left off. One loop per experiment: Don't start multiple loops for the same experiment. Concurrent experiments: Multiple experiments can loop simultaneously ONLY if they're on different git branches (which they are by default — each expe

This is an excerpt. Refer to the complete source and its current requirements.