---
name: Operating Model Template
description: Template for the deployed instance's OPERATING-MODEL.md. The root summary doc that lives at instance root and tells any fresh operator what this instance is, where it stands, and how to start. Read first per BOOTSTRAP-BRIEF Section V.
type: template
populated_from: synthesis of Q1, Q2, Q7, plus current maturity scorecard
---

# Operating Model Template

Copy this file to `OPERATING-MODEL.md` at the deployed instance root. This is the single doc a fresh operator reads first; it summarizes everything else.

The OPERATING-MODEL is updated on every material maturity change (a layer moves from one state to another, a major decision lands, a new platform is added) and on a quarterly minimum.

---

# Operating Model - {{instance_name}}

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

## What this instance is

{{instance_name}} is `{{function_type}}`. It {{purpose_sentence}}.

Sponsor: {{sponsor_name_or_role}}. Primary success metric: {{primary_metric}}.

This document is the root summary. Every other artifact in this instance is one layer below this one.

## Maturity at a glance

| Layer | State | One-line gap |
|-------|-------|--------------|
| L0 Strategy | {{state}} | ... |
| L1 Brand posture | {{state_or_N/A}} | ... or "N/A - internal function" |
| L2 Philosophy | {{state}} | ... |
| L3 Framework contract | {{state}} | ... |
| L4 Platform kit | {{state}} | ... |
| L5 Instance dossiers | {{state}} | ... |
| L6 Per-instance refinement | {{state}} | ... |
| L7 Cross-platform glue | {{state}} | ... |

For full audit detail see `MATURITY-SCORECARD.md`.

## Cross-platform glue at a glance

| Concern | State | Owner |
|---------|-------|-------|
| Shared memory | {{state}} | {{owner_or_n/a}} |
| Shared identity | {{state}} | {{owner_or_n/a}} |
| Handoff protocol | {{state}} | {{owner_or_n/a}} |
| Consent flow | {{state}} | {{owner_or_n/a}} |
| Alerting fabric | {{state}} | {{owner_or_n/a}} |
| Monitoring base | {{state}} | {{owner_or_n/a}} |

## Platforms (L5 instances)

| Platform | Purpose | Production status | Owner |
|----------|---------|------|------|
| `{{platform_a}}` | ... | live / canary / dev / archived | ... |
| `{{platform_b}}` | ... | ... | ... |

Each platform has a dossier at `platforms/{{platform}}/dossier.md`.

## Inheritance chain

This instance sits in the following chain:

```
{{org_strategy}} (if exists)
        │
        ▼
{{instance_name}} - L0 strategy
        │
        ├──▶ L1 brand posture (or N/A)
        ├──▶ L2 philosophy
        │           │
        │           ▼
        ├──▶ L3 framework contract
        │           │
        │           ▼
        ├──▶ L4 platform kit ({{posture}})
        │           │
        │           ▼
        ├──▶ L5 instance dossiers (per platform)
        │
        └──▶ L7 cross-platform glue (six concerns)
```

## Active ADRs

The decisions that shape this instance's current state. Catalog with one-line summary; full text in `decisions/`.

- ADR-0001: {{title}} - {{one_line_summary}}
- ADR-0002: {{title}} - {{one_line_summary}}
- ADR-0003: {{title}} - {{one_line_summary}}

[Add as new ADRs land; superseded ADRs stay in the catalog with `superseded by ADR-XXXX` annotation.]

## Inbox topology summary

Active inbox-outbox pairs:

- {{from_pod_a}} -> {{instance_name}} ({{cadence}}; last drained {{date}})
- {{from_pod_b}} -> {{instance_name}} ({{cadence}}; last drained {{date}})
- {{instance_name}} -> {{to_pod}} ({{cadence}})

For full detail see `inbox-topology.md`.

## What to do if you are new here

1. Read this document end-to-end. (You just did.)
2. Read `BOOTSTRAP-BRIEF.md` if you have not already; that is the standard you operate by.
3. Read the layer policies in order: `policies/strategy.md` -> `policies/brand-posture.md` (or skip if N/A) -> `policies/philosophy.md` -> `policies/framework-contract.md`.
4. Read `MATURITY-SCORECARD.md` for the current full audit state.
5. Read the most recent two `sessions/` logs.
6. Read `BACKLOG.md` for pending work.
7. Read `HANDOFF.md` for custody and cross-pod state.

After this, you should be able to state the instance's purpose and maturity in two sentences, name the highest-leverage next move, and start work.

## Single highest-leverage next move

{{Per most-recent maturity audit, the single move that matures the most layers or unblocks the most downstream work. One sentence; specific; assignable.}}

Example: "Move L3 framework contract from `partial` to `mature` by completing the eval methodology; closes-by 2026-05-15; owner {{owner}}."

## Cross-references

- `BOOTSTRAP-BRIEF.md` - the operating-model standard this instance follows
- `MATURITY-SCORECARD.md` - full audit
- `policies/` - L0-L3 layer artifacts
- `kit/` - L4 platform kit
- `platforms/` - L5 instance dossiers
- `cross-platform/` - L7 glue
- `decisions/` - ADR archive
- `sessions/` - session log archive
- `inbox/` - inbox files
- `BACKLOG.md` - pending work
- `HANDOFF.md` - custody and resumption
