dsh-verification-receipt DSH plugin

DSH Verification Receipt is a small Profile Bundle for DeepSeek Harness. After each durable turn/end, it appends one privacy-minimal, heuristic execution summary to a local JSONL file. It records tool call counts and lexical verification-shaped signals, but does not prove that tests ran or that code is correct.

developer-tools

How to install the dsh-verification-receipt DSH plugin

dsh plugin --profile web add dsh-verification-receipt

Copying does not run this command. Review the repository and version before installing the dsh-verification-receipt DSH plugin.

dsh-verification-receipt DSH plugin data source

dsh-verification-receipt DSH plugin snapshot date: Aug 16, 2026

discovered

What the dsh-verification-receipt DSH plugin can do

Records tool call counts (calls, succeeded, failed, unresolved, topLevel, nested) per turn.
Emits heuristic verification signals when tool names or shell arguments resemble test, typecheck, lint, build, check, verify, or validate work.
Persists receipts to a configurable JSONL file under `$DSH_HOME/verification-receipts/v1/` by default.
Computes an unkeyed SHA-256 hash over each receipt for integrity awareness (not tamper-evident).
Does not persist tool arguments, result content, message text, raw session IDs, or model names to maintain privacy.

Where the dsh-verification-receipt DSH plugin fits

Gain a lightweight, privacy-aware summary of verification-related tool usage across DSH sessions.
Track heuristic signals for test, lint, or build tool calls without relying on full execution logs.
Analyze receipt patterns to identify recurring verification failures or tool call trends.
Integrate receipt output into external monitoring or audit pipelines as a non-authoritative hint.
Use alongside other trust-layer plugins (Telemetry Redactor, Evidence Audit, Context Provenance) for a more complete execution picture.

Who the dsh-verification-receipt DSH plugin is for

Developers using DeepSeek Harness who want a minimal, privacy-preserving execution trace.
Teams that need a lightweight, heuristic verification signal log for debugging or compliance hints.

dsh-verification-receipt DSH plugin limitations

Does not prove that tests ran, that assertions were sufficient, or that output was truthful.
Receipt rows are independent; deletion, reordering, truncation, and rollback are not detectable.
Heuristic classification is lexical only; false positives and false negatives are expected.
Does not support array commands, argv, nested command objects, or custom shell tool names.
Process crash may lose queued receipts because disk write is not synchronous with turn/end.
No cross-process lock; two DSH processes targeting one file risk row order and boundary corruption.

dsh-verification-receipt DSH plugin: from the repository README

Quoted from the 030611/dsh-verification-receipt README, the upstream source of the dsh-verification-receipt DSH plugin. Copyright remains with the original authors.

> Ask a smaller, checkable question: what verification-shaped execution signals did DSH record this turn? ```sh dsh plugin --profile web add dsh-verification-receipt ``` The receipt summarizes recorded tool counts and lexical verification-shaped signals. It does **not** prove that tests ran or that code is correct. > Community-maintained and not an official DeepSeek project. Related trust-layer plugins: [Telemetry Redactor](https://github.com/030611/dsh-telemetry-redactor), [Evidence Audit](https://github.com/030611/qiushi-dsh-evidence-audit), and [Context Provenance](https://github.com/030611/dsh-context-provenance). DSH Verification Receipt is a small, passive Profile Bundle for [DeepSeek Harness](https://github.com/deepseek-ai/deepseek-harness). After each durable `turn/end`, it appends one privacy-minimal, heuristic execution summary to a local JSONL file. ![Verification Receipt data flow](https://raw.githubusercontent.com/030611/dsh-verification-receipt/main/docs/verification-flow.svg) It records execution traces, not semantic correctness. A receipt shows only that DSH logged tool calls and that a lexical heuristic found a possible verification signal. It never proves th

Read the full READMERepository license: MIT

dsh-verification-receipt DSH plugin questions

How do I install DSH Verification Receipt?

Install it using the DSH plugin command: `dsh plugin --profile web add dsh-verification-receipt`. Replace `web` with the profile name you want to use. For local development, clone the repo, run `pnpm install --frozen-lockfile && pnpm run check`, and pass the checkout path to the `add` command instead of the package name.

Does the receipt prove that my tests passed?

No. The receipt only records that a tool call with a test-like name occurred and what its status was according to DSH. It does not verify the actual test results, assertion coverage, or correctness. The heuristic signal is purely lexical and may produce false positives or false negatives.

Where is the receipt file saved?

By default, it is saved at `$DSH_HOME/verification-receipts/v1/receipts.jsonl`. If `DSH_HOME` is not set, it resolves to `~/.dsh/verification-receipts/v1/receipts.jsonl`. You can override the path in the plugin's config using `outputPath` in your `cordis.patch.yml`.

Does the plugin send any data to external servers?

No. The plugin writes to a local JSONL file only. It does not make network requests, register a tool, add a prompt section, inject context, or make model calls. All data stays on your machine.

What happens if the process crashes before the receipt is written?

The plugin does not wait for disk writes synchronously during the turn. If the process crashes before the write queue is drained, the receipt for the last turn may be lost. Normal plugin/application disposal drains accepted writes, but abrupt termination cannot guarantee it.