Skip to content

The upstream repo ships an unusually complete documentation tree under docs/. This appendix maps every top-level Markdown file and subdirectory — what it covers and who should read it — so you can navigate from this site back to the authoritative source.

The i18n convention

Every in-scope document is maintained in English and Simplified Chinese as a pair plus a translation index (the one exception is docs/cordis-api/inherited.md, which is English-only):

  • <name>.md — English source.
  • <name>.zh.md — Chinese translation, a faithful non-literal rendering.
  • <name>.i18n.yaml — the i18n pairing/paths declaration.

The contract, checks, scope, and exclusions live in docs/i18n/README.md; how to translate is in docs/i18n/translation-rules.md; the terminology source of truth is docs/i18n/terminology.md. docs/AGENTS.md is the documentation writing standard that governs this whole tree.

Top-level overview and architecture

Repo pathWhat it coversWorth reading for
docs/architecture.mdRead-before-hacking overview: Cordis, profiles/bundles/patches, core packages, events, turn flow, session log, seamsArchitecture overview, capability seams
docs/glossary.mdCanonical one-term-per-concept domain vocabularyGlossary appendix
docs/cordis-primer.mdThe Cordis ideas a plugin author needs before the generated referencesCordis primer
docs/rescope.mdName mapping for the vendored @deepseek-ai/cordis* scopePackage index

Development

Repo pathWhat it coversWorth reading for
docs/development.mdContributor setup tutorial plus repo layout, daily workflow, CI organizationDevelopment
docs/AGENTS.mdThe documentation writing standard: structure, Markdown tiers, budgetsPage conventions (see docs/AGENTS.md)
docs/testing.mdTesting policy tier by tier and the rules that keep the suite meaningfulTesting
docs/defensive-patterns.mdBug-class rules (events, concurrency, lifecycle, subprocess, teardown) that actually shippedDevelopment
docs/event-producer-consumer.mdGenerated matrix of every event's producers and consumersEvents
docs/module-graph.mdGenerated package-level module dependency graphPackage index
docs/graph-atlas.mdGenerated index of all documentation graphsArchitecture overview
docs/web-styling.mdStyling ownership and component rules for browser client packagesWeb UI

Catalogs (generated reference)

Repo pathWhat it coversWorth reading for
docs/tool-catalog.mdGenerated schema catalog of every model-facing toolTool registry
docs/config-catalog.mdGenerated plugin config catalogConfiguration
docs/persistence-catalog.mdGenerated session persistence event catalogSession
docs/api-gateway.mdCurrent-state reference for the Typert API Gateway (Remote methods, Host/Client contracts)Host API
docs/capability-seams.mdGenerated page of every capability seam and core serviceCapability seams
docs/tool-execution-pipeline.mdGenerated page of the tool execution pipelineTools
docs/agent-lifecycle.mdGenerated agent turn-and-step lifecycle diagramAgent loop

Subsystem references (docs/subsystems/)

45 subsystem pages — core, session, tools, shell, fs, subprocess, sandbox, llm-streaming, session-projection, session-query, session-telemetry, session-title, settings, credentials, persistence, approval, permission-presets, user-questions, commands, plan, goal, schedule, jobs, workflow, subagent, skills, system-prompt, compaction, spill, storage, lsp, web, web-server, terminal, feedback, extensions, client-modules, typert, invariants, scope and more. Each is a plugin-territory reference (service, events, config, providers) for one package group.

Repo pathWhat it coversWorth reading for
docs/subsystems/README.mdIndex of all subsystem referencesSubsystem index (see docs/subsystems/README.md)
docs/subsystems/core.mdAgent, agent-loop, system-prompt registerAgent loop
docs/subsystems/session.mdThe event-sourced session storeSession
docs/subsystems/scope.mdThe scoped-registration primitiveScope
docs/subsystems/goal.mdSame-session goals and goal roundsGoals
docs/subsystems/...One reference page per package group (see README index)Per subsystem

