Run recurring monitoring with evidence

Define what deserves another cycle

For example, watch for changes affecting the workshop and produce a note when new information needs a decision. Choose permitted sources and a concrete progress criterion.

Configure timing and the human contact

A Goal has either a frequency or a parent objective, working windows and a human referrer. Its description and follow-up document preserve the frame between cycles.

A goal ready to resume — The goal brief, assigned agent and human contact; this example remains paused. — **A goal ready to resume** — The goal brief, assigned agent and human contact; this example remains paused.C23

Produce evidence on each pass

Each cycle creates an ordinary Task. The agent examines sources, compares them with available context and delivers a sourced result. A separate evaluator records progress and whether to continue or stop.

Cycle history — Existing cycles show progress, continuation decisions and missing information. Demonstration content replaces private data; historical states are preserved. — **Cycle history** — Existing cycles show progress, continuation decisions and missing information. Demonstration content replaces private data; historical states are preserved.C24

Handle blockers explicitly

A question to the referrer becomes a durable wait. Reminders are bounded: the default is one reminder after 24 hours, then a pause without a response. The objective should not loop indefinitely over the same missing input.

Judge the value of the monitoring

Compare new facts, source quality, corrections and cost per accepted cycle. Memory can preserve useful context; Dream maintains it according to configuration.

Find deliverables between cycles

Check accessible documents in your Goals filing, with provenance back to the Goal’s tasks. Manually filed documents should keep your choice. The folder gathers results; the cycle verdict and decision to continue remain in goal tracking.