# HANDOFF - mql-enrichment-service

- **Project:** mql-enrichment-service
- **Pod root:** `revops-ai/mql-enrichment-service/` (in {{cutting_edge_saas_company}}-revops monorepo)
- **Last reviewed:** 2026-04-25
- **Review cadence:** on-event (refreshed when custody state changes); otherwise quarterly
- **Status:** active (canary phase for sdr-handoff-helper; production for the other two platforms)

## Custody state

`mql-enrichment-service` is owned by the RevOps-AI engineering team within {{cutting_edge_saas_company}}'s Revenue Operations org. The team has 4 engineers + lead, sponsored by VP RevOps {{exec_vp_revops}}. The instance lives in the `{{cutting_edge_saas_company}}-revops` Git monorepo under `revops-ai/mql-enrichment-service/`.

| Aspect | State |
|--------|-------|
| Repository | `git@{{cutting_edge_saas_company}}.internal:revops/{{cutting_edge_saas_company}}-revops.git` (monorepo); pod path `revops-ai/mql-enrichment-service/` |
| Authoritative branch | `main`; production deploys from main; canary deploys from `canary-*` branches per platform |
| Owner | RevOps-AI engineering team; lead {{eng_lead_name}} |
| Backups | Inherits {{cutting_edge_saas_company}} corporate Git backup ({{git_backup_strategy}}); plus warehouse fact tables backed up per RevOps Data retention |
| Secrets | None in repo; all credentials via {{secret_manager}}; tenant JWT signing via {{idp_name}} |
| One-way doors | (1) Closed-won customer corpus used to train intent-signal weighting cannot be regenerated identically; preserve the 2025-Q4 training snapshot. (2) Production retention buckets for SOC 2 audit trail are write-once for 7 years; deletion would require legal-hold override. |

## Cross-pod relationships

| Relationship | Direction | Type | Status | Last verified |
|-------------|-----------|------|--------|---------------|
| `{{platform_team_name}}/ai-kit/` -> `kit/` | source -> mirror | one-way mirror | declared-but-inactive (14-day drift; resolution by 2026-05-05) | 2026-04-12 |
| `inbox/from-{{platform_team_name}}.md` <- `{{platform_team_name}}/outbox/to-revops-ai.md` | inbox-outbox | typed-dated entries (kit-sync, capability-ack, deprecation, breaking-change) | live | 2026-04-22 (last drain) |
| `inbox/from-sdr-team.md` <- `sdr-team/outbox/to-revops-ai.md` | inbox-outbox | typed-dated entries (failure modes, ux issues) | live | 2026-04-25 (last drain) |
| `inbox/from-compliance-engineering.md` <-> `compliance-engineering/outbox/to-revops-ai.md` | inbox-outbox | typed-dated entries (privacy reviews, regulatory changes, control evidence, drill results) | live | 2026-04-22 (last drain) |
| `mql-enrichment-service` -> `consent-service` | runtime call | sync API (cached) | live | 2026-04-22 (incident drill) |
| `mql-enrichment-service` -> `revops.mql_facts` (warehouse) | runtime write | atomic upsert | live | continuously verified via post-hoc guardrail |
| `mql-enrichment-service` -> `enrichment-complete` topic | runtime publish | structured envelope | live | 2026-04-25 |
| `enrichment-complete` topic -> `mql-router` | runtime consume | structured envelope | live | 2026-04-25 |
| `assignment-complete` topic -> `sdr-handoff-helper` | runtime consume | structured envelope | live | 2026-04-25 |
| All platforms -> `consent-revocations` topic | runtime subscribe | event invalidation | live (resilience verified 2026-04-22 after transient failure) | 2026-04-22 |
| All platforms -> {{idp_name}} | runtime call | JWT validation | live | 2026-04-19 (cross-tenant drill) |

## Files in custody

