# Quality gates and exclusion rules

1. Detector precision gate: publish no origin-level result until manual validation reports precision and recall by yield class.
2. Pre-trend gate: event-study leads for months -6 to -2 must not show the post-treatment pattern.
3. Semantic equivalence gate: no-yield and yield lab variants must reach the same final task state.
4. Carryover gate: every interaction scenario must include a second interaction to detect shifted-work harm.
5. Completion marker gate: each lab task must define a task-specific completion marker before data collection.
6. Multiple-comparison gate: primary outcomes are fast_inp, p75_inp, total interaction work, completion time, and carryover input delay.
7. Privacy gate: RUM payloads must not include text input values, user identifiers, full URLs with query strings, or unredacted DOM text.
8. Cost gate: HTTP Archive response_body scans must be date/client filtered and sampled during detector development.