---
name: Operating Model - mql-enrichment-service
description: Root summary of the mql-enrichment-service deployment at {{cutting_edge_saas_company}}. The first document any fresh operator reads. Summarizes maturity across all eight layers, lists the three L5 platforms, names active ADRs, and points to next moves.
type: root-summary
Owner: {{exec_vp_revops}} sponsoring, RevOps-AI engineering team operating
---

# Operating Model - mql-enrichment-service

- **Last reviewed:** 2026-04-26
- **Review cadence:** quarterly + on material maturity change
- **Status:** active

## What this instance is

`mql-enrichment-service` is `internal-platform`. It enriches inbound MQLs from {{cutting_edge_saas_company}}'s paid acquisition channels with firmographic and intent signals before routing to the SDR queue.

Sponsor: VP of Revenue Operations, {{exec_vp_revops}}. Primary success metric: SDR-accepted-MQL rate from enriched leads at >= 42% (vs. 27% baseline pre-enrichment).

This document is the root summary. Every other artifact in this instance is one layer below this one.

## Maturity at a glance

| Layer | State | One-line gap |
|-------|-------|--------------|
| L0 Strategy | mature | none; quarterly review against primary metric due 2026-07-01 |
| L1 Brand posture | N/A-explicit | internal-platform; no user-facing surface |
| L2 Philosophy | mature | none; consent-flow incident drill scheduled 2026-05-20 |
| L3 Framework contract | mature | none; eval baseline current; cost ceiling holding |
| L4 Platform kit | mature (mirror) | mirror sync drift detection at 14 days behind source; resolve by 2026-05-05 |
| L5 Instance dossiers | mature (3 platforms) | sdr-handoff-helper voice-tuning row N/A; no gap |
| L6 Per-instance refinement | mature (per L5 dossier) | mql-router p99 latency above target; tracked in BACKLOG |
| L7 Cross-platform glue | mature | none; six concerns all live |

For full audit detail see `MATURITY-SCORECARD.md`. Last full audit: 2026-04-26.

## Cross-platform glue at a glance

| Concern | State | Owner |
|---------|-------|-------|
| Shared memory | exists-mature | RevOps Data team |
| Shared identity | exists-mature | Platform Engineering |
| Handoff protocol | exists-mature | RevOps-AI (this team) |
| Consent flow | exists-mature | Compliance Engineering |
| Alerting fabric | exists-mature | RevOps-Ops oncall |
| Monitoring base | exists-mature | RevOps-Ops |

## Platforms (L5 instances)

| Platform | Purpose | Production status | Owner |
|----------|---------|-------------------|-------|
| `mql-enrichment-service` | Core enrichment platform; produces enriched MQL records | live | RevOps-AI |
| `mql-router` | Downstream routing; assigns enriched MQLs to SDR queues by territory and intent | live | RevOps-AI |
| `sdr-handoff-helper` | SDR-side copilot inside {{crm_name}}; surfaces enrichment context inline | live (canary 30%) | RevOps-AI |

Each platform has a dossier at `platforms/{{platform}}/dossier.md`.

## Inheritance chain

```
{{cutting_edge_saas_company}} corporate AI policy (org-level)
        |
        v
mql-enrichment-service - L0 strategy (this instance)
        |
        +--> L1 brand posture (N/A-explicit; internal-platform)
        +--> L2 philosophy
        |           |
        |           v
        +--> L3 framework contract
        |           |
        |           v
        +--> L4 platform kit (mature-internal-mirror from {{platform_team_name}}/ai-kit)
        |           |
        |           v
        +--> L5 instance dossiers (3 platforms)
        |
        +--> L7 cross-platform glue (six concerns; all mature)
```

## Active ADRs

- **ADR-0001: Build the enrichment service rather than buying** - chose build because the intent-signal weighting encodes proprietary {{cutting_edge_saas_company}} customer data; vendor solutions cannot match the custom signals
- **ADR-0002: One-way pull from {{platform_team_name}}/ai-kit; no push back** - kit-mirror posture; product team consumes from platform kit; improvements that emerge here flow back via inbox-outbox to platform team for their consideration
- **ADR-0003: Synchronous consent check with 5-minute cache TTL** - consent-flow integration; chose sync-with-cache over fire-and-forget to satisfy GDPR Art. 7 + 17 with bounded latency cost

Full text in `decisions/`. None superseded. None proposed.

## Inbox topology summary

Active inbox-outbox pairs:

- `{{platform_team_name}} -> mql-enrichment-service` (mirror sync events; biweekly drain; last drained 2026-04-22)
- `mql-enrichment-service -> {{platform_team_name}}` (capability requests; biweekly drain; last drained 2026-04-22)
- `sdr-team -> mql-enrichment-service` (failure modes observed in production; weekly drain; last drained 2026-04-25)
- `mql-enrichment-service -> compliance-engineering` (privacy reviews needed; on-event; last activity 2026-04-22 consent-flow incident review)

For full detail see `inbox-topology.md`.

## What to do if you are new here

1. Read this document end-to-end. (You just did.)
2. Read `BOOTSTRAP-BRIEF.md` if you have not already; that is the standard you operate by.
3. Read the layer policies in order: `policies/strategy.md` -> `policies/brand-posture.md` (skim; N/A-explicit) -> `policies/philosophy.md` -> `policies/framework-contract.md`.
4. Read `MATURITY-SCORECARD.md` for the current full audit state.
5. Read the most recent two `sessions/` logs.
6. Read `BACKLOG.md` for pending work.
7. Read `HANDOFF.md` for custody and cross-pod state.

After this, you should be able to state the instance's purpose and maturity in two sentences, name the highest-leverage next move, and start work.

## Single highest-leverage next move

Resolve the L4 mirror sync drift before 2026-05-05. The `{{platform_team_name}}/ai-kit` source has shipped two prompt-library updates and one eval-harness update in the last 14 days; mql-enrichment-service is currently behind. Owner: RevOps-AI eng lead; assistive: Platform Engineering. Closes-by: 2026-05-05. Unblocks: next quarter's eval refresh against the updated harness.

## Cross-references

- `BOOTSTRAP-BRIEF.md` (kit-internal) - the operating-model standard this instance follows
- `MATURITY-SCORECARD.md` - full audit
- `policies/` - L0-L3 layer artifacts
- `kit/` - L4 platform kit (mirrored)
- `platforms/` - L5 instance dossiers
- `cross-platform/` - L7 glue
- `decisions/` - ADR archive
- `sessions/` - session log archive
- `inbox/` - inbox files
- `BACKLOG.md` - pending work
- `HANDOFF.md` - custody and resumption
- `LOCALIZATION-ANSWERS.md` - the 10 answers that drove this instance's population
