brief: n/a escape hatch for unreachable slots, 7d as an early hypothesis, async-source evidence rule, collaborator bucket, doc'd? column
R34: file findings against the cause and size them by outcome; JUDGEMENT reads slot bodies, not labels; a11y defects BLOCK
T4b: theme target names derive as <component-kebab>-<part>; establish frozen-vs-unreleased before asking for a rename
API absorbs USAGE — call site first, then the table, then ossification
API: enumerate as a table — change, public, class, per-row verdict
SOLUTION: a holistic design pass is one decision; behaviour and new API still split out
JUDGEMENT: four verdicts in priority order — comment only when problem/solution/impact are unclear
put the VERDICT line in every slot of the output template, not just the convention note
PERFORMANCE: the evidence a perf block must carry — counts not clocks, both builds one run, multiple N, banked repro
every slot ends in a VERDICT line; JUDGEMENT curates them instead of re-deriving
PERFORMANCE: a measured degradation is request-changes, not a tradeoff note
A11Y & I18N is its own slot, wired to rubric section 1 and section 9
VISUAL EVIDENCE: label every difference intentional or not; intentional cites the PR's problem, Design Conventions or rubric §5
ossification: a new concept is marked [Needs human judgement], not argued
ossification: ask who else has this problem and what they called it
scatter the audit rubric across the template: §3 in API, §2 in THEMING, §1+§9 rendered in VISUAL EVIDENCE, §4+§9 source in BREAKING
API absorbs ossification — answered per enumerated line, not per PR
JUDGEMENT: name which half needs a human — design owner stands in for design, never for API
STEP 5b: grep the siblings before writing a convention finding; R31: merge prose is not a trailer; R32: green CI is not evidence CI ran
R3l: design/API judgement calls have wiki pages; BREAKING gains behaviour, PERFORMANCE gains effects, THEME TARGETS renamed THEMING
VISUAL EVIDENCE absorbs the render matrix — it posts with the review, not as a second comment
kit is the source of truth; every change propagates to this wiki in the same turn
IMPACT: convert the measurement to the experience, or say you could not
IMPACT: always frame it as what a person experiences
IMPACT: say what merging newly exposes, not just who it reaches
STEP 7c2: grep the diff for the fix you are about to ask for; R1e becomes a gate
R1g: changed meaning and wrong mechanism are exceptions too; R30 cites the working sibling
R30: find the interaction decision the findings are children of
STEP 7: the three checks the critic keeps failing; stock spawn prompt
R29: plural problems are fine; unrecorded ones are the failure