DeepSeek Harness 地图

The loop and the handful of services it declares a dependency on. The loop itself is 1,643 lines; the ring around it is the product.

• The Loop1,643 lines

  Driver of turns and steps — the product’s skeleton of time

• Agent Interface2,197 lines

  Inbox, event routing, and a registration scope per session

• Tool Pipeline8,728 lines

  Registry, visibility resolution, and a five-stage execution pipeline

• Session Log16,830 lines

  An append-only ledger; model history is recomputed from it every time

• Prompt Assembly3,991 lines

  Sections, variables and tool schemas, assembled by numbered bands

Everything that decides what the model sees: which model to call, what to do when the window fills up, how outside material gets in.

• Model Seam8,040 lines

  Streaming vocabulary, adapter contract, error classification and retry

• Compaction2,880 lines

  Two triggers, region selection, shadowing instead of deletion

• Skills & Outside Material6,301 lines

  On-demand instruction bodies, web retrieval, attachment storage

How the agent acts on the world: reading and writing files, running commands, confining processes, sending out sub-tasks.

• Filesystem5,734 lines

  Opaque target identity, intent events, an atomic critical section

• Command Execution5,568 lines

  Request/spec split, process trees, output spill

• Sub-agents & Workflows18,566 lines

  One interface holding three kinds of child, plus a workflow engine

• Sandboxing8,696 lines

  Hand over the argv, get back an enforcement report; fail closed

The outward-facing side: typed RPC, editor and external-tool protocols, the browser UI.

• Typed RPC10,234 lines

  Extract a type graph at build time; both ends generate their own validators

• Protocol Bridges5,028 lines

  Translating foreign protocols into internal events, and back

• Browser UI82,337 lines

  Also a plugin tree — it just happens to run in a browser

This is where the product's shape is decided — as data, not code. It's also where the model can edit itself.

• The Patch Stack2,884 lines

  The product is a stack of patches over an empty list, not a program

• Session Presets1,783 lines

  Mounted once; sessions join it through scope parentage

• Runtime Self-Editing16,084 lines

  The model inspects the live runtime and mounts plugins it wrote

The plugin framework itself. 3,830 lines total, and the whole map rests on these two.

• Framework Core2,693 lines

  Contexts, fibers, service resolution, and registrations you can take back

• Config Loader2,129 lines

  YAML becomes a live plugin tree, plus hot reload

Not part of the runtime, yet probably the most portable part of all — plus the real bill this architecture runs up.

• Gates & Process29,981 lines

  Turning team convention into machine enforcement

• Costs & Weaknesses900 lines

  The real bill for this architecture, verified line by line