Mundi QMD — False-Positive Check Integration

Overview

Thin integration pointer layer above tob-fp-check. The base tob skill provides the TRUE/FALSE-POSITIVE verdict protocol; this skill tells you when + how to invoke it in Mundi-specific contexts (Kadenwood CRM bugs, PB/CapIQ data-quality findings, signal hits, outreach bounces) so fixed findings don't retrigger session after session.

The problem this solves: same "issue" gets flagged in 4 consecutive review sessions because no session knows it was already dispositioned.

When to use

• Running /mundi:security-audit — before flagging an issue, check if it was already dispositioned as FP.
• Running /mundi:refusal-test — same pattern; rationalization-to-reject table should include prior FPs.
• Validating intent-signal hits — "this company triggered the signal again" — check if we already decided it wasn't a real signal 30 days ago.
• Bug triage in Kadenwood CRM — email bounce / verification failure recurring → check FP log before opening a ticket.
• PB/CapIQ data-quality reviews — "this field looks wrong" — check if last review already said it's fine.

When NOT to use