DSH Recovery Proof

A read-only recovery-drill evidence verifier for DeepSeek Harness. It does not restore files, create checkpoints, or replace recovery executors such as Turn Rewind or Checkpoint Rewind. It verifies that an external drill left reproducible evidence.

What it proves

• every referenced prestate, rescue, restored or rollback object is a regular workspace file with the declared SHA-256 and revision;
• recovery, failed-apply rollback and stale-plan rejection follow the manifest's exact phase sequence;
• rescue evidence exists before apply, failed apply is followed by successful rollback, and stale plans are rejected;
• accumulated structural event duration remains within each scenario's RTO threshold;
• missing/stale evidence and every failed rule are disclosed in a content-addressed JSON report.

Inputs are explicit JSON/JSONL files. Secret-, token-, prompt-, chat- and content-shaped fields are rejected. Object contents are never included in output. The verifier writes only to the explicit workspace-relative artifactDir, using an atomic write and SHA-256 read-back check.

Install and compose

dsh plugin install github:dongsheng123132/dsh-recovery-proof
dsh plugin compose dsh-recovery-proof

The bundle registers dsh_recovery_proof_inspect and dsh_recovery_proof_verify.

CLI

dsh-recovery-proof inspect --workspace-root ./examples/basic --manifest recovery.manifest.json
dsh-recovery-proof verify --workspace-root ./examples/basic --manifest recovery.manifest.json --events recovery.events.jsonl --artifact-dir artifacts

Exit code 0 means the command ran and verification passed, 2 means the evidence was processed but failed policy, and 1 means invalid or unsafe input.

Manifest and events

See examples/basic. A manifest pins system.revision, content-addressed objects, and explicit scenarios with expectedPhases, requiredObjectIds, and maxRtoMs. Events contain only structural facts: unique idempotency key, scenario, sequence, phase, status, duration and object references.

Security boundary

All input paths and the output directory must remain under workspaceRoot; symlink inputs and symlink output directories are rejected. No shell is spawned, no network is used, no recovery action is executed, and there are no install lifecycle scripts.

Development

npm test
npm run check

MIT