feat(platform-policy): encode ADR-0002 canary expectations #250

Closed
opened 2026-06-26 09:55:26 +02:00 by codex · 0 comments
Collaborator

Context

Platform issue pdurlej/platform#49 tracked ADR-0002 CI/canary enforcement. The original platform ADR designed a strict canary 3+3 merge gate, but current platform CI docs describe canary-required.yml as readiness-gated, not a fully operational strict gate.

This follow-up belongs in Patchwarden because platform PR policy now routes through Patchwarden artifacts/checks, while model review remains advisory.

Goal

Represent the ADR-0002/platform canary expectations as a Patchwarden policy/contract, without relying on Forgejo repository secrets and without executing PR-controlled code in a trusted review path.

Scope

  • Add or update Patchwarden policy support for platform PRs that touch canary-scoped paths.
  • Keep deterministic blockers separate from advisory/model findings.
  • Preserve the trusted-base-code/data-only PR-diff boundary.
  • Produce machine-readable artifacts usable by patchwarden contract-pr / pr-check.

Acceptance

  • Fixture PR metadata/diff for a canary-scoped platform change produces a deterministic missing-evidence finding when required canary/contract evidence is absent.
  • Fixture non-canary platform changes do not get blocked by the ADR-0002 policy.
  • The policy does not require provider/API tokens from Forgejo repository secrets.
  • Documentation references platform ADR-0002 as historical input, but does not claim the old platform #49 rollout is operational.

Source

Supersedes pdurlej/platform#49 as the implementation home. Platform keeps ADR-0002 as historical context; Patchwarden owns the active policy surface.

## Context Platform issue pdurlej/platform#49 tracked ADR-0002 CI/canary enforcement. The original platform ADR designed a strict canary 3+3 merge gate, but current platform CI docs describe `canary-required.yml` as readiness-gated, not a fully operational strict gate. This follow-up belongs in Patchwarden because platform PR policy now routes through Patchwarden artifacts/checks, while model review remains advisory. ## Goal Represent the ADR-0002/platform canary expectations as a Patchwarden policy/contract, without relying on Forgejo repository secrets and without executing PR-controlled code in a trusted review path. ## Scope - Add or update Patchwarden policy support for platform PRs that touch canary-scoped paths. - Keep deterministic blockers separate from advisory/model findings. - Preserve the trusted-base-code/data-only PR-diff boundary. - Produce machine-readable artifacts usable by `patchwarden contract-pr` / `pr-check`. ## Acceptance - Fixture PR metadata/diff for a canary-scoped platform change produces a deterministic missing-evidence finding when required canary/contract evidence is absent. - Fixture non-canary platform changes do not get blocked by the ADR-0002 policy. - The policy does not require provider/API tokens from Forgejo repository secrets. - Documentation references platform ADR-0002 as historical input, but does not claim the old platform #49 rollout is operational. ## Source Supersedes pdurlej/platform#49 as the implementation home. Platform keeps ADR-0002 as historical context; Patchwarden owns the active policy surface.
Sign in to join this conversation.
No labels
agent/claude-code
agent/codex
agent/gemini
agent/hermes
agent/iskra
agent/ollama
agent/patchwarden
area:business-model
area:competitive
area:discovery
area:forgejo
area:metrics
area:product-strategy
area:v0-core
cagan-grade-approved
client:platform
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
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
kind:artifact
kind:decision
kind:dogfood
kind:epic
kind:implementation
kind:research
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
mode:operator-only
mode:patchwarden-iskra-approved
mode:safe-auto
observed/erroring
observed/needs-followup
observed/pending
observed/retire-candidate
observed/unused
observed/used
priority:p0
priority:p1
priority:p2
priority:p3
ready-for-agent
review:claude-reviewed
review:codex-reviewed
review:dziadek-reviewed
review:needs-human
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:blocked-on-discovery
status:cagan-grade-review-pending
status:codex-ready
status:merged:pending-evidence
status:needs-evidence
status:needs-operator-decision
status:operator-needed
status:parked
tier:0-anchor
tier:0-platform-substrate
tier:1-core
tier:1-iskra-value-layer
tier:2-supporting
tier:2-tools-products-modules
type:bug
type:chore
type:docs
type:feat
type:policy
type:research
wave:1-foundation
wave:2-positioning
wave:3-validation
wave:4-economics
wave:5-operating
No milestone
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/patchwarden#250
No description provided.