---
name: L7 Cross-Platform Glue - mql-enrichment-service
description: Summary of the six L7 cross-platform concerns for mql-enrichment-service. Each concern has a dedicated artifact in this directory; this file is the index. All six are exists-mature; verified live within the last 30 days.
type: layer-artifact
layer: L7
populated_from: Q8, Q7
Owner: per-concern (see table); overall L7 governance owned by RevOps-AI eng lead
---

# L7 Cross-Platform Glue - mql-enrichment-service

- **Last reviewed:** 2026-04-26
- **Review cadence:** quarterly + on every new L5 instance addition
- **Status:** active

## Maturity self-assessment

| Concern | State | Owner | Last verified live | Detail |
|---------|-------|-------|--------------------|--------|
| Shared memory | exists-mature | RevOps Data team | 2026-04-22 | `cross-platform/shared-memory.md` |
| Shared identity | exists-mature | Platform Engineering | 2026-04-19 | `cross-platform/shared-identity.md` |
| Handoff protocol | exists-mature | RevOps-AI (this team) | 2026-04-25 | `cross-platform/handoff-protocol.md` |
| Consent flow | exists-mature | Compliance Engineering | 2026-04-22 | `cross-platform/consent-flow.md` |
| Alerting fabric | exists-mature | RevOps-Ops | 2026-04-27 | `cross-platform/alerting-fabric.md` |
| Monitoring base | exists-mature | RevOps-Ops | 2026-04-27 | `cross-platform/monitoring-base.md` |

All six concerns at `exists-mature`; none `none-applicable` or `declared-not-built`. This is unusual; it reflects {{cutting_edge_saas_company}}'s investment in shared cross-cutting capabilities before this team's deployment landed (the consent flow, identity, alerting, and monitoring all existed; this team consumed and extended).

## Cross-instance dependency graph

```
mql-enrichment-service ──participates──▶ shared-memory (write), shared-identity (validate),
                                          handoff (emit), consent-flow (check), alerting (emit),
                                          monitoring (emit)
                                                  │
                                                  │  (handoff envelope)
                                                  ▼
mql-router ────────────participates──▶ shared-memory (read+write), shared-identity (validate),
                                       handoff (consume+emit), alerting (emit), monitoring (emit)
                                                  │
                                                  │  (assignment envelope)
                                                  ▼
sdr-handoff-helper ──participates──▶ shared-memory (read), shared-identity (validate),
                                     handoff (consume), consent-flow (read result),
                                     alerting (emit), monitoring (emit)
```

The chain runs left-to-right; every cross-cutting concern is touched by at least two of the three platforms. Consent-flow is checked authoritatively at mql-enrichment-service and read downstream from the enrichment record (no re-checks; ADR-0003 explains).

## Why L7 is reported with this much rigor

L7 is the most-commonly-missed layer. Reporting six named concerns with explicit live-vs-declared classification defeats the omission failure mode by structure rather than by discipline.

Reporting evidence:

- Every concern has a dedicated artifact in this directory
- Every concern has an owner (not "the team")
- Every concern has a last-verified-live date (not "we believe it works")
- Every concern names which L5 platforms participate

If any of these become missing as the instance evolves (e.g., a new platform adds without declaring its L7 participation), the validate skill flags it.

## Inheritance and dependencies

This L7 inherits from: {{cutting_edge_saas_company}} corporate cross-cutting capabilities (consent service, identity, alerting fabric, monitoring base) that pre-existed this deployment.

This L7 is consumed by: every L5 instance dossier under this strategy declares its participation explicitly.

## Cross-references inside this instance

- `cross-platform/shared-memory.md`
- `cross-platform/shared-identity.md`
- `cross-platform/handoff-protocol.md`
- `cross-platform/consent-flow.md`
- `cross-platform/alerting-fabric.md`
- `cross-platform/monitoring-base.md`
- `OPERATING-MODEL.md` - reports L7 summary
