fp-pattern-finder-signals
When to use
- •You want to reduce FP rate and need concrete, data-driven tuning ideas.
- •You have new labels (manual or outcome backfill) and want to mine for patterns.
Inputs
- •days window and thresholds for pattern detection.
- •output paths for patterns JSON and proposal YAML.
Workflow
- •
- •Ensure labels exist: run outcome backfill and/or manual labeling.
- •
- •Detect patterns:
python -m ops.cli quality find-patterns --days 30 --out /tmp/patterns.json.
- •Detect patterns:
- •
- •Generate tuning proposal:
python -m ops.cli quality propose-tuning --patterns /tmp/patterns.json --out /tmp/proposal.yaml.
- •Generate tuning proposal:
- •
- •Review proposal notes + actions, then (optionally) apply safe patches with
quality apply-tuning.
- •Review proposal notes + actions, then (optionally) apply safe patches with
Outputs
- •patterns JSON report + tuning proposal YAML.
Guardrails
- •Do not auto-apply tuning without review; most actions are suggestions, not deterministic fixes.
- •Validate impact with
quality statsafter deploying changes.
References
- •
references/reference.md - •
docs/QUALITY_OPS_ARCHITECTURE.md