---
name: L4 Platform Kit - mql-enrichment-service
description: Platform kit posture for mql-enrichment-service. Posture is mature-internal-mirror; this instance mirrors components from {{platform_team_name}}/ai-kit. Mirror manifest, sync cadence, and drift discipline below.
type: layer-artifact
layer: L4
populated_from: Q6 (mature-internal-mirror), Q5 (the contract this kit implements)
Owner: RevOps-AI eng lead consumes; {{platform_team_name}} owns the source kit
---

# L4 Platform Kit - mql-enrichment-service

- **Last reviewed:** 2026-04-22 (after biweekly mirror sync)
- **Review cadence:** quarterly + on every L3 contract revision + on every model bump
- **Status:** active (mirror); 14 days behind source as of 2026-04-26 (resolution closes-by 2026-05-05)

## Maturity self-assessment

| Aspect | State | Evidence |
|--------|-------|----------|
| Posture decided | mature | `mature-internal-mirror`; ADR-0002 records the decision |
| L3 contract implemented in code | mature | All four guardrail layers live; eval harness CI-runnable; auth verified 2026-04-19 |
| Prompt library exists | mature | Mirrored from `{{platform_team_name}}/ai-kit/prompts/`; three enrichment tiers |
| Eval harness exists | mature | Mirrored from `{{platform_team_name}}/ai-kit/eval-harness/`; dataset local |
| Guardrail runtime exists | mature | Mirrored from `{{platform_team_name}}/ai-kit/guardrails/`; PII detector, schema validator, consent check |
| Telemetry plumbing exists | mature | Mirrored from `{{platform_team_name}}/ai-kit/telemetry/`; emits to {{observability_platform}} |
| Mirror discipline | partial | 14-day drift identified 2026-04-26; biweekly cadence missed once; resolution scheduled |

## Posture

**Selected posture:** `mature-internal-mirror`

The {{platform_team_name}} central platform team owns the kit. RevOps-AI consumes from it. Mirror direction is one-way (pull only). When this team needs new capabilities, requests flow via the inbox-outbox pair to {{platform_team_name}}; we do not push directly into their kit.

Decision rationale recorded in `decisions/ADR-0002-kit-mirror-direction.md`.

## Mirror manifest

| Component | Source path | Mirror path | Last sync | Drift status |
|-----------|-------------|-------------|-----------|--------------|
| Prompt library | {{platform_team_name}}/ai-kit/prompts/ | kit/prompts/ | 2026-04-12 | declared-but-inactive (14 days behind; two updates pending pull) |
| Eval harness | {{platform_team_name}}/ai-kit/eval-harness/ | kit/eval-harness/ | 2026-04-12 | declared-but-inactive (one update pending pull) |
| Guardrail runtime | {{platform_team_name}}/ai-kit/guardrails/ | kit/guardrails/ | 2026-04-12 | live (no updates upstream since last sync) |
| Telemetry plumbing | {{platform_team_name}}/ai-kit/telemetry/ | kit/telemetry/ | 2026-04-12 | live (no updates upstream since last sync) |
| L3 contract artifact | {{platform_team_name}}/ai-kit/contracts/ | kit/contracts/ | 2026-04-12 | live (no updates upstream; this team's contract local-only) |

Each mirrored file carries `MIRRORED FROM: {{platform_team_name}}/ai-kit/...` as the first non-frontmatter line, plus a sync date.

## Drift discipline

- **Re-sync cadence:** biweekly (every other Monday); driven by the `architect-kit-mirror` skill running against the source
- **Drift detection:** automated; output goes to `inbox/from-{{platform_team_name}}.md` whenever upstream commits since last sync
- **Resolution path:**
  - Clean re-sync: pull, re-run eval against updated harness, ship if eval passes
  - Drift with our local changes: open ADR for each conflict; resolve before pulling
  - Source-side breaking change: flag to {{platform_team_name}} for staged migration

## Locally-owned components (not mirrored)

These are not in the upstream kit; this instance owns them:

- `kit/contracts/enrichment-record-schema.json` - the enrichment record schema; specific to this instance's downstream consumers (mql-router, sdr-handoff-helper)
- `kit/eval-data/revops-mql-eval-2026-Q1.jsonl` - the eval dataset; curated from this team's production logs; not portable to other consumers of the central kit
- `kit/runbooks/mirror-sync-conflict.md` - drift resolution runbook for this team's recovery patterns

These local files do not carry `MIRRORED FROM` headers. They are this instance's L4 contributions.

## Reproducibility pin

The L4 platform kit pins per L3 contract:

- `kit_version` = `2026-04-12.b` (sync hash from {{platform_team_name}}/ai-kit at that date)
- `model_family` = `{{model_family}}` (set in `{{platform_team_name}}/ai-kit/models.yaml`)
- `prompt_library_version` = composite of three tier hashes; tracked in `kit/prompts/MANIFEST.md`
- `eval_harness_version` = sync hash; harness behavior locked at sync time
- `eval_data_snapshot_version` = `revops-mql-eval-2026-Q1@{hash}`

Bumping `kit_version` (next biweekly sync) invalidates the prompt-library and eval-harness pins; re-run eval before shipping.

## Inheritance and dependencies

This L4 implements: `policies/framework-contract.md` (L3) as concrete code (mirrored).

This L4 is inherited by: every L5 instance dossier (each consumes prompts + harness + guardrails + telemetry).

## Cross-references inside this instance

- `policies/framework-contract.md` (L3)
- `decisions/ADR-0002-kit-mirror-direction.md`
- `inbox/from-{{platform_team_name}}.md` - mirror sync events and capability-request acknowledgements
- `runbooks/mirror-sync-conflict.md`
- `kit/contracts/enrichment-record-schema.json`
- `kit/MANIFEST.md` - per-component version pins
