---
name: L5 Instance Dossier - mql-enrichment-service / mql-enrichment-service
description: Core enrichment platform. Reads inbound MQLs, enriches with firmographic and intent signals, persists structured records to revops.mql_facts. Production live.
type: layer-artifact
layer: L5
populated_from: Q7, Q1, inheritance from L0-L4
Owner: RevOps-AI eng team; eng lead {{eng_lead_name}}
---

# L5 Instance Dossier - mql-enrichment-service / mql-enrichment-service

- **Last reviewed:** 2026-04-22
- **Review cadence:** quarterly + on every L4 kit version bump
- **Status:** active

## Maturity self-assessment

| Aspect | State | Evidence |
|--------|-------|----------|
| Purpose articulated | mature | Single-sentence purpose; consistent across L0 strategy and OPERATING-MODEL |
| Owner named and reachable | mature | RevOps-AI eng team; oncall via PagerDuty `revops-ai` schedule |
| Kit components consumed declared | mature | Five components listed below; all with version pin and mirror status |
| L3 contract conformance verified | mature | Eval pass 2026-04-12; cost p90 $0.052 under ceiling; auth verified 2026-04-19 |
| Eval baseline established | mature | 800-example dataset; quarterly refresh; latest run 2026-04-12 |
| L6 refinement concerns named | mature | Three named below; all in acceptable state |
| Production deployment status | mature | Live in production since 2025-11-08; no incidents in last 90 days |

## Identity

- **Platform name:** `mql-enrichment-service`
- **Purpose:** core enrichment service; reads inbound MQLs from `enrichment-queue-{tenant_id}`, enriches with firmographic and intent signals, writes enriched records to `revops.mql_facts`
- **Type:** `automation`
- **Production status:** `live` since 2025-11-08

## Ownership

- **Owner:** RevOps-AI eng team
- **Oncall rotation:** PagerDuty schedule `revops-ai`; primary + secondary
- **Escalation:** RevOps-AI eng lead -> {{exec_vp_revops}}
- **Documentation owner:** RevOps-AI eng lead

## Kit components consumed

| Component | Path | Version pin | Mirror status |
|-----------|------|-------------|---------------|
| Prompt | kit/prompts/enrichment-tier-{1,2,3}.md | composite hash; see kit/prompts/MANIFEST.md | 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 (locally owned, not mirrored) |

Mirror status `live` is verified: telemetry from production calls matches the schema defined in the L3 contract; cross-checked daily by post-hoc guardrail.

## L3 contract conformance

- **Eval score (latest run, 2026-04-12):** faithfulness 0.94, fluency 0.89, human-pass 0.97
- **Eval ship threshold met:** yes (all three thresholds cleared)
- **Per-call cost p90:** $0.052 (well under $0.08 ceiling)
- **Cost ceiling met:** yes
- **Telemetry schema emitted:** complete; verified via post-hoc guardrail daily sample
- **Auth model implemented:** yes; tenant-scoped JWT verified 2026-04-19 in cross-tenant isolation drill

No findings against the L3 contract as of last audit.

## L6 Per-instance refinement

Polish concerns specific to this platform:

- **Latency observed:** p50 380ms, p95 850ms, p99 1.2s
- **Latency target:** p99 under 1.5s (held)
- **UX integration points:** N/A (programmatic only); writes to warehouse; consumed by mql-router
- **Voice tuning notes:** N/A (internal-platform; no user-facing voice)
- **Known sharp edges:**
  - Tier-3 deep-context enrichment is slower (p99 1.1s vs. tier-1 p99 320ms); SDR-handoff-helper sometimes shows tier-2 placeholder while tier-3 completes
  - Cold-start on warehouse-lookup tool adds ~150ms after pod restart; mitigated by warm pool

## Concurrent-actor notes

- **Expected concurrent operators:** 2-3 RevOps-AI engineers + occasional Platform Engineering pairing
- **Lock-on-write boundaries:** `kit/prompts/` (during prompt revision); `kit/contracts/enrichment-record-schema.json` (during schema bump)
- **Session log location:** `sessions/` at instance root (this platform is the namesake; not a sub-platform)

## Recent session activity

- 2026-04-22 - Consent-flow incident response; resolved; runbook updated
- 2026-04-15 - Quarterly maturity review; full audit ran clean

## Open ADRs and findings

- L4 mirror sync 14 days behind source; resolution closes-by 2026-05-05; tracked in BACKLOG and OPERATING-MODEL highest-leverage section
- No open ADRs proposing new decisions

## Inheritance and dependencies

This L5 inherits from: L0 strategy, L1 (N/A-explicit), L2 philosophy, L3 framework contract, L4 platform kit (mature-internal-mirror).

L7 cross-platform participation:

- Shared memory: writes to `revops.mql_facts`; canonical state owner for enrichment fields
- Shared identity: validates tenant-scoped JWT on every inbound call
- Handoff protocol: emits the structured envelope downstream to `mql-router`
- Consent flow: synchronous check before any enrichment (Red Line 1)
- Alerting fabric: emits guardrail trips and cost-ceiling breaches
- Monitoring base: dashboard panels in `revops-mql-pipeline-001`

## Cross-references inside this instance

- `OPERATING-MODEL.md`
- `policies/strategy.md` (L0)
- `policies/philosophy.md` (L2)
- `policies/framework-contract.md` (L3)
- `kit/PLATFORM-KIT.md` (L4)
- `cross-platform/` (L7) - all six concerns
- `decisions/` - all three ADRs apply to this platform
- `runbooks/mql-enrichment-incident.md`
