Introduction

dsh-route-certificate is an experimental plugin for the DeepSeek Harness developer preview. It is used to observe durable turn/end session events and generate a standalone RouteCertificate receipt. It is not responsible for rewriting or hiding the original Harness results, and it is ready to use as-is with its default validator.

Installation and Enablement

First, select an existing Harness Profile and use the official command to install from a fixed public commit:

PROFILE=tui
PACKAGE_SPEC=git+https://github.com/runyuan-wang/dsh-route-certificate.git#<fixed-public-commit>
dsh plugin --profile "$PROFILE" add "$PACKAGE_SPEC"
dsh --profile "$PROFILE" --dump-config

After installation, the plugin generates receipts in the Profile directory by default:

$DSH_HOME/profiles/<profile>/.route-certificate/receipts/

To remove it, use the following command:

dsh plugin --profile "$PROFILE" remove -w dsh-route-certificate

Core Features

The plugin provides the following capabilities:

  • Structured verdicts: Based on terminal state and envelope completeness, it outputs pass (complete and normal), fail (explicit error), or indeterminate (interrupted/unknown).
  • Zero-build direct installation: No clone, build, or custom validator is required.
  • Request and artifact provenance: It binds the request, execution prefix, termination event, result scope, and artifact fingerprints.
  • Bypass observation mode: It defaults to advisory mode; even if validator or receipt writing fails, it does not replace or block the original Harness results.

Notes

  • Functional boundary: It does not judge the truthfulness of answers, semantic correctness, output quality, safety, or whether a task succeeded.
  • Environment requirements: Requires Node.js >= 22.19.0. Supports @deepseek-ai/dsh@0.1.0-rc.7 and session format 0.
  • Component relationship: It does not add or replace official @deepseek-ai/* components.
  • Data visibility: The plugin runs with DSH process permissions; sensitive task content should be considered visible.
  • Platform validation: Currently only validated in macOS environments; runtime behavior on Linux and Windows is unverified.