AI Coding Tools Are Missing a Structural Layer — Observations from a Heavy Vibe Coding User

## The question no one is answering

Every AI coding tool — Claude Code, Cursor, Codex, and potentially DeepSeek Coder — is competing on model capability, tool chains, and context windows. But there's a structural gap that none of them have addressed:

**AI can do more and more things, but no one has told it what rules to follow while doing them.**

How should tasks be decomposed? How should deliverables be verified? What happens when verification fails — who is accountable? How do project conventions evolve alongside the code?

These are not model capability problems. They are engineering discipline problems.

## The 5-layer architecture and the missing 6th layer

Taking Claude Code as an example (the most publicly documented), its Harness can be decomposed into 5 layers:

1. **Instruction Layer** — CLAUDE.md, project configs, user memory
2. **Tool Layer** — Read, Write, Edit, Grep, Glob, Bash
3. **Agent Scheduling Layer** — Sub-agents, parallel execution
4. **Context Management Layer** — Compression, session persistence, cross-session memory
5. **Hooks Layer** — Event-driven automation

These 5 layers answer one question: **what can the AI do?**

But they don't answer: **what rules should the AI follow while doing it?**

Task decomposition protocols, acceptance criteria, cross-validation between executor and reviewer, living documentation that evolves with the project — none of these have been systematized into any tool.

## Why this matters for DeepSeek

Every tool vendor is racing on infrastructure, and the gap is narrowing. But the **Process Layer** — engineering discipline as a system, not just primitives — remains wide open. The vendor that fills this gap first will:

- Unlock a massive new user base (non-professional developers who lack internalized engineering discipline)
- Create switching cost (once a user's project runs on your process layer, migration cost is high)
- Define the standard that models will eventually internalize

## Why I'm writing this

I'm not a professional developer. I've been using AI coding tools (primarily Claude Code and Codex) full-time since early 2026 to build a complete SaaS product — 56 database tables, 23 API routers, 1200+ tests — without writing code directly.

In this process, I was forced to manually build a process layer: standardized task protocols, living documentation, cross-validation mechanisms. It works. But it shouldn't require a human to run it manually.

I've documented the full methodology and would welcome a technical discussion with the DeepSeek Coder team if this direction is of interest.

---

*Note: I'm writing this in English for broader visibility, but I'm based in China and happy to discuss in Chinese.*