Grade every takedown design and decide which ADRs the critic reads #970
Labels
No labels
P0
P1
P2
P3
bug
category/code-change
category/cross-repo
category/eval-run
category/investigation
category/no-test-target
category/owner-ruling
category/prose-artifact
category/recurring-chore
category/structure
category/umbrella
crc-refactor
create
delete
enhancement
filed-by/agent
filed-by/user
frozen
lint-rule
needs-info
needs-triage
next
plugin/cc-architect
plugin/os
plugin/os-adr
plugin/os-aidd-lint
plugin/os-backlog
plugin/os-context
plugin/os-doc-hygiene
plugin/os-sdlc
plugin/os-vault
project/cc-os
ready-for-agent
ready-for-human
recurring
review
rule-proposal
update
waiting
wayfinder:grilling
wayfinder:map
wayfinder:map
wayfinder:research
wayfinder:task
wayfinder:task
wontfix
worklist/deviations
worklist/lint-rule
worklist/new-implement-build
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
jared/cc-os#970
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Problem
The takedown pipeline grades only the final design. So the grade drop between a blind design and an ADR-constrained design is not a number. The critic also reads the ADRs of the case base-commit snapshot. The snapshot for case 650 (base
1280b01d) has no ADR-0279. So the critic'sadr_causeswas empty on a design that crosses a plugin boundary.Observed
Run 650-20261008-112340 scored far_superior (4). Its design shares one plugin's class across the boundary, which ADR-0279 decision 4 forbids. No ADR text in the snapshot could flag it.
Reproduce
n/a: design ticket. See docs/handoffs/2026-10-08-takedown-autoresearch.md, section "ADR-blind designer built and rerun".
Approach
Grade every design the pipeline produces (ADR-0281 decision 4), not only the final one. Decide whether the critic reads ADRs from the current tree instead of the case snapshot. The decision needs an ADR if it reverses ADR-0281.
Origin
VERDICT: CREATE
Skeptic DROP verdicts for related items, folded here for the owner. (1) ADR-blindness gaps: DenySettings writes Grep/Glob deny rules the claude CLI ignores (the Read rule in
3d78ceaealready hides all three, so only cleanup); ticket text can name ADRs and reaches blind roles; map-researcher path still sees ADRs. (2) Numeric pass bar for ticket-takedown before it leaves EXPERIMENTAL: depends on the grading and ADR-visibility decisions here. (3) Owner rulings pending (kept in docs/handoffs/2026-10-08-takedown-autoresearch.md): #823 held-out reference File.exist? guard; 7 training cases still confirmed: false; may tickets carry design constraints (ADR-0209/0190/0255); 803 candidate lens tactic 'a dead optional argument stays after its last caller goes'; may a lens case cite a held-out or training eval ticket (Case 11 now uses invented names,fbbb708a). (4) Reword of cases/650 shipped.md files was done inline, not ticketed.Related: #974 turns on the grader in live takedown runs (cause = researcher cause, baseline = ticket approach), per owner rulings 5 and 6 in docs/handoffs/2026-10-09-takedown-implement-path.md. This ticket stays scoped to per-design grading in the eval and the critic ADR source.
The grade-every-design half moved to #974 under ADR-0285 (Jared ruled option C on 2026-10-10). The ADR-source half stays on #970.