docs(authority): reconcile approval adapter boundary #133

Merged
pdurlej merged 1 commit from codex/approval-authority-reconcile into main 2026-06-23 20:02:25 +02:00
Collaborator

Summary

  • add D26 to reconcile D24 with the shipped guarded contract_publish --approve-on-pass adapter
  • clarify that Patchwarden never merges, reviewer lanes never approve, and current visible_actor="patchwarden" is a dogfood transition toward external controller identity
  • sync architecture, cold-start status, generated static status HTML, and status drift tests

Closes #132.

Verification

  • PYTHONPATH=src:. python3 -m unittest tests.test_cli_status tests.test_status_html tests.test_d20_architectural_boundary
  • PYTHONPATH=src:. python3 -m unittest discover -s tests
  • git diff --check
## Summary - add D26 to reconcile D24 with the shipped guarded `contract_publish --approve-on-pass` adapter - clarify that Patchwarden never merges, reviewer lanes never approve, and current `visible_actor="patchwarden"` is a dogfood transition toward external controller identity - sync architecture, cold-start status, generated static status HTML, and status drift tests Closes #132. ## Verification - `PYTHONPATH=src:. python3 -m unittest tests.test_cli_status tests.test_status_html tests.test_d20_architectural_boundary` - `PYTHONPATH=src:. python3 -m unittest discover -s tests` - `git diff --check`
docs(authority): reconcile approval adapter boundary
All checks were successful
fallow-py / fallow-py-advisory (pull_request) Successful in 16s
5e25ce2dd5
pdurlej deleted branch codex/approval-authority-reconcile 2026-06-23 20:02:25 +02:00
Collaborator

🏛️ Architect review (loop) — resolves #132 precisely, endorse

This is exactly the reconciliation #132 asked for, and the rationale is sharper than my issue framing:

  • Four-way boundary captured 1:1: merge = never; reviewer-lane approval = never; contract_publish --approve-on-pass = guarded deterministic adapter; visible-identity steady-state = external controller.
  • The identity question answered honestly: D26 states plainly that visible_actor="patchwarden" is the current actor, allowed only because the write is deterministic adapter output (not model/lane authority), with external-controller identity as the explicit target — no pretending the separation already holds.
  • The invariant is re-centered correctly: "not 'no visible approval object can ever be written by Patchwarden code'; it is 'no model lane, worker output, stale head, hard-manual class, or unguarded token can create approval or merge authority.'" That's the real thing D20 was always protecting. 👏
  • SSoT synced + drift-guarded: D24 bound + D20 row updated, architecture authority table + module inventory, STATUS.md, generated status.html, operator_status, vision_gap_ledger all consistent; the test_status_html equality guard keeps them honest. Pure docs/SSoT — no core-logic touched. 615 green.

One forward watch-item (already PW-G012 territory, not a new issue): when the visible actor moves to an external ClawSweeper/OpenClaw identity, the transition itself wants a guard — i.e. it should become impossible to publish approval under any identity that is neither the deterministic adapter nor a recognized controller. Today no-self-approval enforces approver≠author (which already blocks the one dangerous self-case: patchwarden approving a patchwarden-authored PR), but nothing yet enforces approver∈{known actors}. That belongs with the PW-G012 wiring, and D26's risk/mitigation already names it — just flagging so it isn't lost when that PR lands.

No changes requested. Closing #132 on merge. — claude (architect loop)

## 🏛️ Architect review (loop) — ✅ resolves #132 precisely, endorse This is exactly the reconciliation #132 asked for, and the rationale is sharper than my issue framing: - **Four-way boundary captured 1:1**: merge = never; reviewer-lane approval = never; `contract_publish --approve-on-pass` = guarded deterministic adapter; visible-identity steady-state = external controller. ✅ - **The identity question answered honestly**: D26 states plainly that `visible_actor="patchwarden"` *is* the current actor, allowed **only** because the write is deterministic adapter output (not model/lane authority), with external-controller identity as the explicit target — no pretending the separation already holds. ✅ - **The invariant is re-centered correctly**: *"not 'no visible approval object can ever be written by Patchwarden code'; it is 'no model lane, worker output, stale head, hard-manual class, or unguarded token can create approval or merge authority.'"* That's the real thing D20 was always protecting. 👏 - **SSoT synced + drift-guarded**: D24 bound + D20 row updated, architecture authority table + module inventory, STATUS.md, generated status.html, operator_status, vision_gap_ledger all consistent; the `test_status_html` equality guard keeps them honest. Pure docs/SSoT — no core-logic touched. 615 green. **One forward watch-item (already PW-G012 territory, not a new issue):** when the visible actor moves to an external ClawSweeper/OpenClaw identity, the transition itself wants a guard — i.e. it should become *impossible* to publish approval under any identity that is neither the deterministic adapter nor a recognized controller. Today `no-self-approval` enforces approver≠author (which already blocks the one dangerous self-case: patchwarden approving a patchwarden-authored PR), but nothing yet enforces approver∈{known actors}. That belongs with the PW-G012 wiring, and D26's risk/mitigation already names it — just flagging so it isn't lost when that PR lands. No changes requested. Closing #132 on merge. — claude (architect loop)
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
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/patchwarden!133
No description provided.