Quality Desk Check-In

Is the Cerberus / grading-desk initiative hooked up, is it catching anything, and what is in the way. Plus a UX fleet's findings on simplifying the desk.

2026-08-26 Β· data pulled live from production Β· UX review: 6 lenses, 39 findings adversarially verified, 31 survived Β· Trello: Grading desk stops fighting the grader

Scorecard

577
machine grades in the last 7 days (5 judges, latest ~1 h ago)
85
red flags on file β€” real Clara failures
34
human grades by a real person (all Fede). 159 are the golden import, 2 smoke.
16 / 187
human grades usable by the test pipeline
2
permanent regression tests landed from πŸ‘Ž
3
golden-set tests stuck on a merge permission

Is it hooked up and live?

PieceStateDetail
Machine judges (rubric, topic sweep, policy gate, fair-housing, trajectory, daily reviewer)LIVE666 grades on file; ~80/day. Running today.
Human grading deskLIVEOne real user. Team has not graded a single item.
πŸ‘Ž / πŸ‘ β†’ regression test (nightly)LIVE Β· ARMEDArmed 2026-08-23. Runs every morning, clean. 2 tests landed.
Auto-merge of drafted testsBLOCKEDThe merge robot can't see that checks passed (token lacks Checks:Read). 3 green PRs unmerged since 08-24. 30-second fix, Fede's side.
Cerberus in front of live outgoing messagesNOT WIREDIt only runs as a test suite in CI. It has never checked a real message before Clara sent it.
Golden-set raw judgmentsHALF59/152 matched to real conversations and shown on the desk. The reasoning text itself is read by nothing.
Promoted principle β†’ Clara's prompt (with eval receipt)SHIPPEDLanded 2026-08-26.
Overall quality roll-upMISSINGNo view adds the grades up. The desk is one-at-a-time only.

What it has caught

The 85 red machine grades, grouped. These are the failure classes the product vision worries about most: unbacked promises and dropped loops.

PatternCountReal example from production
Clara claims she did something the tools never did24"I've got the work order in" β€” no work order was created. On a call, promised to text a tenant the handyman's timing β€” no text was sent.
Escalation promised, never handled14Promised the leasing team would follow up on lease dates, move-in special, parking, buzz code β€” none came back to the resident.
Lead dead-ended11Thread trails off after the resident's last question; no resolution.
Wrong topic label (bookkeeping)17Nightly sweep relabeled resident_inquiry β†’ leasing.
Invented fact6β€”
One-offs1 eachMissing emergency safety instructions; "closed Sunday" repeated three times; prospect had to ask "what time is my tour?" twice.

Human πŸ‘Žs: 178 of 195 verdicts are thumbs-down; only 12 pin a specific message. Why the promise failures keep happening β€” and the one design that fixes the class β€” is in Clara's promises: the systematic pattern.

Going well Β· Gaps

Going well

Gaps

KPIs the desk should show

All computable from data already stored.

UX fleet: how to simplify the desk

Six reviewers (hierarchy, flow, attribution, layout, consistency, copy), each finding then attacked by a skeptic against the actual code. 31 of 39 survived. Ranked by impact.

ChangeEffortImpactWhat changes
Show who graded (initials), not a green checkMhighInitials next to the row: FC / teammate / a distinct "golden import" mark. Grader identity is already stored β€” pure UI.
Right-click = doneMhighπŸ‘ records instantly. πŸ‘Ž shows principle chips inline in the popover; tapping a chip submits. "Record verdict" only for the long form.
Kill the mobile sheet on desktopMhighRight-click πŸ‘Ž on desktop currently slides a phone-style bottom sheet with a second copy of the form over the form already on screen. Route to the visible panel instead. This is the "jarring, mobile-optimized" feeling.
Required field first, optional collapsedMhighPrinciple chips ("pick at least one") right under the thumbs; failure-kind and "what she should have done" tucked into "More detail (optional)".
Delete "What Clara said (quote)"ShighThe pipeline already takes the quote from the pinned message (standing decision 08-23). The box asks graders to redo it by hand.
Delete "inference, not verified"SmedZero readers anywhere in the pipeline.
Fix "What kind of failure?"SmedOnly 3 options exist; stack them full-width so they stop reading as truncated. Widen the panel on large monitors (hard-capped at 320px today).
Fix "You disagreed"SmedIt fires on any grader's disagreement, so it can be false. Say "you said πŸ‘Ž Β· machine said 🟒" when it was you; neutral label otherwise.
Quiet the chip noiseSlowMove "Β· new" (means unvetted, not recent) into the tooltip; collapse the add-a-chip box behind a "+".

Also on the card (found in review, not by the fleet)

Decisions

Proposed β€” pending Fede's review. Each with a recommendation.

D1. Should Cerberus check real messages before Clara sends them?

A (recommended) β€” Shadow mode first: run it on every outgoing draft, log what it would have blocked, block nothing. Two weeks of data, then decide on blocking. Zero customer risk, real numbers.
B β€” Block immediately on the two highest-confidence checks (unbacked "I did X" claims, leaked internal reasoning). Faster protection, some risk of holding good messages.
C β€” Keep it CI-only. It stays a regression net, never a live guard.

D2. "You disagreed" badge

A (recommended) β€” Show "you said πŸ‘ Β· machine said πŸ”΄" only when it was really this grader; otherwise a neutral "Disagreement on file". Keeps the shared queue ranking identical for every viewer.
B β€” Just rename it "Needs another look" for everyone. Cheapest.
C β€” Personalize the whole queue per viewer. Reverses a documented invariant; bigger change.

D3. Initials: ship now or wait for full names?

A (recommended) β€” Ship "you / golden import / someone else" now; teammate initials as a fast follow once the name lookup is in the feed.
B β€” Wait until teammate names resolve end to end.

D4. Widening the desktop panel

A (recommended) β€” Add a wider large-monitor breakpoint on top of the existing laptop one. A previous attempt to edit the laptop values pushed the panel off-screen at 1024px.
B β€” Layout-only: stack the 3 failure buttons, leave the 320px cap.

D5. Collapse the "add a new principle" box?

A (recommended) β€” Behind a "+ New principle" click, auto-focused. One extra click to mint; removes a full-width control from every item.
B β€” Leave it visible; only fix the "Β· new" wording.

Rejected by the skeptics (for the record)

History

Decision record: ADR-0128. 35 commits Aug 11–26. Related docs: grading-playground-design, grading-annotation-guide, grading-desk-qa-2026-08-19, golden-dataset-practices, quality-loop-guide, cerebrus-burnin. Build sessions: Aug 11 (phases 0–1b), Aug 17 (main build), Aug 22 (right-click, failure classifier, blinding), Aug 24 (πŸ‘Žβ†’test pipeline).

PropFlow Docs