The Claude Opus diagnostic project is the intelligence core of OutreachIQ. A dedicated Anthropic project with six documents uploaded as persistent context and a system prompt defining Claude's entire operating procedure.
| Document | Purpose |
|---|---|
| ANR ICP Document | Defines ideal client profile — company size, revenue range, geographies, industries, decision maker titles, distress signals, and bad lead signals |
| ANR Services Master Document | Every ANR service, what it builds, for whom, and what business impact it delivers. Every recommendation must map here |
| Diagnostic Output Schema | Exact JSON structure including all verified contact fields. Field names, data types, required vs optional, string escaping rules |
| Severity Scoring Rubric | Criteria for classifying findings as Critical, High, or Medium. Applied consistently across every diagnostic |
| Report Page Structure | Fields that populate the Cloudflare Pages report. Claude writes knowing bait_finding appears unblurred |
| Meridian Software Group Report | Quality benchmark. Every diagnostic must meet or exceed this standard of specificity |
Step 0 — ICP Validation (added after the Norway incident)
Before browsing anything, Claude validates:
If ICP validation fails, Claude flags it immediately and asks whether to proceed or skip. This step was added after Claude spent twenty minutes producing a full diagnostic for Ish Studio — a Norwegian web agency that Groq had classified as a US Healthcare company at 90/100 ICP score.
Step 1 — Read the Brief
Claude reads the Groq enrichment brief but treats it as a hypothesis to verify, not a fact to accept. Notes every field that looks suspicious before proceeding.
Step 2 — Contact Verification (promoted to mandatory full step after the Caplin & Drysdale incident)
Before browsing for findings, Claude: