---
name: L1 Brand Posture - mql-enrichment-service
description: L1 brand posture for mql-enrichment-service. Marked N/A explicitly per the internal-platform function type. This document exists so the layer is consciously excluded rather than silently forgotten.
type: layer-artifact
layer: L1
populated_from: Q1 (function type returned `internal-platform`), Q3 (disclosure returned `n/a-internal`)
Owner: RevOps-AI eng lead
---

# L1 Brand Posture - mql-enrichment-service

- **Last reviewed:** 2026-04-05
- **Review cadence:** quarterly + on function-type change
- **Status:** active (N/A-explicit)

## Maturity self-assessment

| Aspect | State | Evidence |
|--------|-------|----------|
| Customer segment described | N/A | Function type `internal-platform`; audience is SDRs and downstream automation, not external customers |
| Disclosure posture decided | N/A | Q3 returned `n/a-internal` |
| Tone / voice articulated | N/A | No prose output; structured records only |
| Attribution rule defined | N/A | No human-readable byline; provenance is in telemetry |

L1 is **N/A-explicit** for this instance. Marking N/A is the mature state for internal functions. This document exists so the layer is consciously excluded rather than silently forgotten.

## L1 N/A justification

`mql-enrichment-service` is `internal-platform`. Audience: SDRs at {{cutting_edge_saas_company}} (~45 reps) plus the downstream `mql-router` automation. No brand-facing surface. The output is a structured enrichment record persisted to `revops.mql_facts` and surfaced inside {{crm_name}}; it is read, not heard or seen as voice.

Because the function is internal:

- No disclosure copy is needed (SDRs know the enrichment is automated; this is communicated in `sdr-handoff-helper`'s onboarding doc, not in every output)
- No tone shorthand applies (structured records have no tone)
- No attribution rule applies (provenance is captured in telemetry: `enrichment_source_per_field` plus the reproducibility quadruple)

## If this layer becomes non-N/A

If a future product surface exposes enrichment output to external customers (e.g., a customer-portal that shows their own scoring), this artifact must be updated:

1. Q3 in `LOCALIZATION-ANSWERS.md` is revised; revision logged with date and reason
2. This document moves from `N/A-explicit` to `partial` and the operator answers the customer / disclosure / tone / attribution sections from the L1 template
3. ADR is written for the change
4. `policies/philosophy.md` (L2) is checked for any response-shape conventions that apply to the new external surface

## Inheritance and dependencies

This L1 inherits from: {{cutting_edge_saas_company}} corporate brand guidelines (in case the N/A status is ever reversed); not currently active.

This L1 is inherited by: no L5 instance currently produces user-facing output, so nothing inherits from this. If `sdr-handoff-helper`'s scope expands to expose any output to customers, the L1 layer activates and dossiers update.

## Cross-references inside this instance

- `policies/strategy.md` (L0) - the function-type designation that drives N/A
- `policies/philosophy.md` (L2) - red lines that bound any future activation of L1
- `LOCALIZATION-ANSWERS.md` Q1, Q3
- `OPERATING-MODEL.md` - reports L1 as N/A-explicit in summary table
