Name: Pvl Peleg Review
Author: saidaz24-meet

Peleg Review Task System

FF Data Everywhere: Ask &quot;Should FF data also be shown here?&quot; for every UI element
Aggregation Trust: TANGO aggregation is SECONDARY. Not in dashboard summaries, not as primary chart metrics. OK in peptide detail pages.
User-as-Stupid Principle: Every UI must pass &quot;would a confused first-time user understand this in 3 seconds?&quot;
Repetitiveness Guard: FF data everywhere relevant BUT each view shows it in the way most useful for THAT context

Source Document

docs/active/PELEG_REVIEW_TASKS.md — Read this FIRST for any Peleg-related work.

PLAN MODE FIRST — before touching any code
ASK QUESTIONS — if ANY item is ambiguous, stop and ask. Do not guess intent.
Research before deciding — items marked [DECIDE AFTER RESEARCH] require web search + codebase analysis + user approval
Chunk execution — do ONE chunk per session. Summarize at end.
FF-everywhere check — for EVERY UI element you touch: "Should FF data also be shown here?"

Chunk	Topic	Priority
1	FF Data Layer — new columns, 4 categories, thresholds	Phase 1
2	Threshold Controls — remove old, add smart flagging	Phase 2
3	Terminology & UX — simplify for non-researchers	Phase 3
4	Graphs & Visualizations — delete/replace/add	Phase 4
5	Results Table & Filtering — FF categories in filters	Phase 3
6	Candidate Ranking — deep research + redesign	Phase 5
7	Peptide Detail Page — feature comparison, sliding windows	Phase 6
8	Parked Items — compare 5+ tables, UI redesign, VM/K8s	Later
9	Cross-Cutting Concerns — FF everywhere, agg trust, UX	Always