```
revops-ai/mql-enrichment-service/
├── CLAUDE.md
├── OPERATING-MODEL.md
├── BACKLOG.md
├── HANDOFF.md (this file)
├── MATURITY-SCORECARD.md
├── LOCALIZATION-ANSWERS.md
├── inbox-topology.md
├── policies/
│   ├── strategy.md
│   ├── brand-posture.md
│   ├── philosophy.md
│   └── framework-contract.md
├── kit/
│   ├── PLATFORM-KIT.md
│   ├── contracts/
│   │   ├── enrichment-record-schema.json
│   │   └── handoff-envelope-schema.json
│   ├── prompts/ (mirrored from {{platform_team_name}}/ai-kit/prompts/)
│   ├── eval-harness/ (mirrored)
│   ├── eval-data/ (locally owned)
│   ├── guardrails/ (mirrored)
│   └── telemetry/ (mirrored)
├── platforms/
│   ├── mql-enrichment-service/dossier.md
│   ├── mql-router/dossier.md
│   └── sdr-handoff-helper/dossier.md
├── cross-platform/
│   ├── L7-glue.md
│   ├── shared-memory.md
│   ├── shared-identity.md
│   ├── handoff-protocol.md
│   ├── consent-flow.md
│   ├── alerting-fabric.md
│   └── monitoring-base.md
├── decisions/
│   ├── ADR-0001-build-vs-buy.md
│   ├── ADR-0002-kit-mirror-direction.md
│   └── ADR-0003-consent-flow-integration.md
├── inbox/
│   ├── SCHEMA.md
│   ├── from-{{platform_team_name}}.md
│   ├── from-sdr-team.md
│   └── from-compliance-engineering.md
├── outbox/
│   ├── to-{{platform_team_name}}.md
│   └── to-compliance-engineering.md
├── sessions/
│   ├── 2026-04-15-quarterly-review.md
│   └── 2026-04-22-consent-flow-incident.md
└── runbooks/
    ├── mql-enrichment-incident.md
    ├── mql-router-incident.md
    ├── sdr-handoff-helper-incident.md
    ├── pii-incident.md
    ├── consent-flow-incident.md
    ├── identity-incident.md
    ├── shared-memory-incident.md
    ├── handoff-dead-letter-recovery.md
    ├── oncall-shift-start.md
    ├── retention-extend.md
    ├── cost-extend.md
    ├── cross-tenant-drill.md
    ├── soc2-control-evidence.md
    └── mirror-sync-conflict.md
```

## Resumption posture

If picked up by a fresh session or operator with no prior context, read in this order:

1. `OPERATING-MODEL.md` - root summary; instance purpose and current maturity
2. `policies/` - L0 (strategy), L1 (N/A-explicit), L2 (philosophy), L3 (framework contract) in order
3. `HANDOFF.md` - this file (custody and cross-pod state)
4. Most recent two `sessions/` - what just happened (quarterly review + consent-flow incident)
5. `BACKLOG.md` - what is queued
6. `decisions/` - locked ADRs to respect
7. `platforms/` - the three L5 dossiers being operated

After this read, the operator should be able to: (a) state the instance's purpose and maturity in two sentences, (b) name the next-move owner per pending finding (highest-leverage: L4 mirror sync drift resolution), (c) execute the BOOTSTRAP-BRIEF Section V "When you start any session" protocol.

## IP boundary notes

This instance is internal-only ({{cutting_edge_saas_company}} engineering systems). The methodology applied (L0-L7 layered architecture, BOOTSTRAP-BRIEF standard) is general professional practice; no IP boundary issues. The intent-signal weighting trained on closed-won customer corpus is {{cutting_edge_saas_company}} proprietary; treat as competitive moat.

Application protocol: this instance was deployed using the AI-Architect deployment kit (V1, 2026-05-04). Methodology references the kit's BOOTSTRAP-BRIEF; specific implementation details belong to {{cutting_edge_saas_company}} as work product. Personal-side improvements to the methodology that emerge during this instance's operation flow back to the kit's source library, not into this instance's repo.

## Concurrent-actor posture

- **Expected concurrent actors:** 5-6 sustained (4 RevOps-AI engineers + lead + occasional Platform Engineering pair + ad-hoc Compliance Engineering observer)
- **Lock-on-write boundaries:** `kit/prompts/` (during prompt revision); `kit/contracts/` (during schema bumps); ADRs are immutable so no lock needed
- **Coordination surface:** `#revops-ai` Slack channel for ambient coordination; `#revops-ai-incidents` for incident-time; PagerDuty schedule `revops-ai` for paged events; quarterly review is the formal coordination event

## Compliance posture

Active regimes: GDPR (EU customer data), SOC 2 (vendor audit obligation).

Compliance artifacts:

- GDPR: see `cross-platform/consent-flow.md`; ADR-0003 records the integration approach; quarterly drill captures evidence
- SOC 2: see `policies/framework-contract.md` (telemetry schema with reproducibility quadruple is the audit trail mechanism); annual control evidence captured in `runbooks/soc2-control-evidence.md`

## Cross-references

- `OPERATING-MODEL.md` - root doc this handoff supports
- `BACKLOG.md` - pending work
- `decisions/` - locked ADRs
- `sessions/` - session log directory
- `LOCALIZATION-ANSWERS.md` - the 10 answers driving this instance's shape
