MAGPIE // EVIDENCE INTELLIGENCE

MAGPIE // INCIDENT ROOM

INC_001

EXTRACTION DRIFTRESOLVED

source_support_platforms · collector c_mt4m8fix1gze0scg44

THE FAILURE MODE

RUN SUCCEEDED. JSON VALID.
BUSINESS CONCLUSION WRONG.

The page redesigned: the top three vendors moved into a JavaScript featured carousel and their evidence behind expandable panels. The collector still succeeded and returned schema-valid JSON — but only seven of ten vendors. A naive product would report: NimbusDesk disappeared from the top three of Enterprise Support Platforms 2026.

Latest run quarantined

The collector returned ranks 4–10 while the last trusted observation contained ranks 1–10. Publishing this run could falsely report a source-evidence loss. The last trusted snapshot kept powering the dashboard while the collector was reviewed.

TRUSTED BASELINEPUBLISHED

10 /10

j_mt4mskyc7o888bkba · facts 832c8a89901d…

  • #01 AtlasSupport
  • #02 NimbusDesk
  • #03 HelioSupport
  • #04 ResolveHub
  • #05 TicketForge
  • #06 CaseCraft
  • #07 ZenQueue
  • #08 OrbitDesk
  • #09 HelixDesk
  • #10 SupportLoop

QUARANTINED RUNBLOCKED

7 /10

j_mt4qvbykzs0z36ag6 · schema-valid

  • #04 ResolveHub
  • #05 TicketForge
  • #06 CaseCraft
  • #07 ZenQueue
  • #08 OrbitDesk
  • #09 HelixDesk
  • #10 SupportLoop

RECOVEREDPUBLISHED

10 /10

j_mt4s453e2aktj9woky · facts 832c8a89901d…

  • #01 AtlasSupport
  • #02 NimbusDesk
  • #03 HelioSupport
  • #04 ResolveHub
  • #05 TicketForge
  • #06 CaseCraft
  • #07 ZenQueue
  • #08 OrbitDesk
  • #09 HelixDesk
  • #10 SupportLoop

FAILED CHECKS — DETERMINISTIC, NO LLM

record_countexpected 10 · observed 7

Record count 7 below hard minimum 10 (ratio 70%).

rank_startexpected 1 · observed 4

Ordered source begins at rank 4 instead of 1.

missing_ranksexpected 0 · observed 1, 2, 3

Ranks missing from the expected sequence: 1, 2, 3.

structural validation: PASS — the lie was schema-valid

POST-HEAL VERIFICATION GATE

collector_idunchanged ✓
app contract (SourceEvidenceRowV1)unchanged ✓
business_facts_hashidentical ✓
rows restored7 → 10 ✓
downstream app changes0
human approvalrecorded ✓

HEALING TIMELINE — BRIGHT DATA SELF-HEALING, HUMAN-GATED

  1. 1OPEN — semantic failure detected
  2. 2DIAGNOSING — page inspection confirms extraction drift
  3. 3READY_TO_HEAL — repair prompt generated
  4. 4HEALING — coding agent runs bdata scraper heal
  5. 5AWAITING_APPROVAL — human reviews the proposed diff
  6. 6APPLYING_REPAIR — approved, auto-saved to production
  7. 7VERIFYING — same Collector ID rerun against the changed page
  8. 8RESOLVED — contract verified, data released downstream