---
name: L5 Instance Dossier - {{instance_name}} / {{platform_name}}
description: L5 dossier for one specific platform/agent/workflow under {{instance_name}}. One file per platform listed in Q7. Names what this platform does, which kit components it consumes, its current state and ownership, and any L6 refinement concerns specific to it.
type: layer-artifact
layer: L5
populated_from: Q7 (instances in scope), Q1 (function identity), inheritance from L0-L4
---

# L5 Instance Dossier - {{instance_name}} / {{platform_name}}

- **Last reviewed:** {{capture_date}}
- **Review cadence:** quarterly + on every L4 kit version bump
- **Status:** active

> *Build-flavored template. The maturity rows below name build-mode aspects (eval baseline, kit components consumed). Operator / decider / creator deployments use the same dossier shape with translated content per layer (per ADR-0006). The deploy skill renders the mode that matches Q1.*

## Maturity self-assessment

| Aspect | State | Evidence |
|--------|-------|----------|
| Purpose articulated | none / stubbed / partial / mature | ... |
| Owner named and reachable | none / stubbed / partial / mature | ... |
| Kit components consumed declared | none / stubbed / partial / mature | ... |
| L3 contract conformance verified | none / stubbed / partial / mature | ... |
| Eval baseline established | none / stubbed / partial / mature | ... |
| L6 refinement concerns named | none / stubbed / partial / mature | ... |
| Production deployment status | none / stubbed / partial / mature | ... |

A mature L5 has every aspect concrete; a partial L5 names the gaps; a stubbed L5 has the dossier shape but empty values.

## Identity (from Q7)

- **Platform name:** `{{platform_name}}`
- **One-sentence purpose:** {{platform_purpose}}
- **Type:** {{platform_type}} (e.g., `agent`, `workflow`, `copilot`, `automation`, `dashboard`)
- **Production status:** {{prod_dev_canary_archived}}

Example shape: "Platform: `mql-router`. Purpose: routes enriched MQLs from `{{instance_name}}` to the right SDR queue based on intent score and territory. Type: `automation`. Production status: live."

## Ownership

- **Owner:** {{owner_name_or_team}}
- **Oncall rotation:** {{oncall_path_or_n/a}}
- **Escalation:** {{escalation_path}}
- **Documentation owner:** {{doc_owner_if_different}}

## Kit components consumed (from L4)

This instance consumes from `kit/`:

| Component | Path | Version pin | Mirror status |
|-----------|------|-------------|---------------|
| Prompt | kit/prompts/{{prompt_file}} | {{version_hash}} | live / declared-but-inactive |
| Eval harness | kit/eval-harness/ | {{version_hash}} | live / declared-but-inactive |
| Guardrail runtime | kit/guardrails/ | {{version_hash}} | live / declared-but-inactive |
| Telemetry plumbing | kit/telemetry/ | {{version_hash}} | live / declared-but-inactive |
| L3 contract | kit/contracts/{{instance_name}}-contract.json | {{version_hash}} | live / declared-but-inactive |

Mirror status `live` requires evidence: a recent invocation that produced telemetry consistent with the kit's emitted schema. `declared-but-inactive` is the default until evidence shows otherwise.

## L3 contract conformance

- **Eval score (latest run):** {{score_per_metric}}
- **Eval ship threshold met:** yes / no / pending
- **Per-call cost (90th percentile):** ${{cost_p90}}
- **Cost ceiling met:** yes / no / breaching at {{rate}}
- **Telemetry schema emitted:** complete / partial (gaps named)
- **Auth model implemented:** yes / no / waiver in place

If any conformance row is `no`, that row is a finding for the next session log.

## L6 Per-instance refinement

Polish concerns isolated to this platform. Not L3 contract requirements; specific to how `{{platform_name}}` integrates and feels.

- **Latency observed (p50 / p95 / p99):** {{latency_distribution}}
- **Latency target:** {{target}}
- **UX integration points:** {{ui_or_api_surfaces}}
- **Voice tuning notes:** {{voice_observations_specific_to_this_platform}}
- **Known sharp edges:** {{quirks_known_to_users}}

If `{{instance_name}}` is type `internal-tool` / `internal-platform` / `external-api` (no L1 surface), the voice-tuning row reads: "N/A - internal function, no user-facing voice."

## Concurrent-actor notes

Per BOOTSTRAP-BRIEF Section IX:

- **Expected concurrent operators on this instance:** {{count_or_unbounded}}
- **Lock-on-write boundaries:** {{which_files_or_state_require_locking}}
- **Session log location for this platform:** `sessions/` (root-level) or `{{platform_name}}/sessions/` (platform-local)

## Recent session activity

Most recent two session logs touching `{{platform_name}}`:

- {{date}} - {{session_purpose}} - {{outcome}}
- {{date}} - {{session_purpose}} - {{outcome}}

If none yet, this section reads: "No prior session activity. This dossier is the first artifact for `{{platform_name}}`."

## Open ADRs and findings

- {{open_adr_or_finding_1}}
- {{open_adr_or_finding_2}}

## Inheritance and dependencies

This L5 inherits from: L0 strategy, L1 brand posture (or N/A), L2 philosophy, L3 framework contract, L4 platform kit.

This L5 may participate in L7 cross-platform glue (consent flow, alerting, monitoring base, shared identity, handoff protocol). Named participation:

- {{cross_platform_concern_a}}: {{role_this_instance_plays}}
- {{cross_platform_concern_b}}: {{role_this_instance_plays}}

## Cross-references inside this instance

- `OPERATING-MODEL.md` - root doc summarizing the deployment
- `policies/strategy.md` (L0)
- `policies/philosophy.md` (L2)
- `policies/framework-contract.md` (L3)
- `kit/` - the L4 components this dossier consumes
- `cross-platform/` (L7) - cross-cutting concerns this instance participates in
- `decisions/` - ADRs that touch `{{platform_name}}` specifically
- `runbooks/{{platform_name}}-*.md` - oncall and incident runbooks for this platform
