βοΈ Workflow: End-to-end Human-in-the-loop
A custodian agent must be autonomous in analysis but conservative in action. The workflow below keeps that separation clear.
Full cycle
- Trigger: manual, cron, GitHub webhook, new file, or scheduled audit.
- Preflight: verify branch, Git state, rules, active plan, and folders to ignore.
- Execution: read, audit, generate fixes or report.
- Isolation: create a dedicated branch or produce an unapplied patch.
- Report: summarize changes, sources, risks, and verifications.
- Human validation: review diff, questions, corrections.
- Merge: only after explicit agreement.
- Publication: build + deployment, separate from editing work.
Autonomy levels
| Level | Name | What the agent can do | Risk |
|---|---|---|---|
| 0 | Report-only | Read and produce a report | Very low |
| 1 | Patch proposal | Generate a patch or plan | Low |
| 2 | Branch | Modify a dedicated branch | Medium |
| 3 | PR | Open a PR with description | Medium |
| 4 | Staging | Deploy to preproduction | High |
| 5 | Publish | Publish to production | Avoid without human |
For this vault, the reasonable level is 2 or 3: branch/PR, human validation, then merge.
Minimal preflight
Before each run:
- Verify the repo is clean (
git status --porcelain): if the repo is dirty (uncommitted changes), the agent must abort and notify the operator. It must never bundle a human draft in progress into its commit. Explicit exception only:git stashwith a timestamped name if the operator enabled this mode in the agent configuration. - verify that the active maintenance plan is up to date (in this vault:
.agents/plans/directory in the repository); - ignore
_private/,build/,dist/,.git/, and obsolete logs; - refuse destructive commands;
- cite sources for any factual change.
Expected report
For a run with Git delivery, the PR (description + diff) is the primary trace. Otherwise, a chat report is enough:
- objective;
- modified files;
- sources consulted;
- proposed changes;
- tests or verifications;
- residual risks;
- next steps.