run-without-you

Topics in the source

• Phase 4 — Run Without You (the recurring loop)
• Choose the trigger
• Workflow (recurring)
• Hard rules
• Forcing-question library (recommend + cite)
• Tools

A scheduled deployment fires a fresh session on a cron cadence — the agent runs without you. Each firing can carry its own outcome, nesting the bounded grade→iterate loop inside every recurring run. See ../../references/loops-and-workflows.md. | Answer | Shape | Tool | |---|---|---| | "every morning / weekly / nightly" | recurring cron deployment | deploymentbuilder.py + cronvalidator.py | | "when X happens" | event-driven curl (documented, not scheduled) | deploymentbuilder.py (message only) | | "only when I ask" | on-demand (no deployment) | none — just re-send a user.message | 1. Validate the schedule. Invalid cron/timezone → exit 1. Read the DST note: wall-clock semantics mean spring-forward times are skipped and fall-back times fire twice — avoid 02:00–03:00 in DST zones if exactly-once matters. 2. Build the deployment payload. --nest-outcome includes the rubric so each firing self-grades. The tool prints the BYOK curl to create it and to test it once with the manual run endpoint before trusting the schedule. 3. Test before you trust. Fire one manual run, read the verdict, only then leave the cron in place. Pin the agent version in the deployment once it passes. 4. Finalize th

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