Coder/deepseek-harness
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

docs: clarify package hierarchy example

Browse Source
This commit is contained in:
Tianyi Cui
2026-06-20 21:36:49 +08:00
parent 800e08e930
commit c079b74c78
1 changed files with 9 additions and 7 deletions
Download Patch File Download Diff File Expand all files Collapse all files

16
docs/rfc/proposed/2026-06-20-package-hierarchy.md
View File

@@ -17,30 +17,32 @@ One plausible shape:
```text ```text
packages/ packages/
core/ core/
llm/
session/ session/
system-prompt/ system-prompt/
tools/ tools/
agent/ agent/
agent-loop/ agent-loop/
invariants/ invariants/
capabilities/ llm/
llm/
adapters/
llm-deepseek/
llm-pi-ai/
bash/
bash/ bash/
bash-local/ bash-local/
tool-bash/ tool-bash/
session-persistence/
session-persistence/ session-persistence/
session-persistence-jsonl/ session-persistence-jsonl/
session-persistence-sqlite/ session-persistence-sqlite/
integrations/ acp/
llm-deepseek/
llm-pi-ai/
acp/
support/ support/
ui-stdio/ ui-stdio/
llm-replay/ llm-replay/
``` ```
The final implementation may choose different names or groupings, but it should keep the same intent: core APIs, capability seams, concrete integrations, and support/test/example packages are distinguishable from the filesystem alone. Npm package names can stay `@deepseek-ai/dsh-*`; the hierarchy is about repo structure and maintenance policy, not public package renaming. The final implementation may choose different names or groupings, but it should keep the same intent: core APIs, package families such as LLM/bash/session persistence, standalone integrations such as ACP, and support/test/example packages are distinguishable from the filesystem alone. Npm package names can stay `@deepseek-ai/dsh-*`; the hierarchy is about repo structure and maintenance policy, not public package renaming.
This proposal does not delete `llm-replay` or `ui-stdio` by itself. It makes their status honest: either they graduate into product packages with documented consumers, or they live under a support/testing/example classification where release and compatibility expectations are lower. This proposal does not delete `llm-replay` or `ui-stdio` by itself. It makes their status honest: either they graduate into product packages with documented consumers, or they live under a support/testing/example classification where release and compatibility expectations are lower.