@zakza/dsh-dwf
用于 DeepSeek Harness 的确定性动态工作流引擎：TS-facade 编译器、重放日志、确定性来宾沙箱、参与者子代理、dwf 工作流工具
插件会安装到这里；不确定时保持 web。
npx -y @deepseek-ai/dsh plugin --profile web add github:Achi-Migo/dsh-dwf#cf8efe46a143002de34c7e5d46837a30f39f7898Dwf 以 @zakza/dsh-dwf 发布，当前版本为 0.1.1。Plugin Hub 会校验它的 manifest，并保存精确安装来源，便于复现安装结果。
Dynamic workflows for DeepSeek Harness — a workflow engine that replaces the
official workflowEngine slot with a compiled, replayable, resumable one.
dsh-dwf brings the ZCode-style workflow contract to DSH: a TypeScript-checked
script facade instead of plain JS, a replay journal in SQLite, a
deterministic guest sandbox, persistent actor subagents, and a
model pool that spreads load across providers and fails over on quota errors.
License: source-available, non-commercial, attribution required. See LICENSE and NOTICE. Commercial use needs written permission. This is not an OSI-approved open-source license.
| Capability | Detail |
|---|---|
| Typed workflow scripts | agent<T>() results are validated against a JSON Schema generated from a script-local TS interface — the facade is checked at compile time |
| Replay journal | Every run, event, node and actor is persisted in SQLite (dwf_run / dwf_event / dwf_node / dwf_actor); the model tool reads the same database the engine writes |
| Deterministic guest | Scripts run in a restricted realm: no Date.now(), no Math.random(), no filesystem, no network — a run can be replayed |
| Persistent actors | One agent() handle keeps its conversation across asks (FIFO per actor) |
| Model pool | Unbound actors spread across providers (spread or round-robin); deterministic provider failures cool down and fail over |
| Stall detection | A deadlocked or stalled script settles as a clean error instead of hanging the run |
| Background runs | run_in_background via the host job registry |
workflowEngine seam of
that release)dsh-dwf resolves its @deepseek-ai/* imports from the DSH host, so it must be
installed into a DSH profile — not into a bare project (a plain npm i
outside DSH leaves the peer packages unresolved, by design).
# from GitHub
dsh plugin --profile personal add github:Achi-Migo/dsh-dwf
# or from a packed tarball
npm pack && dsh plugin --profile personal add ./zakza-dsh-dwf-0.1.0.tgz
Then disable the official engine + tool so only one workflow surface is mounted
(add to $DSH_HOME/profiles/personal/cordis.patch.yml):
- id: workflow-ptc
disabled: true
- id: tool-workflow
disabled: true
The bundle patch (cordis.patch.yml in this package) inserts two rows:
dwf-engine (publishes the workflowEngine service) and dwf (registers the
dwf model tool). Both must point at the same dbPath — that database is
the single source of truth shared by engine and tool.
Set dbPath explicitly in your profile layer; an empty value means ./dwf.db
relative to the host process cwd:
- id: dwf-engine
config:
toolName: dwf
dbPath: /absolute/path/to/dwf.db
modelPool: 'providerA/model-x,providerB/model-y'
Config fields: toolName, dbPath, maxConcurrency, maxTotalAgents,
maxResultChars, enableRunInBackground, modelPool, poolPolicy
(spread | round-robin), poolCooldownMs, failoverAttempts.
The model calls the dwf tool with a script. Scripts are TypeScript bodies with
top-level await and a final return:
phase("Review the changed files");
const reviewer = agent("reviewer", {
system: "You review code. Report only real defects.",
model: "providerA/model-x",
});
interface Review {
/** File the finding is in. */
path: string;
/** One sentence: what is wrong. */
problem: string;
/** low | medium | high */
severity: string;
}
const review = await reviewer.ask<Review>("Review src/parser.ts");
log(`found ${review.severity} issue in ${review.path}`);
await report(review);
return { ok: true, path: review.path };
Facade: agent / ask<T> / model / phase / log / report /
publishArtifact / channel / future / world (run, read) /
files (glob, read, grep) / git (changedFiles, diff, status,
log) / args / hole.
Verified on Windows + Node 24.20.0 against DSH 0.2.1-rc.3 in a personal
profile, with a real host boot and journal reconciliation:
dsh-workflow-gate coexistence: the gate's verdict equals the command exit
code, no model involvedKnown boundaries (deliberate deferrals, not bugs):
amend/resume caching and SaveWorkflow are placeholdersreport items
and artifact rows are recorded in the journal insteadhole() answers with a deterministic "unavailable" error rather than parking
the runsrc/compile/ TS → JS lowering, facade checking, JSON Schema, phase graph
src/engine/ engine, run lifecycle, scheduler, actor pool, effects, artifacts
src/journal/ SQLite schema, store, projection, caps
src/guest/ deterministic realm, prelude, channel primitives, protocol
src/tool/ model-facing tools (create/get/list, mirror, recorder)
assets/ facade declaration, guest templates, journal DDL
test/ smoke, stub-check, compile/engine/tool/pool/integration suites
Provenance, upstream projects and required attribution are in
NOTICE. In short: dsh-dwf is an independent reimplementation of
ZCode's dynamic-workflow runtime, built on the DeepSeek Harness plugin
contract. It redistributes no ZCode code and no @deepseek-ai/* package.
Issues and pull requests are welcome for non-commercial purposes. By contributing you agree your contribution is licensed under LICENSE. Keep the NOTICE intact.