Repository navigation
[Ops / Security] Double-Lock Risk Flags on Cases & Tutors (V1 Manual) #441
Description
[Ops / Security] Double-Lock Risk Flags on Cases & Tutors (V1 Manual)
Summary
Add manual risk flags so CS can mark and skim suspicious cases or tutors before heads-ups or phone unlock. V1 is visibility + audit only — no auto-block from WhatsApp metadata, no hard hide from Top 8.
Pairs with: triage #438, contact-after-fee #255, fee_marked_paid / matching #428. Desk protocol: MM-OPS-CS-005 V5.3 (CEO: no CS-006).
CEO locks (V1)
| Topic | Lock |
|---|---|
| Detection | Manual only — never auto-set from WABA / display-name APIs |
| Effect | Badges + notes; flags do not auto-delete or auto-archive |
| Shortlist | BLOCKED tutors still appear with 🛑 (so agents don’t re-ping); no hard Top 8 purge yet |
| Authority | Any CS → REVIEW; Operator confirms / sets BLOCKED |
| vs triage | Independent of priority_tier (P2+REVIEW is valid) |
1. Database
cases
risk_flagenum:NONE|REVIEW|BLOCKED(defaultNONE)risk_notetext nullable- Optional:
risk_flagged_at,risk_flagged_by(agent id) if cheap — nice for audit
tutors
risk_flagenum: same (defaultNONE)risk_notetext nullable- Same optional audit columns
2. Admin UI
- Case lists (Active Desk + Hold): badge when
REVIEW(⚠️ ) orBLOCKED(🛑); tooltip / line showsrisk_note. - Tutor shortlist + tutor admin profile: same badges.
- Case + tutor admin: dropdown
risk_flag+ shortrisk_notefield. - Optional V1 filter chip: “Hide BLOCKED” on case list / shortlist (off by default).
3. Explicit non-goals (V1)
- No auto-tag from Business WhatsApp / company display name.
- No automatic block of matching or phone unlock from the flag alone (locks are process in CS-005; paid gate stays Operator
fee_marked_paid). - No Notes Shop escrow changes (that’s [Feature / Notes Shop] Escrow Hold & Anti-Scam (Seller-Funded Refunds) #429/# Issue D7 — Order, receipt, and dispute #269).
Acceptance criteria
- Agents can set
risk_flag+risk_noteon any case and any tutor (BLOCKEDOperator-gated if auth is ready; else document Operator-only SOP). -
REVIEW/BLOCKEDbadges show immediately on case lists and tutor shortlists. - New cases/tutors default to
NONE. - No automated blocking or auto-tagging.
- Flag state is independent of
priority_tier.
Desk protocol (CS-005)
Double-Lock Security Protocol is folded into MM-OPS-CS-005 V5.3 (not a separate CS-006).
Activity
owlstonbusiness-svg commentedon Oct 24, 2026
Broker Overflow #442 routes permanent broker/agency discipline through this issue’s
risk_flag = BLOCKED(Operator-gated) — ghost/collapse → REVIEW; 2nd failure / poaching → BLOCKED.owlstonbusiness-svg commentedon Oct 24, 2026
Cross-link: #442 Overflow discipline (ghost / 2nd failure / poach) → Operator
risk_flag = BLOCKEDhere.owlstonbusiness-svg commentedon Oct 24, 2026
Cross-link: V1 tutor progression #445 — two early L1 drop-offs on New tutors → set tutor
risk_flag=REVIEW(manual).owlstonbusiness-svg commentedon Oct 24, 2026
Admin backboard will surface L1 drop-off count for REVIEW path — #448.
owlstonbusiness-svg commentedon Oct 25, 2026
V1 must-have — marked
urgent(2026-10-25 re-audit)Manual Double-Lock is titled V1 Manual and pairs with triage (#438) + phones-after-fee (#255). Visibility/audit flags before unlock are required for safe V1 desk ops (still no auto-block from WABA).
Merge PR #470: manual risk flags on cases + tutors (#441 V1)