Kordant/tasks/core-services-implementation

Core Services Implementation

Objective: Convert all stub/placeholder services into production-ready implementations with real API integrations, enabling paid customer subscriptions and revenue.

Status legend: [ ] todo, [~] in-progress, [x] done

Tasks

Phase 1 — Foundation (Revenue Enabler)

• 01 — Stripe Checkout, webhooks, and subscription state management → 01-stripe-checkout-webhooks.md
• 02 — Automated removal engine for top 20 data brokers → 02-removebrokers-top-20.md

Phase 2 — Core Services (Table Stakes)

• 03 — HIBP API integration for email breach monitoring → 03-darkwatch-hibp.md
• 04 — SecurityTrails, Censys, Shodan API integrations → 04-darkwatch-attack-surface.md
• 05 — Periodic scan scheduling, WebSocket progress, alert deduplication → 05-darkwatch-scheduler.md
• 06 — Twilio Lookup and phone reputation API integration → 06-spamshield-reputation.md
• 07 — Fine-tuned DistilBERT SMS spam classifier with ONNX deployment → 07-spamshield-ml-classifier.md

Phase 3 — Scale & Expand

• 08 — Expand broker coverage to 50+ with CAPTCHA solving → 08-removebrokers-50-plus.md
• 09 — Attom Data Solutions API for property record snapshots → 09-hometitle-attom-api.md
• 10 — County recorder web scrapers for top 100 US counties → 10-hometitle-county-scrapers.md
• 11 — Azure Voice Live API for synthetic voice detection → 11-voiceprint-azure-api.md

Phase 4 — Differentiation & Polish

• 12 — iOS CallKit and Android Telecom API for real-time call analysis → 12-voiceprint-mobile-integration.md
• 13 — Cross-service threat correlation scoring and unified alert feed → 13-correlation-engine.md
• 14 — Family plan member management, billing proration, multi-user dashboard → 14-family-plans.md

Dependencies

• 02 → 08 (expand broker automation after initial 20 work)
• 03 → 04 (HIBP before attack surface APIs before scheduling)
• 04 → 05 (HIBP before attack surface APIs before scheduling)
• 06 → 07 (reputation APIs before ML classifier)
• 09 → 10 (Attom API before county scraping fallback)
• 11 → 12 (Azure API before mobile integration)
• 01 → 14 (billing before family plan management)
• 05, 07, 08 → 13 (core services feed into correlation engine)

Exit Criteria

• All 5 core services make real API calls or run real ML inference — no stub responses remain in production code
• Billing supports Stripe Checkout, webhooks, tier upgrades/downgrades, and trial periods
• A paying customer can sign up, receive real alerts, and see tangible value within 48 hours
• Mobile apps display real data from all working services
• No crypto.randomUUID(), isSynthetic: false, isSpam: false, or Unknown Owner mock responses in production paths