docs(w6d): record Patchwarden policy boundary #500

Merged
Iskra merged 1 commit from codex/w6d-patchwarden-boundary into main 2026-05-26 08:48:42 +02:00
Collaborator

Canary status: missing — rely on required Forgejo checks before merge

Canary Context Pack

Product story

W6d works for narrow boring PRs. After the Patchwarden decision, platform should not grow another local policy lane for review/automerge scope expansion.

What changed

  • Recorded that #488 is closed as superseded.
  • Documented the Patchwarden/platform boundary for future W6d expansion.
  • Kept current platform W6d scope as boring docs/status/roadmap only.

Why it changed

Operator approved closing #488 after Oracle review. The useful exact-head-SHA/provenance requirement belongs in Patchwarden, while platform remains the thin client and merge dispatcher.

Files touched

  • state/cycle/W6d-autonomous-merge-pilot.md

Runtime evidence

No runtime mutation. Local checks:

  • git diff --check -> pass

Known constraints

This is documentation/status only. It does not change workflows, readiness code, Patchwarden, runtime, secrets, or merge behavior.

Explicit out-of-scope

  • Implementing Patchwarden verdict provenance.
  • Expanding W6d scope.
  • Any runtime deploy/apply/restart.

Requested decision

Merge through the existing boring W6d lane if checks pass.

Merge blockers

Any accidental expansion of platform-local automerge policy.

Spec sources read

  • state/cycle/W6d-autonomous-merge-pilot.md — current W6d policy and proven runs.
  • PR #488 diff/body — superseded direction being recorded.
  • Oracle answer from platform-pr488-wave-status — advisory decision basis.

Closes: none.

Canary status: missing — rely on required Forgejo checks before merge ## Canary Context Pack ### Product story W6d works for narrow boring PRs. After the Patchwarden decision, platform should not grow another local policy lane for review/automerge scope expansion. ### What changed - Recorded that #488 is closed as superseded. - Documented the Patchwarden/platform boundary for future W6d expansion. - Kept current platform W6d scope as boring docs/status/roadmap only. ### Why it changed Operator approved closing #488 after Oracle review. The useful exact-head-SHA/provenance requirement belongs in Patchwarden, while platform remains the thin client and merge dispatcher. ### Files touched - `state/cycle/W6d-autonomous-merge-pilot.md` ### Runtime evidence No runtime mutation. Local checks: - `git diff --check` -> pass ### Known constraints This is documentation/status only. It does not change workflows, readiness code, Patchwarden, runtime, secrets, or merge behavior. ### Explicit out-of-scope - Implementing Patchwarden verdict provenance. - Expanding W6d scope. - Any runtime deploy/apply/restart. ### Requested decision Merge through the existing boring W6d lane if checks pass. ### Merge blockers Any accidental expansion of platform-local automerge policy. ## Spec sources read - `state/cycle/W6d-autonomous-merge-pilot.md` — current W6d policy and proven runs. - PR #488 diff/body — superseded direction being recorded. - Oracle answer from `platform-pr488-wave-status` — advisory decision basis. Closes: none.
docs(w6d): record Patchwarden policy boundary
All checks were successful
canary-required / collect-diff (pull_request) Successful in 4s
patchwarden-client-dry-run / collect-diff (pull_request) Successful in 4s
canary-required / canary (pull_request) Has been skipped
patchwarden-client-dry-run / dry-run (pull_request) Successful in 21s
base-is-main / guard (pull_request) Successful in 1s
patchwarden-pr-sanity / collect-diff (pull_request) Successful in 5s
patchwarden-pr-sanity / sanity (pull_request) Successful in 22s
b7d43b436a
Iskra approved these changes 2026-05-26 08:48:41 +02:00
Iskra left a comment

Approved by Iskra after W6d Matrix approval and deterministic readiness for the current PR head SHA.

Approved by Iskra after W6d Matrix approval and deterministic readiness for the current PR head SHA.
Iskra merged commit 636d723298 into main 2026-05-26 08:48:42 +02:00
Iskra referenced this pull request from a commit 2026-05-26 08:48:43 +02:00
Sign in to join this conversation.
No reviewers
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 milestone
No project
No assignees
2 participants
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!500
No description provided.