Skip to content

docs(manifesto): state-based rules need a state-based gate (feedback from cli.py bloat)#157

Merged
hadamrd merged 1 commit into
trunkfrom
docs/manifesto-state-based-gates
May 29, 2026
Merged

docs(manifesto): state-based rules need a state-based gate (feedback from cli.py bloat)#157
hadamrd merged 1 commit into
trunkfrom
docs/manifesto-state-based-gates

Conversation

@hadamrd
Copy link
Copy Markdown
Owner

@hadamrd hadamrd commented May 29, 2026

Boiling-frog observation by the CTO — cli.py is 1705 LOC, 3.4x soft-cap, critic never flagged because each PR-delta was reasonable. Adds the rule + cites #155 / #156.

CTO observation: src/forge_loop/cli.py is 1705 LOC. The Python soft-cap
is 500. The critic never flagged it because cli.py grew 50-100 LOC per
PR over many merges. Each individual increment was reasonable; the
cumulative state-violation slipped past every per-PR review. Boiling-frog.

Adds the rule: a manifesto rule checkable only by codebase state (file
size, module count, deprecated-pattern count, test coverage, dead code)
MUST register a probe in the codebase auditor (#156). Per-PR critic
catches deltas; the auditor catches accumulation. Rule + gate ship
together — otherwise the rule is decoration.

References #155 (the cli.py split that this gap surfaced) and #156
(the auditor framework that closes the gap).
@hadamrd hadamrd merged commit 38fe599 into trunk May 29, 2026
2 checks passed
@hadamrd hadamrd deleted the docs/manifesto-state-based-gates branch May 29, 2026 00:29
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant