CoroidYour AI software factory
Documentation

Sentinel

Autonomous monitors that watch for conditions and open remediation work when they find one.

Sentinel watches for conditions and acts when it finds one. Where a schedule is triggered by time, Sentinel is triggered by something becoming true.

Find it under the factory's Schedules area.

What it watches for

Conditions you define — a failing check, a pattern appearing in the codebase, a signal from a connected system, a standard drifting out of compliance.

When a monitor fires, it opens remediation work: an ordinary task, with a specification, going through the same plan, build, verify and review path as anything else.

Why this is the safe shape

Sentinel does not fix your code directly. It opens work that fixes your code, and that work produces a pull request you approve.

This matters more than it might appear. An autonomous system that edits production code directly has no review step at exactly the moment you would most want one — when nobody asked for the change and nobody is watching. Routing through the normal path means autonomy adds throughput without removing control.

Templates

Common monitors ship as templates so you are not writing the first one from scratch — recurring health checks, drift detection, and standard remediation loops.

Start from a template, run it advisory for a while, and adjust before letting it open work unattended.

Keeping it under control

Sentinel-opened work competes for the same agent slots as everything else. A monitor that fires often can quietly consume your capacity.

Three rules that keep it useful:

  1. Give it lower priority than human-requested work. P2 or P3.
  2. Make conditions specific. "A test is failing" fires constantly on a busy repository; "this specific check has failed on the base branch for more than an hour" fires when something is actually wrong.
  3. Review the yield. If a monitor has opened twenty tasks and you merged two, it is generating noise and budget burn, not value.

Watch the merge rate, not the fire rate

The honest measure of a monitor is what fraction of the work it opens gets merged. A monitor that fires rarely and is right every time is working. A monitor that fires constantly and is usually ignored is a tax.