---
name: Inbox Topology - mql-enrichment-service
description: Declared inbox-outbox pairs for mql-enrichment-service. Four pairs active. Each pair has typed entries, cadence, owners on both sides, and audit trail.
type: governance-artifact
populated_from: Q9, Q7, Q8
Owner: RevOps-AI eng lead
---

# Inbox Topology - mql-enrichment-service

- **Last reviewed:** 2026-04-22
- **Review cadence:** quarterly
- **Status:** active

## Maturity self-assessment

| Aspect | State | Evidence |
|--------|-------|----------|
| Inbox pairs declared | mature | Four pairs below; each has both inbox and outbox files live |
| Each pair has typed entry schema | mature | Common schema in `inbox/SCHEMA.md`; each pair links to it |
| Each pair has named owners (both sides) | mature | All four pairs have owners on both sides |
| Each pair has drain cadence | mature | All four pairs have stated cadence; drains evidence in session logs |
| Each pair shows recent drain evidence | mature | Most recent quarterly review log shows all four drained |

## Declared pairs

### Pair 1: {{platform_team_name}} -> mql-enrichment-service (kit sync events + capability acknowledgements)

- **Inbox path:** `inbox/from-{{platform_team_name}}.md`
- **Outbox path (other side):** `{{platform_team_name}}/outbox/to-revops-ai.md`
- **Typed entries:** kit-sync-event, capability-request-ack, deprecation-notice, breaking-change-notice
- **Cadence:** biweekly drain (every other Monday); event-driven additions any time
- **Owner (this side):** RevOps-AI eng lead
- **Owner (other side):** {{platform_eng_lead}} (Platform Engineering)
- **Last drained:** 2026-04-22 (during consent-flow incident review; opportunistic)
- **Recent activity:** 4 entries open / 14 drained this quarter
- **Audit:** quarterly review confirms entries either resolved, escalated to ADR, or moved to BACKLOG

### Pair 2: mql-enrichment-service -> {{platform_team_name}} (capability requests)

- **Inbox path (other side):** `{{platform_team_name}}/inbox/from-revops-ai.md`
- **Outbox path:** `outbox/to-{{platform_team_name}}.md`
- **Typed entries:** capability-request, drift-resolution-needed, kit-improvement-proposal
- **Cadence:** biweekly drain (Platform Engineering side, every other Monday)
- **Owner (this side):** RevOps-AI eng lead
- **Owner (other side):** {{platform_eng_lead}}
- **Last drained:** 2026-04-22 (Platform Engineering drained their inbox; we observed via response in their outbox)
- **Recent activity:** 2 entries open / 6 drained this quarter
- **Audit:** Platform Engineering side maintains the audit; we receive the outcomes via Pair 1 acknowledgements

### Pair 3: sdr-team -> mql-enrichment-service (failure modes observed in production)

- **Inbox path:** `inbox/from-sdr-team.md`
- **Outbox path (other side):** `sdr-team/outbox/to-revops-ai.md`
- **Typed entries:** ux-issue, sdr-edit-respect-violation, helper-card-feedback, enrichment-quality-issue, false-positive, false-negative
- **Cadence:** weekly drain (Friday afternoon)
- **Owner (this side):** RevOps-AI eng team (rotating)
- **Owner (other side):** SDR Team Lead
- **Last drained:** 2026-04-25
- **Recent activity:** 3 entries open / 22 drained this quarter
- **Audit:** SDR-side feedback drives canary expansion decisions; quarterly summary captured in OPERATING-MODEL highest-leverage section

### Pair 4: mql-enrichment-service <-> compliance-engineering (privacy and regulatory reviews)

- **Inbox path:** `inbox/from-compliance-engineering.md`
- **Outbox path (other side):** `compliance-engineering/outbox/to-revops-ai.md`
- **Typed entries:** privacy-review-needed, regulatory-change-notice, control-evidence-due, audit-finding, drill-result
- **Cadence:** on-event (no fixed cadence; entries drive their own drain)
- **Owner (this side):** RevOps-AI eng lead
- **Owner (other side):** {{compliance_eng_lead}}
- **Last drained:** 2026-04-22 (during consent-flow incident; new entry with heartbeat-event proposal)
- **Recent activity:** 1 entry open (heartbeat proposal) / 4 drained this quarter
- **Audit:** every entry tied to a regulatory regime or control; SOC 2 control evidence captured annually

## Patterns considered but not declared

- **Customer -> Product:** N/A; this instance is `internal-platform`; no external customer surface to receive feedback from. If sdr-handoff-helper ever exposes summaries to customers, this pattern activates.
- **Engineering -> Compliance:** covered by Pair 4 (consolidated direction; this team treats Compliance as both Engineering and Compliance touch points)

## Drain protocol

Per BOOTSTRAP-BRIEF Section IX and the inbox-topology template:

1. Read entry; confirm typed shape
2. Classify next move: `acknowledge` / `actioned-here` / `escalate-to-ADR` / `move-to-BACKLOG`
3. Update entry's state and date
4. Ping other side's owner if needed

A drain that produces no state changes is a finding (either no traffic or read-only-glance; both warrant attention).

## Audit posture (last quarterly review)

From 2026-04-15 quarterly review:

- Pair 1: 14 entries / quarter; healthy
- Pair 2: 6 entries / quarter; healthy
- Pair 3: 22 entries / quarter; high traffic but well-drained; SDR feedback is core production input
- Pair 4: 4 entries / quarter; appropriately low (Compliance is on-event)

No retirements proposed; no cadence increases needed.

## Inheritance and dependencies

Inherits from: portfolio-level Inbox Flow standard (referenced as a general pattern; no portfolio-level enforcement at {{cutting_edge_saas_company}} but the pattern is universal here).

Consumed by: every session log that drains an inbox; quarterly review.

## Cross-references inside this instance

- `inbox/SCHEMA.md` - typed-entry schema (date, source, type, state, priority, target close)
- `inbox/from-{{platform_team_name}}.md`
- `inbox/from-sdr-team.md`
- `inbox/from-compliance-engineering.md`
- `outbox/to-{{platform_team_name}}.md`
- `BACKLOG.md` - destination for parked entries
- `decisions/` - destination for escalated entries
- `sessions/2026-04-15-quarterly-review.md` - last drain evidence
