docs(burndown): record what the Clean and Cogent UI/UX burndown measured - #363
Merged
Merged
Conversation
Sixteen rules the workflow learned while burning down the milestone, each earned by a defect that reached a gate rather than by reasoning about one. Seven concern guards that were green, mutation-checked, and measuring something other than their own claim: a comparison blind to both sides moving together, a fixture building a DOM the application never renders, an absence asserted without its value, a criterion checking two properties of a recipe with a third that drifted, a census entry passing by inheritance after its class was deleted, two criteria each correct alone whose interaction nothing asserted, and a fix that removed the symptom its own test measured. The rest are dispatcher rules. Only a regression the change created blocks a merge. When a second review finds more of the same class, ask for the rule rather than the next list. A figure an instrument cannot fully see is a floor. A search built from enumerated forms is never finished. Estimates price the repository's contracts, not just its code, at roughly thirty-five test lines per acceptance criterion. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Signed-off-by: Jared Scott <jared.scott@variable.team>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Records what the Clean and Cogent UI/UX burndown measured, so the next one does not pay for it again.
What changed
Evidence
validate_plugins.pyclean;test_documentation113/113 passed, which asserts this repository's docs by literal path.Review guidance
Every rule names the measurement behind it rather than the principle. The most load-bearing is that a finding blocks a merge only when it is a user-visible regression the change created — applying that from the start would have saved this milestone its first pull request's four review cycles.
fo/burndown-lessons