feat(review): add advisory simplicity lane #128

Merged
pdurlej merged 1 commit from codex/simplicity-review-lane into main 2026-06-23 19:02:38 +02:00
Collaborator

Issue: #126
Value: quality
Effort: medium
Lead time: same-day

Summary

  • add disabled review_lanes.simplicity_review to policies/platform.v0.toml
  • keep default lane selection stable by choosing the single enabled lane when no --reviewer-lane is passed
  • add lane-aware prompt guidance for the D25 simplicity finding vocabulary
  • add review-quorum --advisory-lane so simplicity findings can be recorded without blocking required clean lanes

Verification

  • PYTHONPATH=src:. python3 -m unittest tests.test_policy_bundle tests.test_cli_render_review_prompt tests.test_cli_review_run tests.test_review_quorum tests.test_cli_review_quorum
  • PYTHONPATH=src:. python3 -m unittest tests.test_artifact_schema_contract tests.test_redrive_plan tests.test_cli_redrive_plan tests.test_policy_bundle tests.test_cli_render_review_prompt tests.test_cli_review_run tests.test_review_quorum tests.test_cli_review_quorum
  • PYTHONPATH=src:. python3 -m unittest discover -s tests
  • git diff --check

Boundary: no Ponytail runtime dependency, no hooks/adapters, no schema bump, no blocker promotion.

Refs #126

Issue: #126 Value: quality Effort: medium Lead time: same-day ## Summary - add disabled `review_lanes.simplicity_review` to `policies/platform.v0.toml` - keep default lane selection stable by choosing the single enabled lane when no `--reviewer-lane` is passed - add lane-aware prompt guidance for the D25 simplicity finding vocabulary - add `review-quorum --advisory-lane` so simplicity findings can be recorded without blocking required clean lanes ## Verification - `PYTHONPATH=src:. python3 -m unittest tests.test_policy_bundle tests.test_cli_render_review_prompt tests.test_cli_review_run tests.test_review_quorum tests.test_cli_review_quorum` - `PYTHONPATH=src:. python3 -m unittest tests.test_artifact_schema_contract tests.test_redrive_plan tests.test_cli_redrive_plan tests.test_policy_bundle tests.test_cli_render_review_prompt tests.test_cli_review_run tests.test_review_quorum tests.test_cli_review_quorum` - `PYTHONPATH=src:. python3 -m unittest discover -s tests` - `git diff --check` Boundary: no Ponytail runtime dependency, no hooks/adapters, no schema bump, no blocker promotion. Refs #126
feat(review): add advisory simplicity lane
All checks were successful
fallow-py / fallow-py-advisory (pull_request) Successful in 16s
37ffb8c086
Collaborator

🏛️ Architect review (loop) — sound, faithful to D25

Verified the subtle correctness property that makes "advisory" actually safe:

  • Non-blocking: _lane_entry sets status = "clean" for an advisory lane before the elif findings: status = "blocked" branch (review_quorum.py:161). So an advisory lane can never reach status == "blocked", and the verdict aggregation (if any(lane["status"] == "blocked" …)) never trips on it.
  • Non-inflating: advisory lanes don't pad the clean count either — clean_count is summed over quorum_lanes (required-only), and the required ∩ advisory = ∅ guard (review_quorum.py:42-45) ensures an advisory lane is never in that set. So it can't falsely satisfy min_clean.
  • Still recorded: the lane entry + its findings persist, just non-blocking — exactly D25's "record for dogfood, don't block" intent.

Also confirmed: lane is enabled = false / required_for = [] / fail_on_missing = false (default-off), and the change touches only policy/prompt/quorum — no schema bump, no forgejo_client/controller/executor surface, no new dependency. 601 tests green. D25 boundary (no Ponytail runtime dep, no blocker promotion) honored.

On cloud_review = "allowed": withdrawn as a concern — the lane is intrinsically a cloud lane (model = kimi-k2.6:cloud), so allowed is internally coherent, and it's default-off, so nothing egresses until an operator knowingly opts in (with D23's guard still clamping sensitive classes). No change requested.

Clean execution of the governance decision. — claude (architect loop)

## 🏛️ Architect review (loop) — ✅ sound, faithful to D25 Verified the subtle correctness property that makes "advisory" actually safe: - **Non-blocking**: `_lane_entry` sets `status = "clean"` for an advisory lane *before* the `elif findings: status = "blocked"` branch (review_quorum.py:161). So an advisory lane can never reach `status == "blocked"`, and the verdict aggregation (`if any(lane["status"] == "blocked" …)`) never trips on it. ✅ - **Non-inflating**: advisory lanes don't pad the clean count either — `clean_count` is summed over `quorum_lanes` (required-only), and the `required ∩ advisory = ∅` guard (review_quorum.py:42-45) ensures an advisory lane is never in that set. So it can't falsely satisfy `min_clean`. ✅ - **Still recorded**: the lane entry + its findings persist, just non-blocking — exactly D25's "record for dogfood, don't block" intent. ✅ Also confirmed: lane is `enabled = false` / `required_for = []` / `fail_on_missing = false` (default-off), and the change touches **only** policy/prompt/quorum — no schema bump, no `forgejo_client`/controller/executor surface, no new dependency. 601 tests green. D25 boundary (no Ponytail runtime dep, no blocker promotion) honored. On `cloud_review = "allowed"`: withdrawn as a concern — the lane is intrinsically a cloud lane (`model = kimi-k2.6:cloud`), so `allowed` is internally coherent, and it's default-off, so nothing egresses until an operator knowingly opts in (with D23's guard still clamping sensitive classes). No change requested. Clean execution of the governance decision. — 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!128
No description provided.