📑 dsh-research-report
- 1024 store channel:
npm i -g dsh1024 once, then dsh1024 plugin --profile web add dsh-research-report (counts toward the deepseek1024.com install ranking).
OpenSSF Scorecard
A verifiable research-report engine for DeepSeek Harness.
Every claim is bound to immutable evidence snapshots, verified byte-for-byte, and sealed into a versioned report whose manifest hash anyone can recompute.
DSH Market
English · 简体中文 · Español · Português · हिन्दी
dsh plugin --profile <name> add dsh-research-report
📖 Ecosystem knowledge base — measured data, not marketing: plugin development guide · plugin-selection data · maintenance criteria.
Install & uninstall
dsh plugin --profile demo add dsh-research-report # install
dsh plugin --profile demo remove dsh-research-report # uninstall
Verify the row mounts: dsh --profile demo --dump-config | grep dsh-research-report.
⭐ 如果它帮到了你
这个插件是 DSH 插件家族的一员（95 个，全部 Apache-2.0）。如果你在用，给个 star —— 它不会解锁任何功能，但会让下一个人在搜索里更容易找到它。
English: part of a 95 plugin family for DeepSeek Harness. If it is useful, a star helps the next person find it — nothing is gated behind it.
What is dsh-research-report?
A verifiable research-report engine for DeepSeek Harness.
Every claim is bound to immutable evidence snapshots, verified byte-for-byte, and sealed into a versioned report whose manifest hash anyone can recompute.
Workflow diagram for dsh-research-report: question → sealed sources → report.
Workflow overview: question → sealed sources → report. The examples below use the real command surface.
Compatibility
- DeepSeek Harness
dsh-v0.2.1-alpha.1 (verified 2026-09-25). npm dev/test line 0.1.7-rc.2; peers >=0.1.6-0 <0.2.0 || >=0.1.7-0 <0.2.0. The compat matrix pins all four declared peer lines. On this line Session.append's third parameter is a SurfaceIntent for surface-eligible types only, so research-report/* events still do not land in the session log: the ledger journals are the durable source of truth and the audit mirror activates only once a host knows the vocabulary (the regression lock in test/events-gate.spec.ts pins that).
0.1.5-alpha.1 (adapted 2026-09-09): the session envelope keeps its ignorable field for stored-log read compatibility only - Session.append still cannot stamp it, so audit-gate behavior is unchanged. Verified 2026-09-11 against the published 0.1.5-rc.2 types (full local gate chain); the compat workflow pins both declared peer lines.
- Node
^22.19.0 || >=24.0.0, ESM only ("type": "module").
- Peer dependencies:
@deepseek-ai/cordis ^4.0.2, @deepseek-ai/schemastery ^3.18.2, and @deepseek-ai/dsh-session, @deepseek-ai/dsh-tools, @deepseek-ai/dsh-system-prompt, @deepseek-ai/dsh-web, @deepseek-ai/dsh-jobs at >=0.1.6-0 <0.2.0 || >=0.1.7-0 <0.2.0.
- Optional siblings (never required):
ctx.web providers for URL capture/gather, ctx.jobs for background assembly, ctx.dataQuality (dsh-data-quality) for dataset citation cross-checks.
What you get
- Evidence ledger — a content-addressed snapshot store (
<ledgerRoot>/objects/<sha256> + JSONL journals). The same content is stored exactly once; snapshots are immutable; every read recomputes the hash, so tampering or deletion is detected instead of trusted.
- Claim ↔ evidence binding — claims register with the evidence ids they rely on; the ledger keeps the binding and every verification verdict (latest wins).
- Byte-level verification — every number and quoted span in a claim must be locatable verbatim in the bound snapshots. No bound evidence, or no checkable literal, marks the claim
unverified; bound evidence that cannot confirm or deny the claimed literals marks it insufficient; a label whose snapshot value differs (the claimed value absent) marks it disproven; tampered/missing snapshots mark it contradicted. No semantics, no embeddings — auditable byte checks.
- Optional numeric bridge — when a claim cites a structured workspace dataset (CSV/JSON) and
dsh-data-quality is mounted, citations are cross-checked with tolerances through its frozen verifyCitations contract; a dataset mismatch disproves the claim.
- DOI evidence (zero network) — DOI origins are validated deterministically (
10.xxxx/xxxx structure, a prefix whitelist, and a DOI character set); invalid DOIs fail loud. Optional journal/year metadata is accepted, and requireJournalMetadata gates academic DOI evidence only when enabled.
- Versioned sealed reports —
<reportRoot>/<slug(topic)>/<YYYYMMDD-HHmmss>/report.md + manifest.json + verification.jsonl + disconfirmation.jsonl; the seal hash is the SHA-256 of the manifest, which itself carries the report hash, every evidence hash, and the hash of each audit journal.
- Pre-delivery re-audit & seal interception — before sealing, every bound claim is re-verified offline and journaled to
verification.jsonl; verdict drift, tampered/missing bound evidence, or a journal serialization failure blocks the seal (fail loud, no tunable).
- Falsification ledger — every contradicted or disproven claim is recorded in
disconfirmation.jsonl (claim + evidence references + reason) and listed in the report's falsification log appendix.
- Negative knowledge — a disproven claim is remembered by its content hash (
disproofs.jsonl); the same text re-reported against unchanged evidence is forced back to disproven and only re-verifies once the evidence changes.
Quick start
dsh plugin --profile web add github:PerryLink/dsh-research-report
git channel
# From a scratch profile (pins the commit; runs the self-contained `prepare` build)
dsh plugin --profile demo add "github:YOUR_ORG/dsh-research-report#<sha>"
# The profile's pnpm-workspace.yaml gains an allowBuilds entry for dsh-research-report on first add.
npm channel
dsh plugin --profile demo add dsh-research-report
Both channels install the bundle row (see cordis.patch.yml) into the profile's dsh.profile.bundles stack and take effect on restart.
Then, in a session:
evidence_add({ origin: "docs/market.md", title: "Market snapshot" }) # → ev-1a2b3c4d5e6f
research_report({ topic: "示例行业概览", sections: [...], claims: [...], evidenceRefs: ["ev-1a2b…"] })
ledger_query({ claimId: "c1" }) # bindings + verdict
Examples
These are the plugin's real entry points; install once, then call one.
Detailed example
Command
research_report({
topic: "示例行业概览",
sections: [{ heading: "市场规模", paragraphs: [{ text: "2025 年全球示例行业市场规模为 1,280 亿元。", claimIds: ["c1"] }] }],
claims: [{ id: "c1", text: "市场规模为 1,280 亿元", evidenceIds: ["ev-5dc0a84d0e48"] }],
evidenceRefs: ["ev-5dc0a84d0e48", "ev-c6cf024e0916", "ev-61f8f4533cb7"]
})
Output
report sealed: /tmp/rr-test-4U2mlF/reports/示例行业概览/20261019-124904
seal (sha256 of manifest.json): 5c85c97597096ced281ca191d7abaaf7434f18b397d35ac81c31aa364a3b12f9
claims: 1 verified / 0 unverified / 0 contradicted / 0 insufficient / 0 disproven (of 1); evidence bound: 3
Observed from README.md:112-118,150; test/index.spec.ts:166-177; src/tools/research-report.ts:170-175
Failure branch
Input
{"topic":"probe","sections":[{"heading":"Growth","paragraphs":[{"text":"Growth was 42%.","claimIds":["c1"]}]}],"claims":[{"id":"c1","text":"Growth was 42%.","evidenceIds":[]}]}
Output
edge-case (no throw): isError=false; kind=sealed; verdicts[0]={"claimId":"c1","status":"unverified","note":"claim binds no evidence snapshot"}; counts={"verified":0,"unverified":1,"contradicted":0,"insufficient":0,"disproven":0}; evidenceCount=0; report.md marker=Growth was 42%. [未核实]
Observed from plugins/dsh-research-report/src/verify.ts:173-175 (unverified verdict); plugins/dsh-research-report/src/assemble.ts:209-220 (visible mark); plugins/dsh-research-report/README.md:87 (honest gaps); exercised through plugins/dsh-research-report/test/harness.ts
Brief examples
research_reportledger_query
Configuration
All tunables are Schemastery Config fields; invalid values fail the profile load loudly. Relative roots resolve against the harness working directory (the workspace).
| Key | Default | Description |
|---|
enabled | true | Master switch; false mounts nothing. |
ledgerRoot | .research-ledger | Evidence-ledger directory (objects + JSONL journals). |
reportRoot | research-reports | Sealed-report root (versioned per topic and timestamp). |
workspaceRoot | (host session working directory) | Root for workspace-path evidence; defaults to the session working directory, then the harness cwd. |
maxEvidenceBytes | 2097152 | Hard cap on one evidence snapshot's UTF-8 bytes. |
maxEvidencePerReport | 200 | Hard cap on evidence items bound into one report. |
fetchTimeoutMs | 20000 | Deadline (ms) for one ctx.web fetch during capture. |
requireJournalMetadata | false | When true, DOI-typed evidence must carry a journal name and publication year at registration (fails loud otherwise). |
Tools & surfaces
evidence_add({ origin, content?, title? }) — register one evidence snapshot. With content the text is stored verbatim; without it a URL origin is fetched through ctx.web and a workspace-relative path is read from disk (reads never escape the workspace). Returns the evidence id and SHA-256 hash.research_report({ topic, title?, sections, claims, evidenceRefs, gather?, depth?, background? }) — assemble and seal a report: validate (unregistered claim references are rejected loudly), verify every claim, render report.md with visible markers, write manifest.json, and return the seal hash. gather: true runs ONE search round over ctx.web and returns captured candidate evidence plus an explicit gap list — it never auto-assembles. background: true returns { kind: 'background', jobId } over ctx.jobs.ledger_query({ claimId? | evidenceId? }) — read-only binding/verdict queries; evidence is re-hashed on read so a tampered or missing snapshot is reported explicitly. With no id, returns a ledger summary.ctx.researchReport.assemble(request) — the frozen service surface for sibling plugins (see src/service.ts; gated byte-for-byte by scripts/verify-frozen-contract.mjs).
Permissions & data
dsh-research-report consumes only public seams: ctx.tools, ctx.systemPrompt, and optionally ctx.web / ctx.jobs / ctx.dataQuality (looked up at call time, never injected). It writes only inside the configured ledger and report roots (both default to workspace-local directories), reads workspace files only inside the workspace, and reaches the network exclusively through the harness web seam — never a direct fetch. Evidence snapshots are immutable and content-addressed; claim registrations are immutable; verdicts are append-only.
Security boundaries
- Tamper-evidence by construction — every snapshot read recomputes SHA-256 against the index; a mismatch verifies the bound claims
contradicted and ledger_query reports integrity: tampered/missing.
- Workspace confinement — local evidence reads resolve against the workspace root and refuse escapes (both sides are
path.resolved before comparison).
- Fail-loud configuration — invalid bounds throw at mount; unregistered claim references, unknown evidence ids, and id/content conflicts throw at assemble.
- No credential handling, no hidden network — URL capture rides
ctx.web (provider selection, error taxonomy, and any SSRF policy stay with the deployment's web providers).
- Reversible registrations — every contribution goes through
ctx.effect() / register(), so uninstall and hot reload are clean.
Known limitations
- Byte-level, not semantic — the built-in check locates number/quote literals verbatim; paraphrased claims without a checkable literal verify as
unverified, and a true claim whose number is absent while its label appears with a different value reads contradicted. This is a deliberate v1 choice (auditable beats clever).
- Session events are adaptive — the plugin declares typed
research-report/evidence, research-report/verify, and research-report/seal session events, but the 0.1.5-alpha.1 Session.append still exposes no ignorable option and no plugin event-registration surface, so appends activate only when the host build knows the types (otherwise the persistence layer would refuse the log on restore). The ledger journals are always the durable source of truth.
- Default profiles mount no fetch provider — the shipped
dsh-base mounts search only, so URL capture fails loud (WEB_UNAVAILABLE/WEB_PROVIDER_UNAVAILABLE) until a fetch provider is configured; search-based gather lists uncaptured sources in the gap list.
- Single-workspace scope — ledger and report roots resolve against the harness working directory at mount; multi-workspace deployments should configure absolute roots per profile.
Verifier CLI
The standalone dsh-research-verify binary (bundled as lib/cli.js, zero @deepseek-ai imports) audits any sealed report directory without mounting the plugin:
dsh-research-verify --report <dir> [--seal <sha256>] [--ledger <dir>] [--format json|sarif]
--report <dir> — the sealed report directory (manifest.json + report.md + the audit journals).--seal <sha256> — the expected seal hash to compare the recomputed manifest hash against. Omitted = the recomputed hash is reported without comparison.--ledger <dir> — the evidence ledger root (objects/<sha256> + index.jsonl) enabling per-claim byte-level re-checks. Omitted = claim re-checks are skipped honestly.--format — json (default) or sarif (SARIF 2.1.0).
It recomputes the seal hash (SHA-256 of manifest.json), the report.md hash, and the audit-journal hashes, re-runs the byte-level + integrity check for every claim, and exits non-zero when any performed check fails. The same verifySealedReport / buildVerificationReport / renderSarif / renderVerificationJson functions are exported from the package for library use.
Development
pnpm install
pnpm run typecheck && pnpm run typecheck:ci
pnpm test
pnpm run build
pnpm run verify:self-contained && pnpm run verify:artifacts
node scripts/check-readme-sync.mjs
node scripts/verify-frozen-contract.mjs
pnpm pack
typecheck resolves @deepseek-ai/* through the installed 0.1.7-rc.2 peers; typecheck:ci clears skipLibCheck and enables verbatimModuleSyntax against the published types. Both must stay green.- Tests use the real
Context/Session/ToolRuntime/LocalJobRegistry/WebRuntime from the 0.1.7-rc.2 peers; only network backends are scripted providers registered through the real ctx.web registries.
- Release:
node scripts/release.mjs <x.y.z> (bumps, stamps CHANGELOG, re-runs the gate, commits + tags; never pushes).
Topics
dsh, dsh-plugin, deepseek-harness, cordis, research, evidence-ledger, verifiable-report, audit, citation-verification
Contributors
- PerryLink — original author and maintainer: plugin architecture, evidence ledger, byte-level verification, sealed reports, five-language documentation, CI and release automation.
PerryLink DSH Plugin Family
This project is part of the DeepSeek Harness plugin family from PerryLink. The roster stays collapsed below so every README keeps a short first screen; expand it to see every row and its status.
Expand all plugins
License
Apache-2.0 — see LICENSE.
