> 🌐 中文版本 / Chinese version: [CASE_WRITING_STANDARD.md](CASE_WRITING_STANDARD.md)

# Case Writing Standard: L1-L5 IPOE and Verifiable Deliverables

Last updated: 2026-05-13

## 1. Purpose

No client case may be written as just a scenario story; every case must be written as a consulting delivery case.

Each case must answer:

1. Which evaluations has the client already undergone?
2. What is the input for each of the L1-L5 levels?
3. What is the process for each level?
4. What is the output for each level?
5. Which deliverables can be verified?
6. How is each stage judged to be complete?

## 2. Required Case Sections

Every complete case must include at least the following sections:

1. Case positioning.
2. Case delivery logic.
3. Client story.
4. Questionnaire response summary.
5. Company profile and deployment model judgment.
6. Recommended training mix.
7. Work assets to be produced during training.
8. Eight-stage consulting diagnostic analysis.
9. Three-phase Roadmap.
10. ROI metrics.
11. Final consulting report summary.
12. L1-L5 Input / Process / Output / Evidence.
13. Evaluation process and verifiable deliverables.
14. Stage Gate acceptance design.

## 3. L1-L5 IPOE Standard Format

IPOE stands for:

- Input: The data, systems, documents, roles, questionnaires, or processes required to enter the maturity stage.
- Process: What is actually done at this stage, including training, workshops, system integration, and governance design.
- Output: The documents, Skills, Workflows, Agents, reports, or operational outcomes produced at this stage.
- Evidence: Proof that the output exists and is usable.

### Standard Table

| Item | Definition |
| --- | --- |
| Input | `[Data, systems, processes, roles, questionnaires, documents]` |
| Process | `[Training, interviews, organization, build-out, integration, testing, review]` |
| Output | `[Prompt, Skill, Workflow, Agent task card, report, Roadmap]` |
| Evidence | `[Screenshots, logs, test cases, sign-off, version history, execution results]` |
| Acceptance criteria | `[Measurable or confirmable completion conditions]` |

## 4. Minimum Deliverable Standards for L1-L5

### L1 Controlled AI Access

Minimum deliverables:

- AI usage guidelines.
- A controlled AI entry point or an approved tool list.
- High-frequency personal Prompt templates.
- Training exercise outputs.

Verifiable evidence:

- Tool screenshots.
- Usage guideline documents.
- Prompt examples.
- Training attendance records.

### L2 Knowledge Codification

Minimum deliverables:

- Skill Library.
- 3-5 Skills.
- Skill Owners.
- Skill version history.

Verifiable evidence:

- Skill templates.
- Sample inputs and outputs.
- Test results by non-original authors.
- Owner sign-off.

### L3 Workflow Automation

Minimum deliverables:

- n8n Workflow PoC.
- System integration list.
- Credential / permission table.
- Human review node.
- Logging and error handling.

Verifiable evidence:

- Workflow JSON.
- Execution Log.
- Test data.
- Error notification screenshots.
- Human review records.

### L4 Autonomous Agent

Minimum deliverables:

- Hermes Agent task card.
- Agent tool inventory.
- Agent permission table.
- Agent reporting format.
- Human takeover mechanism.

Verifiable evidence:

- Agent test records.
- Tool invocation records.
- Output samples.
- Human review records.

### L5 Multi-Agent Organization

Minimum deliverables:

- ClawTeam role cards.
- Multi-Agent task assignment table.
- Output integration template.
- Reviewer / Critic / human Gate design.
- ROI tracking table.

Verifiable evidence:

- Agent Team execution records.
- Output from each Agent.
- Integration report.
- Manager review records.

## 5. Stage Gate Acceptance Logic

| Gate | Corresponding Maturity | Criterion for Progressing to the Next Stage |
| --- | --- | --- |
| Gate 1 | L1 | A controlled entry point, usage guidelines, and basic Prompts exist, and employees understand the data boundary |
| Gate 2 | L2 | Reusable Skills exist with Owners and versions |
| Gate 3 | L3 | The Workflow runs end-to-end with logging, human review, and error handling |
| Gate 4 | L4 | The Agent can invoke Skills / Workflows, permission boundaries are clear, and outputs are auditable |
| Gate 5 | L5 | Multi-Agent teams have role division, output integration, and human Gates |

## 6. Case Quality Checklist

Run this check before completing a case:

- [ ] Are the client industry, scale, departments, and systems clearly described?
- [ ] Are questionnaire scores and maturity judgments included?
- [ ] Is the company profile and deployment model judgment included?
- [ ] Is the L1-L5 training mix included?
- [ ] Is the eight-stage consulting diagnosis included?
- [ ] Are L1-L5 Input / Process / Output / Evidence included?
- [ ] Are verifiable deliverables included?
- [ ] Are Stage Gates included?
- [ ] Are ROI metrics included?
- [ ] Are explicit security boundaries and human review mechanisms included?

