---
name: Localization answers - mql-enrichment-service
description: Captured answers to the 10 localization questions for the mql-enrichment-service worked example. Drives every layer artifact and ADR in this instance. Anonymized via {{token}} placeholders.
type: instance-record
---

# Localization Answers - mql-enrichment-service

- **Captured:** 2026-04-08
- **Captured by:** deploy skill v0 on behalf of {{exec_vp_revops}}
- **Status:** captured

## Q1. Function identity

- **Name:** `mql-enrichment-service`
- **Purpose:** Enriches inbound MQLs from {{cutting_edge_saas_company}}'s paid acquisition channels with firmographic and intent signals before routing to the SDR queue.
- **Type:** `internal-platform`

## Q2. Sponsor and success metric

- **Sponsor:** VP of Revenue Operations, {{exec_vp_revops}} ({{cutting_edge_saas_company}} executive team)
- **Funding source:** RevOps operating budget; FY26 line item RevOps-AI-001 ($420K annualized)
- **Primary success metric:** SDR-accepted-MQL rate from enriched leads at >= 42% (vs. 27% baseline pre-enrichment)
- **Tiebreak rule:** if SDR-accepted rate ties two consecutive quarters, optimize for time-to-first-touch reduction (target: under 4 business hours)

## Q3. Customer, disclosure, and voice

- **Customer segment:** SDRs at {{cutting_edge_saas_company}} (~45 reps across NA, EMEA, APAC); secondary consumer is the `mql-router` automation
- **Disclosure posture:** `n/a-internal` - internal function; no external surface
- **Tone:** N/A (no user-facing voice; emits structured records, not prose)

## Q4. Red lines and human-in-loop

- **Red lines:**
  1. Never enriches an MQL with data from sources where consent is missing or revoked
  2. Never overwrites an SDR's manual qualification edit (SDR edits are authoritative)
  3. Never produces a confidence score on data older than 90 days without flagging the staleness explicitly
- **PII rule:** `pii-tenant-only`
- **Human-in-loop placement:** `sample-review` at 5%, plus SDR-side manual override on every individual MQL

## Q5. Framework contract

- **Eval methodology:** `hybrid` - LLM-judge on 800-example curated dataset for enrichment-correctness + 10% human review per quarter
- **Per-call cost ceiling:** $0.08 per MQL enriched
- **Telemetry minimum:** reproducibility quadruple (model_version, prompt_version, tools_version, data_snapshot_version) + tenant_id + cost_estimate_usd + enrichment_source_per_field + consent_check_result
- **Auth model:** `tenant-scoped-jwt` issued by {{idp_name}}

## Q6. Platform kit posture

- **Posture:** `mature-internal-mirror`
- **Source path:** `{{platform_team_name}}/ai-kit/` (the central platform team's kit)
- **Mirror direction:** {{platform_team_name}}/ai-kit -> mql-enrichment-service/kit (one-way; no push back)

## Q7. Instances in scope

Three L5 platforms:

1. `mql-enrichment-service` - core enrichment platform; produces enriched MQL records
2. `mql-router` - downstream routing automation; consumes enriched MQLs and assigns to SDR queues by territory + intent score
3. `sdr-handoff-helper` - SDR-side copilot inside {{crm_name}}; surfaces enrichment context inline when SDR opens a lead

## Q8. Cross-platform glue

- **Shared memory:** `exists-mature` - {{warehouse_name}} schema `revops.mql_facts` is canonical state across all three platforms; owner: RevOps Data team
- **Shared identity:** `exists-mature` - tenant-scoped JWT from {{idp_name}} validated by every platform; owner: Platform Engineering
- **Handoff protocol:** `exists-mature` - structured envelope between mql-enrichment-service -> mql-router -> sdr-handoff-helper; owner: this RevOps-AI team
- **Consent flow:** `exists-mature` - synchronous check against `consent-service` API with 5-minute cache TTL; owner: Compliance Engineering
- **Alerting fabric:** `exists-mature` - {{alerting_destination}} routing per `cross-platform/alerting-fabric.md`; owner: RevOps-Ops oncall
- **Monitoring base:** `exists-mature` - {{observability_platform}} board id `revops-mql-pipeline-001`; owner: RevOps-Ops

## Q9. Compliance and tooling stack

- **Regulatory regimes:** GDPR (EU customer data), SOC 2 (vendor audit obligation)
- **Cloud:** AWS (us-east-1 primary, eu-west-1 for EU tenants)
- **Observability:** {{observability_platform}}
- **Serving infrastructure:** Kubernetes (EKS) for stateful enrichment service; Lambda for downstream routing
- **Ticketing / comms:** Linear (engineering tickets), Slack (cross-team), Confluence (long-form docs)

## Q10. Governance shape

- **Instance root:** `revops-ai/mql-enrichment-service/` (in the `{{cutting_edge_saas_company}}-revops` Git monorepo)
- **ADR location:** `revops-ai/mql-enrichment-service/decisions/ADR-NNNN-{title}.md` (kit default)
- **Frontmatter conventions:** kit default (Last reviewed, Review cadence, Status); RevOps adds `Owner` field on every artifact
- **Concurrent-actor count:** ~4 sustained (RevOps-AI eng team) + occasional pairing with Platform Engineering (~1 weekly) + ad-hoc Compliance reviews. Treat as 5-6 expected.
- **IP boundary:** standard {{cutting_edge_saas_company}} engineering policies; no special restrictions; competitor-product references prohibited per L2 red line

## Revision log

| Date | Question | Old answer | New answer | Reason | ADR? |
|------|---------|-----------|-----------|--------|------|
| 2026-04-08 | (initial capture) | - | (above) | Deploy run | no - locked at landing |
