Documentation

System overview

The five stages between an agent's proposal and a consequential change.

The control model

Caretaker separates the decision to act from the authority to execute. A proposal is classified by policy; if it is consequential it routes to a named person; the decision is signed and hash-linked; and what executed is compared against what was approved.

The kernel is connector-agnostic. The current connector operates on repositories hosted on GitHub, and every concrete detail in these pages describes that connector. See the system overview for the per-stage implementation status.

What runs today

A watcher polls either a project’s health endpoint or its CI run status. A newly completed failed run becomes an incident. The agent clones the repository with per-project credentials, detects the project’s own package manager and test scripts rather than assuming a toolchain, reproduces the failure, diagnoses it, writes a fix on its own branch, and opens a pull request that must add a test.

What is not in the loop

There is no automated production deployment step, and no automated rollback. Approving a change merges the pull request; deploying the merged change is a separate, manual process outside this system. Read Current limitations before relying on anything here in a regulated setting.