feat(executor): add guarded executor preflight contract #122

Merged
pdurlej merged 3 commits from codex/executor-preflight-contract into main 2026-06-23 18:19:21 +02:00
Collaborator

Issue: #107
Value: risk
Effort: medium
Lead time: same-day

Summary

  • add executor-preflight-check as a read-only guarded branch/PR executor contract
  • preserve deterministic controller/job-plan branch names for fix/worker-loop handoffs
  • publish the executor preflight schema/example and update the operator status, schema inventory, architecture module inventory, and vision-gap ledger

Verification

  • PYTHONPATH=src:. python3 -m unittest discover -s tests
  • jq empty spec/schemas/executor-preflight.schema.json spec/schemas/examples/executor-preflight.ready.json spec/schemas/job-plan.schema.json spec/schemas/controller-intake.schema.json
  • git diff --check origin/main
  • PYTHONPATH=src:. python3 -m patchwarden.cli status
  • patchwarden contract-pr on PR #122: Vistula pass, required check success, only expected policy_governance manual tier remains

Refs #107

Issue: #107 Value: risk Effort: medium Lead time: same-day ## Summary - add `executor-preflight-check` as a read-only guarded branch/PR executor contract - preserve deterministic controller/job-plan branch names for fix/worker-loop handoffs - publish the executor preflight schema/example and update the operator status, schema inventory, architecture module inventory, and vision-gap ledger ## Verification - `PYTHONPATH=src:. python3 -m unittest discover -s tests` - `jq empty spec/schemas/executor-preflight.schema.json spec/schemas/examples/executor-preflight.ready.json spec/schemas/job-plan.schema.json spec/schemas/controller-intake.schema.json` - `git diff --check origin/main` - `PYTHONPATH=src:. python3 -m patchwarden.cli status` - `patchwarden contract-pr` on PR #122: Vistula pass, required check success, only expected `policy_governance` manual tier remains Refs #107
feat: add executor preflight contract
All checks were successful
fallow-py / fallow-py-advisory (pull_request) Successful in 17s
3783c5653a
chore: keep executor schema inventory complete
All checks were successful
fallow-py / fallow-py-advisory (pull_request) Successful in 16s
97566ddcb5
Collaborator

🏛️ Architect review (loop) — sound, safe to merge

Reviewed against D20 + D24 as the riskiest gap (PW-G011 guarded executor). It honors the "risk" tag by staying read-only + fail-closed:

  • No real mutation: no create_branch / push / merge / post_* / set_status calls — only a verdict. patchwarden_write_allowed=false, external_write_allowed=false, merge_allowed=false hardcoded.
  • Fail-closed default-deny on writes: blocks unless the upstream job-plan has materialization.write_allowed=false AND external_write_allowed=false AND the job-plan verdict is ready (job_plan_write_allowed / job_plan_external_write_allowed / job_plan_not_ready blockers).
  • Head-bound: _valid_sha + expected-vs-live head comparison → needs_live_state on drift.
  • Chains the read-only contract stack (intake → approval-preflight #121 no-self-approval → executor-preflight) with each link refusing unless the whole chain keeps writes off.
  • 585 tests green; D20 lint passes (no merge endpoint introduced).

The decision chain is now provable end-to-end read-only before any actuator exists — textbook safe sequencing. The one thing I'll review hardest is the next PR: the real actuator that performs an actual Forgejo write (branch create / PR raise / merge) — that's where D24's mission/vision scope + hard-manual carve-out + no-self-approval get exercised live. This PR keeps that boundary clean.

No changes requested. — claude (architect loop)

## 🏛️ Architect review (loop) — ✅ sound, safe to merge Reviewed against D20 + D24 as the riskiest gap (PW-G011 guarded executor). It honors the "risk" tag by staying **read-only + fail-closed**: - **No real mutation**: no `create_branch` / `push` / `merge` / `post_*` / `set_status` calls — only a verdict. `patchwarden_write_allowed=false`, `external_write_allowed=false`, `merge_allowed=false` hardcoded. - **Fail-closed default-deny on writes**: blocks unless the upstream job-plan has `materialization.write_allowed=false` AND `external_write_allowed=false` AND the job-plan verdict is `ready` (`job_plan_write_allowed` / `job_plan_external_write_allowed` / `job_plan_not_ready` blockers). - **Head-bound**: `_valid_sha` + expected-vs-live head comparison → `needs_live_state` on drift. - **Chains the read-only contract stack** (intake → approval-preflight #121 no-self-approval → executor-preflight) with each link refusing unless the whole chain keeps writes off. - **585 tests green**; D20 lint passes (no merge endpoint introduced). The decision chain is now provable end-to-end **read-only** before any actuator exists — textbook safe sequencing. The one thing I'll review hardest is the *next* PR: the real actuator that performs an actual Forgejo write (branch create / PR raise / merge) — that's where D24's mission/vision scope + hard-manual carve-out + no-self-approval get exercised live. This PR keeps that boundary clean. No changes requested. — claude (architect loop)
pdurlej deleted branch codex/executor-preflight-contract 2026-06-23 18:19:21 +02:00
Sign in to join this conversation.
No reviewers
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
3 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/patchwarden!122
No description provided.