dsh-reckoner
DSH 插件：确定性计算引擎——数值、公式、量纲分析和逐步记录
插件会安装到这里；不确定时保持 web。
npx -y @deepseek-ai/dsh plugin --profile web add github:curtainsmall/dsh-reckoner#4a0bcdbd39aadb1deed190320d42f01799f59dc8Reckoner 以 dsh-reckoner 发布，当前版本为 0.1.0。Plugin Hub 会校验它的 manifest，并保存精确安装来源，便于复现安装结果。
点击下方 Badge 复制 Markdown，粘贴到 README 即可。
验证 package.json 声明的 GitHub 仓库，即可管理这个公开页面。认领后，Hub 会优先安排当前版本的安全扫描，并在通过后公开展示结果。
认领这个 Plugin →A deterministic calculation engine for the DeepSeek Harness: the model writes every formula, the engine owns the numerical rules.
dsh plugin --profile <profile> add dsh-reckoner
Install a local checkout by path instead: dsh plugin --profile <profile> add link:<path>.
dsh-reckoner to the profile's dsh.profile.bundles.dsh.bundle.patch, cordis.patch.yml.The package ships two agent presets. A session picks one when it is created: the pure reckoner preset, unless the question needs a fact from outside. A session that has produced anything cannot change its preset.
| preset | id | sandbox | outside lookup |
|---|---|---|---|
| Reckoner | reckoner | six plugin tools, no network | none |
| Reckoner with search | reckoner-with-search | the same six tools plus search | one fact at a time, written into the record with its sources |
set, or a result produced by evalThe engine inside a record is optional: set and eval carry the parts that need numbers, and a question that needs none is answered through the record's own messages.
search, and nothing elseweb_search and web_fetch are mounted by neither presetThe record keeps what the model does not see: the question, every candidate source the provider returned, the sources the policy allowed, and the route and prompt version of the extractive step that wrote the answer. The retrieval policy is the preset row's config: the strict tier keeps only an allow-list of reference hosts, and a record carries at most four lookups by default.
Each plugin mount copies both preset directories into $DSH_HOME/.agent-presets/. Each preset contributes the persona only, because the plugin itself is mounted globally by the bundle patch.
One engine runs per host process, and every session's calls act on it. It is a calculator with no domain knowledge: no solver, no registry, no named formula. The model writes a formula that says how the units combine, and the engine checks those units while it evaluates, so a dimension that does not add up is refused rather than answered.
| tool | effect |
|---|---|
set | writes one slot; value: null deletes it |
get | reads one slot back; the only way to read a value |
eval | writes one formula's result into the target slot |
record_start / record_message / record_end | open, annotate and close a record |
dim names it, as a table name such as ohm or as the 7 integers.+ - * / ^, a set of $ functions and sums; no comparison, no logic, no assignment.{ok: true, ...} or {ok: false, code, error}. A refusal changes nothing.The whole reference - the value types, the notation, the dimension rules, the record on disk and the HTTP paths - is in the engine manual (简体中文).
A record is the process of one calculation: its title, conditions, explanations, evaluation steps and optional closing text.
| marker | effect | refused when |
|---|---|---|
record_start {title} | opens a record | a record is already open |
record_message {text, hide?} | one explanation, as many as the work needs | never |
record_end {text?} | closes the record and writes it to disk | no record is open |
hide: true keeps a message out of the record view while the article writer still receives it. set, get and eval are refused while no record is open, and closing a record clears the slot table, so the table is non-empty exactly while a record is open.
<home>/open-record.jsonl; closing renames that file into <home>/records/<id>.jsonl, so a closed record is always complete.The Reckoner panel is the sidebar entry of the same name. It has two tabs.
Every closed record can be written up as a standalone article. A host-side LLM call receives the record's facts as plain text: the title, the conditions still standing, the explanations and evaluation steps interleaved in seq order, and the closing text, with numbers cut to at most four decimal places and hide: true messages presented as author's notes the writer must not print. The product name appears only in the fixed title DeepSeek Harness Reckoner Solution and the fixed author line.
| format | output |
|---|---|
| Markdown | a flat .md file, never compiled |
| LaTeX | a .tex source in a folder named after the file, compiled to PDF when requested |
Each format remembers its own output directory and language, and LaTeX remembers whether to compile: the setup dialog opens with what its format remembers, and the Settings tab edits the same values. The file name is prefilled from the record identifier. PDF compilation is delegated to latexmk or MiKTeX's texify and needs the xelatex engine; with compilation requested and no usable driver or engine, Generate is disabled and the dialog names what is missing.
| setting | meaning |
|---|---|
DSH_RECKONER_HOME | the plugin home, ~/.dsh-reckoner by default |
DSH_RECKONER_LOG_LEVEL | debug, info, warn, error or off; the default is info |
The home holds the unclosed record (open-record.jsonl), the closed records (records/<id>.jsonl), the plugin state and the logs (logs/<YYYY-MM-DD_HH-mm-ss.SSS>.log, one per plugin mount). The state file, state.json, is a tree with one subtree per module that remembers settings, plus the flat restartRequired marker.
| document | content |
|---|---|
| Engine manual (简体中文) | the long-form engine reference |
| reckoner-interface, reckoner-template | the manual the agent reads in Reckoner Mode |
| Contributing (简体中文) | setup, commit conventions, release process |
MIT. Copyright (c) 2026 curtainsmall