dsh-research-report plugin
DeepSeek Harness plugin: a research report where each claim binds to a source snapshot and a SHA-256 seal can be checked offline
- 214 ★ on the repository
- Last commit
- Apache-2.0
Extended access
Why this level
- Reads workspace files and fetches pages by URL through the Harness, and writes the `.research-ledger` and `research-reports` directories
Install
Manual install
dsh plugin --profile web add dsh-research-reportNeeds DeepSeek Harness 0.1.6–0.3.0 and Node 22.19 or newer. Restart the Harness after installing.
Access and checks
How we reviewExtended accessThe tool runs code or makes network calls and only reads external data.
- Reads workspace files and fetches pages by URL through the Harness, and writes the `.research-ledger` and `research-reports` directories
This is third-party code. Review the repository files before installing.
What it does
dsh-research-report is a community plugin for DeepSeek Harness that turns a topic and a set of sources into a sealed report. The `evidence_add` tool stores a source as an immutable snapshot: text, a URL or a workspace file. The `research_report` tool takes sections, claims and snapshot references, checks every number and quote byte for byte against the bound snapshots and builds a report directory: `report.md`, `manifest.json`, `verification.jsonl` and `disconfirmation.jsonl`. The seal is the SHA-256 of `manifest.json`. A claim with no bound source or no checkable literal gets the `unverified` status, and a disproven one lands in the falsification log and an appendix. Gaps stay visible in the report body. Before sealing, all bindings are re-verified offline, and any drift blocks the release. The `ledger_query` tool shows bindings and the verdict for a claim. The `dsh-research-verify --report <dir>` command recomputes the seal on any machine with no network and no model. DOIs get a deterministic format check.
Who it is for. Analysts and researchers who build reports in DeepSeek Harness and want a reader to recompute each figure from a stored source.
Good fit when
- A report goes to a client who needs proof that figures and quotes match the sources
- A source may change later, so the snapshot is stored by content hash
- A claim has to be disproven and remembered so it does not return in the same report
- You want to recompute the seal of a finished report with `dsh-research-verify` and no network
Not a fit when
- You work in Claude Code, Cursor or Codex: the plugin targets DeepSeek Harness
- You need a deep-research loop: the plugin leaves search and synthesis to the model and `ctx.web`
- You want a quick-read report with no verification: sealing adds steps
Example request
Build a market report from three documents, bind every figure to a snapshot and seal the resultLimitations
- The plugin targets DeepSeek Harness 0.1.6 up to 0.3.0 and Node 22.19 or 24.9 and newer. It does not work with other agents.
- The author states it is a community plugin unaffiliated with DeepSeek. The Gitee repository is a mirror.
- Byte-level checking finds a number or quote in the snapshot text but does not judge whether the source itself is right. The call on meaning stays with a person.
- URL fetching goes through the Harness `ctx.web`, so page availability depends on its settings.
How to disable. Run `dsh plugin --profile web remove dsh-research-report` or delete the plugin row from the profile patch. The `.research-ledger` and `research-reports` directories remain and are removed by hand.
FAQ
How do I install dsh-research-report?
Run `dsh plugin --profile web add dsh-research-report` from npm, or use the `github:PerryLink/dsh-research-report` prefix for the latest branch. Restart the Harness afterwards.
What counts as the report seal?
The SHA-256 of `manifest.json`. The manifest records the report hash, every snapshot hash and the audit journal hashes, so changing any byte breaks the seal.
How do I verify a finished report?
Run `dsh-research-verify --report research-reports/<topic>/<version>`. It recomputes the seal and rechecks each claim with no network and no model.
What happens to a claim with no source?
It gets the `unverified` status, stays in the text with a visible marker and is listed in the gaps appendix. It never passes silently.
Does it need a network?
Not for seal checks. The network is used only when `evidence_add` fetches a URL through `ctx.web`. DOI checks run offline too, against format and a prefix list.
Discussion
No questions or reviews yet.
Related
PluginsA DeepSeek Harness plugin for industry research: four tools and two skills, every figure carries a source and a date
Excel analysis skill that profiles a sheet, cleans it, reconciles totals against the sheet's own sums and then releases numbers.
The Dex plugin: an agent explores a database, builds dbt models and a semantic layer and tracks schema drift under cost control
Skill and CLI for tables: cleaning with recorded decisions, level-based statistics, a PDF report and a separate audit.
Codex skill that picks fresh research papers for a researcher profile and builds a scored summary in Chinese.
A pack of 14 skills for public-data research in Chinese: a lead skill runs the project and 13 specialists cover market, competitors and valuation
README in short
The README opens with the idea of giving a topic and sources and getting a sealed report, then gives three setup steps, a capability list and the three tools. It goes on to compatibility, privacy, FAQ and the DSH Desktop market.