---
name: L5 Instance Dossier - mql-enrichment-service / sdr-handoff-helper
description: SDR-side copilot inside {{crm_name}}. Surfaces enrichment context inline when an SDR opens a lead. Currently in 30% canary; full rollout planned 2026-05-15 contingent on canary metrics.
type: layer-artifact
layer: L5
populated_from: Q7, Q1, inheritance from L0-L4
Owner: RevOps-AI eng team; eng pair {{eng_member_3}} + {{eng_member_4}}
---

# L5 Instance Dossier - mql-enrichment-service / sdr-handoff-helper

- **Last reviewed:** 2026-04-25
- **Review cadence:** quarterly + on every L4 kit version bump + on every canary expansion
- **Status:** active (canary 30%)

## Maturity self-assessment

| Aspect | State | Evidence |
|--------|-------|----------|
| Purpose articulated | mature | Single-sentence purpose; SDR-facing context surfacing |
| Owner named and reachable | mature | Engineering pair; rotated weekly |
| Kit components consumed declared | mature | Five components below |
| L3 contract conformance verified | mature | Eval pass on canary cohort; auth verified |
| Eval baseline established | mature | 200-example SDR-context-relevance eval; 0.91 pass rate (above 0.85 ship threshold for canary phase) |
| L6 refinement concerns named | partial | One concern: tier-3 enrichment placeholder visible during deep-context fetch; cosmetic; logged |
| Production deployment status | partial | Canary 30%; full rollout closes-by 2026-05-15 |

## Identity

- **Platform name:** `sdr-handoff-helper`
- **Purpose:** surfaces enriched MQL context inline when an SDR opens a lead in {{crm_name}}; produces a 3-line summary plus the top three intent signals plus any consent caveats
- **Type:** `copilot`
- **Production status:** `canary` at 30% of SDRs; full rollout target 2026-05-15

## Ownership

- **Owner:** RevOps-AI eng team
- **Oncall rotation:** PagerDuty `revops-ai` (canary alerts route to engineering pair before oncall)
- **Escalation:** RevOps-AI eng lead -> {{exec_vp_revops}}; SDR-side feedback channels through SDR Team Lead
- **Documentation owner:** RevOps-AI eng lead

## Kit components consumed

| Component | Path | Version pin | Mirror status |
|-----------|------|-------------|---------------|
| Prompt | kit/prompts/sdr-context-summary.md | hash from sync-2026-04-12 | live |
| Eval harness | kit/eval-harness/ | sync-2026-04-12 | live |
| Guardrail runtime | kit/guardrails/ | sync-2026-04-12 | live |
| Telemetry plumbing | kit/telemetry/ | sync-2026-04-12 | live |
| L3 contract | kit/contracts/enrichment-record-schema.json | 3.1.0 | live (consumed; not modified) |

## L3 contract conformance

- **Eval score (latest run, 2026-04-12):** SDR-context-relevance 0.91, citation-correctness 0.96, no-leak (PII / competitor) 1.00
- **Eval ship threshold met:** yes (canary phase thresholds met; full-rollout thresholds same)
- **Per-call cost p90:** $0.034 (well under ceiling)
- **Cost ceiling met:** yes
- **Telemetry schema emitted:** complete
- **Auth model implemented:** yes; tenant-scoped JWT plus SDR identity propagated

No findings against the L3 contract.

## Canary metrics (live)

- **Cohort size:** 14 SDRs (30% of 45)
- **Sessions:** 312 lead-opens with helper visible (last 14 days)
- **SDR-explicit feedback:** 89% positive (thumbs-up vs. thumbs-down on the helper card)
- **SDR-implicit signal:** 67% expand-to-tier-3 rate when tier-3 enrichment is available (indicates utility)
- **Disengagement:** 2 SDRs opted out of canary (one cited too-noisy, one cited tier-3 latency)
- **Closes-by 2026-05-15:** if canary metrics hold, full rollout proceeds

## L6 Per-instance refinement

- **Latency observed:** p50 220ms (tier-1+2 summary); p95 480ms; p99 1.4s when tier-3 deep-context renders inline
- **Latency target:** p99 under 1.5s for inline render (held)
- **UX integration points:** {{crm_name}} lead-detail page; helper card top-of-fold; consent caveat shown if `consent_check_result: revoked`
- **Voice tuning notes:**
  - 3-line summary opens with the lede (per L2 response-shape conventions transferred to user-facing voice; this is the only L5 with a voice surface)
  - Tier-3 deep-context section uses bullet points; never paragraphs
  - Decline copy: "Cannot summarize with confidence; here are the gaps."
- **Known sharp edges:**
  - Tier-3 enrichment placeholder visible during deep-context fetch (~600ms typical); cosmetic; planned mitigation: skeleton-loader pattern

## Concurrent-actor notes

- **Expected concurrent operators:** 2 RevOps-AI engineers (pair)
- **Lock-on-write boundaries:** `kit/prompts/sdr-context-summary.md` (during prompt revision); SDR-feedback inbox during drain
- **Session log location:** `sessions/` at instance root

## Recent session activity

- 2026-04-25 - Canary metrics review; expansion to 30% from 15% approved
- 2026-04-22 - Consent-flow incident drill; helper card correctly suppressed enrichment for revoked-consent leads
- 2026-04-08 - Initial canary deploy

## Open ADRs and findings

- Canary expansion to 100% scheduled 2026-05-15; gating on metric hold
- Tier-3 placeholder cosmetic; tracked in BACKLOG (low priority)

## L1 activation note

This is the only L5 with a user-facing voice surface (SDRs read the 3-line summary). L1 brand posture remains N/A-explicit at the instance level because the audience is internal (SDRs at {{cutting_edge_saas_company}}, not external customers); but the response-shape conventions from L2 transfer here as voice rules. If `sdr-handoff-helper` ever exposes summaries to customers (e.g., a customer-facing "your lead score" view), L1 must activate at the instance level.

## Inheritance and dependencies

This L5 inherits from: L0 strategy, L1 (N/A at instance level; voice rules from L2 apply here), L2 philosophy, L3 framework contract, L4 platform kit.

L7 cross-platform participation:

- Shared memory: reads enriched records from `revops.mql_facts`
- Shared identity: validates tenant-scoped JWT plus SDR identity
- Handoff protocol: receives assignment envelope from mql-router; produces no downstream envelope (terminal in chain)
- Consent flow: reads `consent_check_result` from enrichment record; suppresses helper card for revoked-consent leads
- Alerting fabric: emits SDR-feedback alerts (thumbs-down patterns)
- Monitoring base: dashboard panels in `revops-mql-pipeline-001` plus a canary-specific panel

## Cross-references inside this instance

- `OPERATING-MODEL.md`
- `policies/philosophy.md` (L2) - response-shape conventions transfer here
- `policies/framework-contract.md` (L3)
- `kit/PLATFORM-KIT.md` (L4)
- `cross-platform/handoff-protocol.md`
- `cross-platform/consent-flow.md`
- `runbooks/sdr-handoff-helper-incident.md`
