recipe-maintainers/cc-ci-orchestrator
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

AGENTS.md: ship infra work as PRs, self-merge, operator reviews retrospectively #6

Merged
autonomic-bot merged 1 commits from policy/pr-then-merge into main 2026-08-11 19:08:55 +00:00
Conversation 0 Commits 1 Files Changed 1
+26
autonomic-bot commented 2026-08-11 19:08:54 +00:00
Owner
Copy Link
Copy Source

Records the operator policy set on 2026-08-11, and is itself the first change to follow it.

For the two infrastructure repos — cc-ci-orchestrator and cc-ci:
branch → PR → merge it yourself once verified → operator reviews retrospectively.

The PR is not a gate; it is how the work stays legible after the fact. So the description has to
carry what changed, why, and the evidence it works — a PR that says "fix scanner" has failed at its
only job.

Explicitly does NOT extend to recipe repos. Any coop-cloud/<recipe> or its mirror is created
and verified but never agent-merged — those change what deploys on other people's infrastructure.
Agents own the tooling; the operator owns the recipes.

Also records the recovery for work that already landed on main without a PR: pin a branch at the
pre-work commit and open the PR against that, so the diff stays reviewable and merging only advances
the pointer — rather than rewriting published history. PRs #2–#5 were done that way.

Records the operator policy set on 2026-08-11, and is itself the first change to follow it. **For the two infrastructure repos** — `cc-ci-orchestrator` and `cc-ci`: branch → PR → **merge it yourself once verified** → operator reviews retrospectively. The PR is not a gate; it is how the work stays legible after the fact. So the description has to carry what changed, why, and the evidence it works — a PR that says "fix scanner" has failed at its only job. **Explicitly does NOT extend to recipe repos.** Any `coop-cloud/<recipe>` or its mirror is created and verified but **never agent-merged** — those change what deploys on other people's infrastructure. Agents own the tooling; the operator owns the recipes. Also records the recovery for work that already landed on `main` without a PR: pin a branch at the pre-work commit and open the PR against that, so the diff stays reviewable and merging only advances the pointer — rather than rewriting published history. PRs #2–#5 were done that way.
autonomic-bot added 1 commit 2026-08-11 19:08:54 +00:00
AGENTS.md: ship infra work as PRs, self-merge, operator reviews retrospectively 96c536f543 
Operator policy (2026-08-11). For cc-ci-orchestrator and cc-ci: branch, open a PR
whose description is written to be read AFTER the fact, merge it yourself once
verified, and let the operator review retrospectively. The PR is not a gate — it
is how the work stays legible — so a description that says 'fix scanner' has
failed at its only job.

Explicitly does NOT extend to recipe repos: those are created and verified but
never agent-merged, because they change what deploys on other people's
infrastructure.

Also records what to do when work has already landed on main without a PR: pin a
branch at the pre-work commit and PR against that, rather than rewriting
published history.
autonomic-bot merged commit 6ebc35bc18 into main 2026-08-11 19:08:55 +00:00
Sign in to join this conversation.
Reviewers
No Reviewers
Labels
No items
No labels
Milestone
No items
No Milestone
Projects
Clear projects
No projects
Assignees
Clear assignees
autonomic autonomic-bot kawaiipunk (KawaiiPunk) notplants trav (Trav Fryer)
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: recipe-maintainers/cc-ci-orchestrator#6