---
name: L0 Strategy - {{instance_name}}
description: L0 strategy artifact for {{instance_name}}. Names why this capability exists, who sponsors it, the funding source, and the single primary success metric. Source for every downstream layer's scope decisions.
type: layer-artifact
layer: L0
populated_from: Q1 (function identity), Q2 (sponsor and success metric)
---

# L0 Strategy - {{instance_name}}

- **Last reviewed:** {{capture_date}}
- **Review cadence:** quarterly + on sponsor change
- **Status:** active

## Maturity self-assessment

| Aspect | State | Evidence |
|--------|-------|----------|
| Why this capability exists | none / stubbed / partial / mature | {{what backs this rating}} |
| Sponsor named and reachable | none / stubbed / partial / mature | ... |
| Funding source identified | none / stubbed / partial / mature | ... |
| Primary success metric quantified | none / stubbed / partial / mature | ... |

A mature L0 has all four aspects backed by concrete evidence. A stubbed L0 has placeholders only. The deploy skill writes the initial values from Q1 and Q2 answers.

## Function identity (from Q1)

- **Name:** `{{instance_name}}`
- **One-sentence purpose:** {{purpose_sentence}}
- **Type:** {{function_type}}

Example shape (anonymized): "`mql-enrichment-service`. Enriches inbound MQLs from {{paid_acquisition_channel}} with firmographic and intent signals before routing to SDR queue. Type: `internal-platform`."

## Sponsorship and success (from Q2)

- **Sponsor:** {{sponsor_name_or_role}}
- **Funding source:** {{funding_source}}
- **Primary success metric:** {{primary_metric}}
- **Tiebreak rule (if multiple metrics):** {{tiebreak_rule_or_n/a}}

Example shape: "Sponsor: VP of {{revenue_org}}, {{exec_name}}. Funding source: {{revenue_org}} operating budget, FY26 line item {{line_item_code}}. Primary metric: SDR-accepted-MQL rate from `{{instance_name}}`-enriched leads at or above {{baseline_pct}} (vs. {{control_pct}} baseline). Tiebreak: if SDR-accepted rate ties, optimize for time-to-first-touch reduction."

## Strategic posture

### Build vs. buy
{{build_vs_buy_decision}}

If `build`: {{build_rationale}}
If `buy`: {{vendor_selection_summary}}; ADR reference if any
If `hybrid`: name the boundary

### Capability portfolio fit
{{how_this_fits_in_the_broader_capability_portfolio}}

### Risk appetite
{{risk_appetite_statement}}

Example: "Build, because the enrichment logic encodes proprietary intent-signal weighting that {{org_name}} considers competitive moat. Capability fits between {{adjacent_capability_a}} (upstream) and {{adjacent_capability_b}} (downstream) in the demand-gen flow. Risk appetite: medium - false-positive enrichment costs SDR time but does not damage customer relationships; false-negative under-enrichment costs pipeline."

## Inheritance and dependencies

This L0 inherits from: {{parent_strategy_doc_or_none}}

This L0 is inherited by: L1 brand posture; L2 philosophy; L3 framework contract; every L5 instance dossier under this strategy.

If `inherits from` is `none`, this is a top-level strategy artifact. Note that explicitly to distinguish from "forgot to check parent."

## Cross-references inside this instance

- `policies/philosophy.md` (L2) - inherits red lines and PII handling
- `policies/framework-contract.md` (L3) - inherits eval threshold from primary metric
- `OPERATING-MODEL.md` - root doc summarizing this instance
- `decisions/` - ADRs that touch the build-vs-buy decision live here
