Skip to content

refactor(features): one instruction per rule - #2115

Open
braboj wants to merge 1 commit into
mainfrom
refactor/features-score
Open

braboj wants to merge 1 commit into
mainfrom
refactor/features-score

Conversation

@braboj

@braboj braboj commented Oct 21, 2026

Copy link
Copy Markdown
Collaborator

Raises backend/features from 92.2 to 99.7 with one instruction per rule.

Section Change
Purpose Four noun-phrase uses and a closing paragraph → one sentence and two rules
Rules Owner and removal date, nesting, small path, runtime evaluation each one instruction; caching split out
Targeting Bold labels → instructions: roll out by percentage, target cohorts, canary first, hash the user ID
Evaluation "handler or service layer" → the feature's entry point
Observability Logging and per-variant metrics shortened

Checks

  • Smoke 35/35; conformance 12 passed, 0 failed, 1 not applicable; readings read
  • Fork sync, redundancy audit, score ratchet, markdownlint, pre-commit hooks

No CHANGELOG entry: the rules are unchanged in meaning.

🤖 Generated with Claude Code

The purpose list and the rollout strategies become instructions; long
rules with trailing explanations split or shorten. The failure-policy
rules from the last review are unchanged.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
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