9. Maturity Assessment
Context engineering capability develops in stages. Most teams reach Level 2 and stop, not because higher levels are complex but because the failures at Level 2 are invisible. Output quality is acceptable, so the pressure to go further never appears. This assessment makes the gap visible.
The Six Levels
| Level | Name | What exists | Failure mode |
|---|---|---|---|
| 0 | No configuration | LLM with no CLAUDE.md | Generic outputs, zero project awareness |
| 1 | Flat config | Single CLAUDE.md, no structure | Rules pile up, adherence degrades after ~100 lines |
| 2 | Structured config | Sections, clear organization, global/project separation | Works solo, breaks at team scale |
| 3 | Modular config | Path-scoped modules, deliberate layering | Rules maintained but no verification |
| 4 | Measured config | Canary tests, adherence tracking, lifecycle management | System works but drifts silently over time |
| 5 | Engineered system | Profiles, CI drift detection, ACE pipeline, quarterly audit rhythm | None identified |
Self-Assessment
Answer each question and stop at the first "No": that is your current level.
Level 0 → 1: Do you have a CLAUDE.md file in your project?
Level 1 → 2: Does your configuration distinguish between global conventions (in ~/.claude/CLAUDE.md) and project-specific rules (in ./CLAUDE.md)? Are sections clearly separated?
Level 2 → 3: Are subsystem-specific rules in path-scoped modules rather than the root CLAUDE.md? Does your root CLAUDE.md stay under 150 lines?
Level 3 → 4: Do you have canary checks that verify key conventions? Do you track violation rates for your most important rules? Do you run a context audit after major milestones?
Level 4 → 5: Do team members assemble their CLAUDE.md from profiles rather than editing it directly? Is there CI drift detection that alerts when configuration diverges from source modules? Do you run session retrospectives to feed new patterns back into configuration?
What to Do at Each Level
| Your level | Next action |
|---|---|
| 0 | Create a minimal CLAUDE.md with 5-10 rules. See §3 for what belongs there. |
| 1 | Split global and project config. Move cross-project preferences to ~/.claude/CLAUDE.md. |
| 2 | Identify the 2-3 highest-traffic subsystems. Create path-scoped modules for them. |
| 3 | Write 3-5 canary prompts for your most violated rules. Automate them. |
| 4 | Introduce profiles for team members. Add CI drift detection. Start session retrospectives. |
| 5 | Maintain quarterly audits. The system is built. The work is ongoing calibration. |
Most teams move from Level 0 to Level 2 in a single afternoon. Moving from Level 3 to Level 4 requires a measurement habit, not more configuration. Knowledge matters less at the higher levels than discipline: the willingness to treat configuration as a living system rather than a one-time setup.