Cordis API and tutorial (docs/cordis-api/, docs/cordis-tutorial/)

Generated catalog of the vendored Cordis framework surface (context, events, fiber, registry, service, plus inherited.md), and a hands-on 7-lesson tutorial (first plugin → lifecycle/effects → services → events → config → composition/HMR → into the harness).

Repo pathWhat it coversWorth reading for
docs/cordis-primer.mdConcept primer before the generated referencesCordis primer
docs/cordis-api/context.mdCordis Context APICordis
docs/cordis-api/events.mdCordis typed event APIEvents
docs/cordis-api/service.mdCordis Service APICordis
docs/cordis-api/fiber.mdCordis fiber modelCordis
docs/cordis-api/registry.mdCordis registry APICordis
docs/cordis-api/inherited.mdInherited generated API surfaceCordis
docs/cordis-tutorial/index.mdHands-on introduction in seven lessonsCordis tutorial

Cookbook (docs/cookbook/)

Repo pathWhat it coversWorth reading for
docs/cookbook/adding-a-package.mdHow to add a workspace packageExtension cookbook (see docs/cookbook/extension-cookbook.md)
docs/cookbook/adding-a-tool.mdTool authoring referenceTools
docs/cookbook/adding-an-llm-adapter.mdHow to add an LLM adapterLLM
docs/cookbook/adding-a-vendored-package.mdHow to add a vendored packageVendored packages
docs/cookbook/adding-a-conversation-node.mdAdd a Web Client conversation nodeWeb UI
docs/cookbook/extension-cookbook.mdExtension plugin shapes (features → capabilities index)Extension cookbook (see docs/cookbook/extension-cookbook.md)
docs/cookbook/maintaining-dsh-code-review.mdMaintaining the dsh-code-review skillDevelopment
docs/cookbook/responding-to-pr-review-on-a-stack.mdResponding across a stacked PR chainDevelopment

User guides (docs/user/)

Three sub-trees: guide/ (Web UI usage, providers/models, Python SDK), develop/ (basic plugin → service framework → three-role practice), and the top-level index.md (redirect).

Repo pathWhat it coversWorth reading for
docs/user/index.mdRedirect to the Web UI quickstartQuickstart
docs/user/guide/index.mdUsing the Web UI after server startWeb UI
docs/user/guide/providers.mdConfiguring models and providersModels
docs/user/guide/python-sdk.mdGetting started with the Python SDKSDK
docs/user/develop/basic/index.mdYour first plugin, loaded into the Web UIFirst plugin (see docs/user/develop/basic/)
docs/user/develop/framework/index.mdCordis plugin model and lifecycle state machineDevelop framework (see docs/user/develop/framework/)
docs/user/develop/practice/index.mdThree-role capability design, concept + advanced tutorialCapability seams

docs/user/develop/basic/ covers tool.md, config.md, publish.md; docs/user/develop/framework/ covers service.md and events.md; practice has an llm-adapter.md.

Post-mortems (docs/postmortem/)

Repo pathWhat it coversWorth reading for
docs/postmortem/README.mdIndex of incident post-mortemsPost-mortems (see docs/postmortem/README.md)
docs/postmortem/0001-*.mdACP default-export drops injectExtensibility
docs/postmortem/0002-*.mdJS expression disabled filesystem toolsFilesystem
docs/postmortem/0003-*.mdWeb agent GUI feedback loopWeb UI
docs/postmortem/0004-*.mdLandlock partial notice misclassified child failuresSandbox

There are four numbered post-mortems at this revision (00010004).

Further reading

  • Package index — maps each doc to the packages it describes.
  • Glossary — the vocabulary the upstream docs assume.
  • docs/README.md-level scaffolding lives in docs/*.md (repo-relative).
  • docs/i18n/README.md — the bilingual pairing contract (repo-relative).