Busabase x Knowledge Base for DeepSeek HarnessKnowledge Base for DeepSeek Harness
DeepSeek Harness is an open-source agent harness built around an everything-is-a-plugin architecture. Plugin composition makes capability flexible; it does not make a tool result, runtime state, or agent conclusion a durable fact for the rest of the company.
MAP
Treat a Harness composition as a runnable system, then promote only an evidence-backed conclusion to shared knowledge.
DeepSeek Harness is an open-source agent harness built around an everything-is-a-plugin architecture. Plugin composition makes capability flexible; it does not make a tool result, runtime state, or agent conclusion a durable fact for the rest of the company.
Plugins, services, lifecycle wiring
Creation, resume, cancellation, result return
Shell, file, web, MCP or plugin capabilities
Owner, claim, evidence, freshness
01 · Knowledge Base for DeepSeek Harness
Cordis plugin composition
DeepSeek Harness is an open-source agent harness built around an everything-is-a-plugin architecture. Plugin composition makes capability flexible; it does not make a tool result, runtime state, or agent conclusion a durable fact for the rest of the company.
| Layer | Owns | Boundary |
|---|---|---|
| Cordis composition | Plugins, services, lifecycle wiring | A runtime configuration, not an approved policy |
| Agent lifecycle | Creation, resume, cancellation, result return | Execution history, not reusable truth |
| Tool surface | Shell, file, web, MCP or plugin capabilities | Observed output still needs validation |
| Busabase record | Owner, claim, evidence, freshness | Canonical only through a Change Request |
02 · Knowledge Base for DeepSeek Harness
developer preview with breaking changes
Treat a Harness composition as a runnable system, then promote only an evidence-backed conclusion to shared knowledge.
A plugin is executable code with its own lifecycle and dependencies.
The official project labels the product developer preview and warns of compatibility-breaking changes.
A successful call proves a response occurred, not that its interpretation is correct.
A shared result names the accountable owner and the conditions under which it stays valid.
03 · Knowledge Base for DeepSeek Harness
AGENTS.md, tools, configuration, and lifecycle documentation
Knowledge Base for DeepSeek Harness: Cordis plugin composition; developer preview with breaking changes; AGENTS.md, tools, configuration, and lifecycle documentation.
Cordis compositionPlugins, services, lifecycle wiring. A runtime configuration, not an approved policyAgent lifecycleCreation, resume, cancellation, result return. Execution history, not reusable truthTool surfaceShell, file, web, MCP or plugin capabilities. Observed output still needs validationBusabase recordOwner, claim, evidence, freshness. Canonical only through a Change RequestEVIDENCE
Knowledge Base for DeepSeek Harness: inspect the execution boundary
PLUGIN: A plugin is executable code with its own lifecycle and dependencies. PREVIEW: The official project labels the product developer preview and warns of compatibility-breaking changes. TOOL: A successful call proves a response occurred, not that its interpretation is correct. RECORD: A shared result names the accountable owner and the conditions under which it stays valid.
deepseek-harness_1Cordis composition: Plugins, services, lifecycle wiring; A runtime configuration, not an approved policydeepseek-harness_2Agent lifecycle: Creation, resume, cancellation, result return; Execution history, not reusable truthdeepseek-harness_3Tool surface: Shell, file, web, MCP or plugin capabilities; Observed output still needs validationdeepseek-harness_4Busabase record: Owner, claim, evidence, freshness; Canonical only through a Change Request
ACCEPTANCE
Knowledge Base for DeepSeek Harness: execution is not acceptance
Treat a Harness composition as a runnable system, then promote only an evidence-backed conclusion to shared knowledge.
A plugin is executable code with its own lifecycle and dependencies.
The official project labels the product developer preview and warns of compatibility-breaking changes.
A successful call proves a response occurred, not that its interpretation is correct.
A shared result names the accountable owner and the conditions under which it stays valid.
PLACEMENT
Knowledge Base for DeepSeek Harness: keep context with its owner
Cordis composition owns Plugins, services, lifecycle wiring. Agent lifecycle owns Creation, resume, cancellation, result return. Tool surface owns Shell, file, web, MCP or plugin capabilities. Busabase record owns Owner, claim, evidence, freshness.
| Layer | Owns | Boundary |
|---|---|---|
| Cordis composition | Plugins, services, lifecycle wiring | A runtime configuration, not an approved policy |
| Agent lifecycle | Creation, resume, cancellation, result return | Execution history, not reusable truth |
| Tool surface | Shell, file, web, MCP or plugin capabilities | Observed output still needs validation |
| Busabase record | Owner, claim, evidence, freshness | Canonical only through a Change Request |
FRESHNESS
Knowledge Base for DeepSeek Harness: record what can change
PLUGIN: A plugin is executable code with its own lifecycle and dependencies. PREVIEW: The official project labels the product developer preview and warns of compatibility-breaking changes. TOOL: A successful call proves a response occurred, not that its interpretation is correct. RECORD: A shared result names the accountable owner and the conditions under which it stays valid.
source_versionhttps://github.com/deepseek-ai/deepseek-harnessruntime_factCordis plugin composition | developer preview with breaking changes | AGENTS.md, tools, configuration, and lifecycle documentationreview_ownerAccountable human reviewernext_reviewA stated recheck boundaryFAQ
Knowledge Base for DeepSeek Harness: practical questions
Treat a Harness composition as a runnable system, then promote only an evidence-backed conclusion to shared knowledge.
Does a plugin configuration become shared knowledge?
No. It is a runnable setup. Capture the intended decision, evidence, owner, and recheck date separately.
Does a completed agent run prove the conclusion?
No. It provides provenance. Tests, source-system readback, and an accountable owner decide whether to reuse it.
Can a developer-preview configuration be canonical?
Only as a versioned, time-bounded claim with a clear verification point because the project warns of breaking changes.
Does MCP make external data trusted?
No. MCP exposes a capability. Preserve the server identity and verify the returned evidence.
NEXT
Treat a Harness composition as a runnable system, then promote only an evidence-backed conclusion to shared knowledge.
DeepSeek Harness is an open-source agent harness built around an everything-is-a-plugin architecture. Plugin composition makes capability flexible; it does not make a tool result, runtime state, or agent conclusion a durable fact for the rest of the company.