Review policy: allow safe atomic stack slices
Review Loop 4.0: make public history immutable
review loop 3.4: keep per-PR reviews private
review loop 3.3: scope limiter to GChat blockers
review loop 3.2: remove author eligibility gates
review loop 3.1.1: correct attempt accounting
review loop 3.1: add operating safety gates
review loop: require current in-repo spec authority
Review loop 2.0: route decisions from current authority
review loop 1.9.1: enforce the architecture template
review loop 1.9: surface architecture burden
review loop 1.8: stop unproven features early
Review loop 1.6.0: cap visual remedy search
Review-5548: record static-shell and CLS review
review loop: require user impact and evidence
Sync current review presentation template
Review loop 1.0.0: version the kit and every presentation
Wiki: describe the loop as it runs tonight
- Home: kit is source of truth (was backwards), R0-R30, POSTING status with
what still needs Cindy, presentation named as the product, mirror table
- Running-It: rewritten walkthrough — review -> presentation -> gate -> a new
presentation; rubric and rules as the two inputs; STEP 7's five checks; gate
artifacts; tiers; three consumers; R1g and R12c corrections
- Review-Presentation: the artifact the gates iterate on; adds USAGE, TIME and
SOLUTION-as-decisions; links the harness and evidence templates from the
visual-evidence slot
- Measurement-Harness: sync the two probe traps from the operational copy
- Aged-PRs: triage/full tiers, and the NEED test measured as a sorter
- Rulings: drop the duplicated escalation rule, reunite ruling 1's note, add
ruling 8 (divider margin)
- Calibration, Draft-Rubric-Integrated-Loop, retrospective: direction of flow,
what actually shipped, and tonight's numbers
PROBLEM is a user-facing failure; the absence of a mechanism is never a problem
R15e: visual evidence is a slot — frames, or a stated reason there are none
R15d: anything that got larger reflows its neighbours; low-risk gains a fourth condition
R16d: a break must reach the verdict. R14f: test the far side of a clamp
R16c: an Impact slot for the change, numbered arrows for each finding
R16b: the API slot enumerates signatures — writing it out is the check
R18c: perf tests for O(N) work on hot flows; assert render counts, not milliseconds
R18b: effects earn a question; direct DOM writes are a pattern, two owners is the bug
R18 performance slot, R19 the low-risk class
R17: give the review pages a copyable skeleton, incl. what changed before posting
R1g-surface: new props and theme targets are ossification; must solve a class, not a case
R16: one presentation format for every draft — problem, solution, API, breaking, judgement