//OPERATIONS
Live, not staged.
Every number below is read live from the same Postgres tables the pipeline writes to while processing real requests — nothing on this page is mocked or hand-entered. Small numbers are expected: this is a portfolio demo, not a production tenant with thousands of leads/day.
//ALERTS
No stuck workflows
All leads resolved within the 2-minute expected-duration window.
No duplicate writes prevented recently
No replay/duplicate-key collisions in the last 24 hours.
Unsupported-fact rate 0.0% — within target
0/42 drafts had an unsupported claim (target: below 2%).
//BREAKDOWN
Leads by status
- completed66 (100%)
Leads by qualification band
- Sales-ready19 (29%)
- Disqualified16 (24%)
- Needs review13 (20%)
- Nurture10 (15%)
- Insufficient evidence8 (12%)
Identity resolution outcomes
- New (no match)58 (88%)
- Confident match6 (9%)
- Possible match2 (3%)
Outreach draft decisions
- pending_review42 (100%)
//LATENCY PER STAGE (real, from audit_events)
| Stage | Runs | Avg duration |
|---|---|---|
| draft_outreach | 42 | 2.86s |
| extract_facts | 42 | 2.31s |
| verify_facts | 42 | 1.78s |
| classify_message | 66 | 1.72s |
| check_draft_claims | 42 | 1.37s |
| identity_resolution | 66 | 362ms |
| find_research_source | 53 | 158ms |
| propose_crm_change_set | 66 | 155ms |
| qualify | 66 | 150ms |
Scope note
This is the v1 scope from CLAUDE.md section 15: real audit-event data plus 3 alerts (stuck workflows, duplicate-write prevention, unsupported-fact rate). CRM API error tracking, qualification drift over time, and operational controls (pause outbound, replay dead-lettered workflows) are documented in the spec as design, not built — an honest cut line, not a silent shortfall.