# Security policy

## Trust boundary

This plugin is trusted local code. It runs inside DeepSeek Harness, registers
tool hooks and commands, and starts the local child process
`owp dsh-bridge --stdio`. A compromise of Harness, the plugin process, or the
Sidecar key may falsify host observations unless independent repository
readback exposes the mismatch.

The plugin can observe declared tool names, closed arguments, execution IDs,
live results, and durable session events. It cannot prove hidden reasoning,
unobserved side effects, or remote-system state without an independent
readback. Cryptographic validity proves integrity and key possession under the
frozen rules; it does not prove that the chosen business criterion was correct.

Manager, Verifier, and Acceptor private keys must remain outside Harness and
the plugin. Never put those keys in a case directory, environment variable,
command line, repository, session transcript, or delivery export.

## Supported candidate

The only tested host version is DeepSeek Harness `0.1.1-rc.2`. The plugin is a
local `0.1.0` candidate and is not published to npm. Unsupported host versions
must fail compatibility preflight rather than silently enabling Enforce.

## Reporting a vulnerability

Use the OpenWorkProof repository's
[GitHub Private Security Advisory](https://github.com/dengyier/OpenWorkProof/security/advisories/new).
Do not attach private keys, customer repositories, unredacted ledgers, or
sensitive evidence to a public issue.

## Not a certification

A passing local test or preflight is not a security certification, legal audit,
production proof, customer adoption, or DeepSeek endorsement.