docs(m05): define regular module update flow for agents #560

Closed
opened 2026-05-28 01:43:00 +02:00 by codex · 0 comments
Collaborator

Scope

Write the practical update-flow runbook for routine module updates.

It should describe how an agent updates a module from source/artifact metadata to PR:

  1. find current artifact;
  2. find candidate artifact;
  3. decide risk class;
  4. prepare backup/rollback/smoke packet;
  5. open atomically scoped PR;
  6. use Patchwarden/Vistula labels where appropriate;
  7. avoid runtime mutation until explicit gate.

Spec sources

  • state/roadmap/current-platform-roadmap.md § 09 - Module upgrade waves
  • decisions/0022-* if present
  • W8 issues #501, #505, #506, #507, #508, #534
  • runbooks/ existing style

Acceptance criteria

  • Add or update one runbook only.
  • Include a small checklist suitable for Gemini/agent execution.
  • Include no broad architecture essay.
  • Make clear which module classes are manual-only.
  • No runtime mutation.

Out of scope

  • Implementing an updater.
  • Changing branch protection or automerge policy.

Gemini execution profile

Recommended executor: Gemini 3.5 Flash High, local repo access only.

Constraints:

  • Keep the PR atomic and boring.
  • Do not SSH, mutate runtime, edit secrets, or change live compose behavior.
  • Prefer generated tables/checks over more strategy prose.
  • If the issue is too broad, split once into 2-4 smaller issues and stop.
  • PR body must include Spec sources read.
## Scope Write the practical update-flow runbook for routine module updates. It should describe how an agent updates a module from source/artifact metadata to PR: 1. find current artifact; 2. find candidate artifact; 3. decide risk class; 4. prepare backup/rollback/smoke packet; 5. open atomically scoped PR; 6. use Patchwarden/Vistula labels where appropriate; 7. avoid runtime mutation until explicit gate. ## Spec sources - `state/roadmap/current-platform-roadmap.md` § 09 - Module upgrade waves - `decisions/0022-*` if present - W8 issues #501, #505, #506, #507, #508, #534 - `runbooks/` existing style ## Acceptance criteria - Add or update one runbook only. - Include a small checklist suitable for Gemini/agent execution. - Include no broad architecture essay. - Make clear which module classes are manual-only. - No runtime mutation. ## Out of scope - Implementing an updater. - Changing branch protection or automerge policy. ## Gemini execution profile Recommended executor: Gemini 3.5 Flash High, local repo access only. Constraints: - Keep the PR atomic and boring. - Do not SSH, mutate runtime, edit secrets, or change live compose behavior. - Prefer generated tables/checks over more strategy prose. - If the issue is too broad, split once into 2-4 smaller issues and stop. - PR body must include `Spec sources read`.
Sign in to join this conversation.
No labels
W6d-automerge-calibration
agent/claude-code
agent/codex
agent/hermes
agent/iskra
agent/ollama
agent/patchwarden
automerge-candidate
class/security-sensitive
cutover-gate
dependency/blocked
dependency/blocks-others
dependency/cross-repo
dependency/needs-confirmation
domain:agents
domain:ci
domain:docs
domain:forgejo
domain:infra
domain:memory
domain:runtime
domain:signal
domain:ux
flow/architecture
flow/blocked
flow/deployed
flow/done
flow/implementation
flow/intake
flow/maintained
flow/observed
flow/ready
flow/refining
flow/retired
flow/review
iterating
judge/codex-candidate
judge/hermes-candidate
judge/low-confidence
judge/needs-refinement
judge/operator-needed
judge/p0
judge/p1
judge/p2
judge/p3
judge/park
judge/patchwarden-candidate
judge/stale-priority
kind/adr
kind/bug
kind/chore
kind/feature
kind/infra
kind/ops
kind/refactor
kind/research
large-impact
merge/auto
merge/manual
merge/manual-dependency-conflict
merge/manual-failing-tests
merge/manual-merge-conflict
merge/manual-missing-review
merge/manual-operator-preference
merge/manual-red-zone
merge/manual-security-sensitive
merge/manual-unclear-scope
merge/manual-unknown
meta
mode:operator-only
mode:patchwarden-iskra-approved
mode:safe-auto
needs-operator-decision
needs-triage
not-ready
observed/erroring
observed/needs-followup
observed/pending
observed/retire-candidate
observed/unused
observed/used
operator-emotional
owner-attention
phase/02
phase/03
priority:p0
priority:p1
priority:p2
priority:p3
proposed
ready-for-agent
ready-for-operator
recovery
review:claude-reviewed
review:codex-reviewed
review:dziadek-reviewed
review:needs-human
risk/exposure
risk/process
risk/product
risk/runtime
safety:external-write
safety:no-prod-mutation
safety:prod-impact
safety:secret-touch
size/large
size/medium
size/small
size/tiny
size/unknown
source/adr
source/agent-generated
source/manual
source/operator-chat
source/voice-note
status:blocked
status:codex-ready
status:merged:pending-evidence
status:needs-evidence
status:operator-needed
status:parked
tier/full
tier/lite
tier/stacked
tier:0-platform-substrate
tier:1-iskra-value-layer
tier:2-tools-products-modules
type:bug
type:chore
type:docs
type:feat
type:policy
type:research
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
pdurlej/platform#560
No description provided.