Automate recurring work

Recurring briefs and readouts are useful when the input evidence changes on a predictable cadence. The scheduling boundary matters: your agent harness schedules and executes the prompt; Deliberate does not.

Example: weekly readout

Create a recurring prompt in a harness that supports scheduled tasks:

Every Friday at 3 PM, open this project and run /deliberate readout week.
Use the current project sources. If required evidence is unavailable or
the command fails, report the failure instead of producing an empty readout.

At run time, the harness opens the project, invokes Deliberate, and writes the normal durable artifact.

Keep failures visible

Do not convert a missing source, failed command, or unavailable repository into a successful empty report. A trustworthy automation should:

1. Use the same checked-in context and methods as an interactive run.
2. Produce the normal artifact only when the workflow succeeds.
3. Surface failures through the harness’s task history or notification system.
4. Leave the repository unchanged when no valid artifact was produced.

What Deliberate does not provide

Deliberate has no scheduler, daemon, hosted worker, or model runtime. It stays portable because those responsibilities remain with the agent harness you already use.

For the workflow itself, see readouts.