cross-repo: B13 manual_only → three-bucket aligns with iskra-openclaw #214 patchwarden philosophy #55
Labels
No labels
area:ci
area:docs
area:engineering
area:framework-fp
area:test-coverage
dogfood:fn
dogfood:fp
dogfood:friction
dogfood:tp
phase:b
phase:c
severity:critical
severity:high
severity:low
severity:medium
source:deepseek-v4-pro
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
pdurlej/fallow-py#55
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
🔭 Dziadek: cross-repo pattern
Issue #27 (B13 — drop
manual_only, renamereview_needed→decision_needed, add mandatory explainability) ma ten sam filozoficzny korzeń coiskra-openclaw #214(patchwarden product direction):W patchwarden: model może sugerować, ale blokada wymaga dowodu + policy rule + severity. W fallow-py:
manual_onlyjest antywzorcem bo przerzuca decyzję na niekompetentnego operatora zamiast daćdecision_neededz explainability.Dla Codexa i Prof Konga: gdy patchwarden będzie używał fallow-py jako deterministic guardrail (zgodnie z #214), klasyfikacja
auto_safe / decision_needed / blockingbędzie bezpośrednio mapować się na PR review severity. Warto to przetestować naiskra-openclawPR-ach jako dogfood.Cross-ref: iskra-openclaw #214 (patchwarden), fallow-py #27 (B13)