030611/dsh-context-provenance
Observe-only provenance ledger over public DeepSeek Harness runtime evidence
Compares adjacent request evidence as Observed, Estimated, or Unavailable — without returning prompt text, message content, tool schemas, or raw paths. It retains only the two most recent ordinary agent-loop request observations in memory and exposes them through the existing Cordis inspect query mechanism. Evidence fields include effective request provider/model, adapter context window, system presence/change, tool names/catalog change, and tool owner/plugin mapping. Audit verdict: conditional pass against official DSH commit 47f943859bef60e4160492346772ded9b24f765a.
Install
dsh plugin --profile web add dsh-context-provenancenpm package dsh-context-provenance 0.1.1 (registry-verified 2026-08-25). README: add the public bundle to the selected DSH profile, then inspect the resolved configuration with dsh --profile --dump-config. Before installing, verify the registry version, source tag, and release notes rather than treating an untagged repository checkout as a release artifact. Community-maintained, not an official DeepSeek project. Related trust-layer plugins: Telemetry Redactor, Verification Receipt, Evidence Audit.
Compatibility
DeepSeek Harness Web profile. Observe-only, CPU-only, local-only — performs no file, network, subprocess, GPU, persistence, session, permission, tool, model-routing, or request mutation.
Details
- Repo: 030611/dsh-context-provenance
- Category: Coding & Development
- Stars: 4
- Version: npm dsh-context-provenance 0.1.1 (registry-verified 2026-08-25)
- Last push: 2026-09-03
- First seen: 2026-08-14
Recent updates
v0.1.1: strict evidence labeling (Observed/Estimated/Unavailable) plus adjacent actual-request comparison; distinct from dsh-context-doctor (no rescan, no token re-estimation, no optimization advice).
FAQ
- What can this plugin prove about the agent's context?
- Only what public runtime interfaces can actually prove: effective request provider/model and adapter context window (Observed), system presence/tool catalog changes (Observed), and tool owner/plugin mapping (Unavailable). No prompt text, message content, or tool schemas are returned.
- Does it modify anything?
- No — it is observe-only: no file, network, subprocess, GPU, persistence, session, permission, tool, model-routing, or request mutation. It keeps only the two most recent request observations in memory.
- Is it an official DeepSeek project?
- No — it is community-maintained. An audit verdict of conditional pass was recorded against official DSH commit 47f943859bef60e4160492346772ded9b24f765a.
Alternatives
030611/dsh-verification-receipt · 030611/qiushi-dsh-evidence-audit · LeslieWylie/dsh-evidence-memory