//OPERATIONS
Inspectable operations, at portfolio scale.
Every number below is read live from the same PostgreSQL tables the pipeline writes to while processing requests. Small numbers are expected: this is a portfolio sandbox, not a production tenant with thousands of leads per day. The point is to make latency, spend, retries, and stuck work inspectable.
The snapshot includes the seeded 60-case evaluation run and guided demo replays; it is not customer traffic.
//OPERATING SIGNALS
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
- completed 66 (100%)
Leads by qualification band
- Sales-ready 19 (29%)
- Needs review 15 (23%)
- Insufficient evidence 13 (20%)
- Disqualified 11 (17%)
- Nurture 8 (12%)
Identity resolution outcomes
- New (no match) 59 (89%)
- Confident match 6 (9%)
- Possible match 1 (2%)
Outreach draft decisions
- pending_review 40 (95%)
- approved 2 (5%)
//LATENCY PER STAGE (real, from audit_events)
| Stage | Runs | Avg duration |
|---|---|---|
| draft_outreach | 42 | 2.48s |
| extract_facts | 46 | 2.13s |
| verify_facts | 46 | 1.51s |
| classify_message | 66 | 1.48s |
| check_draft_claims | 42 | 1.04s |
| identity_resolution | 66 | 1ms |
| find_research_source | 58 | 1ms |
| qualify | 66 | 1ms |
| propose_crm_change_set | 66 | 1ms |
Scope note
This is the v1 scope: 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 as design, not built — an honest cut line, not a silent shortfall.