Skip to content

βš™οΈ 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

  1. Trigger: manual, cron, GitHub webhook, new file, or scheduled audit.
  2. Preflight: verify branch, Git state, rules, active plan, and folders to ignore.
  3. Execution: read, audit, generate fixes or report.
  4. Isolation: create a dedicated branch or produce an unapplied patch.
  5. Report: summarize changes, sources, risks, and verifications.
  6. Human validation: review diff, questions, corrections.
  7. Merge: only after explicit agreement.
  8. Publication: build + deployment, separate from editing work.

Autonomy levels

LevelNameWhat the agent can doRisk
0Report-onlyRead and produce a reportVery low
1Patch proposalGenerate a patch or planLow
2BranchModify a dedicated branchMedium
3PROpen a PR with descriptionMedium
4StagingDeploy to preproductionHigh
5PublishPublish to productionAvoid 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 stash with 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.

See also

Give my opinion

Everything is optional: one answer is enough. This site sends nothing: you send it, the way you choose.

Your noteNo note
Your opinion is about
About what? (several choices possible)
What will be sent
Send by e-mail

Private, no account: opens your mail program with the message ready, for ia-on-prem@damien.becherini.fr.

Open a GitHub issue β†—

Public, with a GitHub account. You read the issue again before you publish it.

To paste it wherever you want.

Give at least a note, a subject or a message to be able to send.