---
type: "synthesis"
tags: ["synthesis", "maturity-model", "adoption"]
spans: ["video", "paper"]
id: "synthesis-three-levels-meets-stage-pipeline"
sources: ["cross-day"]
---
# Synthesis: Three Levels of AI Use × ICM Stages

The video proposes a maturity model — [[concept-three-levels-ai]]:

- **L1** Copy & paste
- **L2** Structured prompts (brand-tone files, prompt libraries)
- **L3** Integrated workflows (automated pipelines)

The paper proposes a workspace architecture — [[framework-icm-architecture]] with stages, [[concept-stage-contracts]], [[concept-five-layer-hierarchy]].

## How they nest

The two are **complementary, not redundant**:

- L1 (ad-hoc) — no ICM at all. Just chat.
- L2 (structured prompts) — populate **Layer 3 references** (voice-and-tone, style guides — [[action-codify-voice]]). A team at L2 has a `references/` folder full of stable rules but is not yet running a multi-stage pipeline.
- L3 (integrated workflow) — full ICM pipeline. Numbered stage folders ([[action-numbered-stage-folders]]), review gates ([[action-review-gates]]), L4 outputs feeding L4 inputs.

## The ROI claim revisited

[[claim-l2-roi]] / [[quote-l2-roi]] says the L1 → L2 jump has the highest ROI. In paper terms, **building the L3 references/ layer pays the largest dividend** before you build any pipeline. This is consistent with the paper's [[concept-edit-source-principle]]: stable rules are the source; pipelines are runs of the source.

## On-ramp

The coherent adoption path across both sources:

1. [[action-codify-voice]] — write `voice-and-tone.md` (an L3 reference).
2. [[action-move-to-l2]] — build the prompt library (an L3 reference collection).
3. [[action-implement-folders]] — restructure into an ICM workspace.
4. [[action-numbered-stage-folders]] — add staged pipeline.
5. [[action-review-gates]] — formalize the review boundaries.

See [[arc-talk-vs-paper-altitude]], [[synthesis-skill-equals-stage-contract]].