dsh-2origin DSH plugin

dsh-2origin is a DSH plugin that lets agents inspect a `task.origin.json` state, distinguish semantic content from provenance metadata, compare a complete candidate, and freeze the exact observed version with an optimistic-lock credential. It provides both DSH tool surfaces and a separate proof-only MCP server for inline verification.

developer-tools skills-workflows

How to install the dsh-2origin DSH plugin

dsh plugin --profile <name> add github:dongsheng123132/dsh-2origin

This source command needs manual review. Copying does not run it.

dsh-2origin DSH plugin data source

dsh-2origin DSH plugin snapshot date: Aug 16, 2026

discovered

What the dsh-2origin DSH plugin can do

Compact status projection with hash integrity check via `dsh_2origin_status`
Read-only semantic diff against a candidate JSON document via `dsh_2origin_diff`
Content-addressed freeze with exclusive creation and read-back verification via `dsh_2origin_freeze`
Independent stdio MCP server for bounded state proof and diff proof (no filesystem writes)

Where the dsh-2origin DSH plugin fits

Verify the integrity of a task state before making workflow decisions
Compare a candidate state against the current frozen state to detect semantic changes
Freeze a specific version of the task state as an immutable snapshot for audit or rollback
Use the MCP server to validate inline state documents without filesystem access

Who the dsh-2origin DSH plugin is for

DSH agent developers working with 2Origin task state documents
Teams that need a verifiable, immutable record of task state transitions

dsh-2origin DSH plugin limitations

Only supports 2Origin/0.2 task state format; not a general memory store or activity logger
Freeze is the only write action and targets a separate snapshot directory; live state is never mutated
Requires explicit workspace configuration (workspaceRoot, stateFile, freezeDir)
MCP server does not expose freeze (filesystem writes remain on CLI/DSH surfaces)

dsh-2origin DSH plugin: from the repository README

Quoted from the dongsheng123132/dsh-2origin README, the upstream source of the dsh-2origin DSH plugin. Copyright remains with the original authors.

Evidence-first 2Origin state projection, semantic diff and immutable freeze for [DeepSeek Harness](https://github.com/deepseek-ai/deepseek-harness). Chat history is not the handoff artifact. A `task.origin.json` state is. This plugin lets a DSH agent inspect that state, distinguish semantic content from provenance metadata, compare a complete candidate, and freeze the exact observed version with an optimistic-lock credential. v0.2 is a formal Codex plugin with a separate proof-only MCP surface. It also removes the default export that made the real Cordis Loader discard namespace `inject` metadata, and carries a stock Web Loader regression smoke. ## Install ```bash dsh plugin --profile <name> add github:dongsheng123132/dsh-2origin ``` Configure the workspace explicitly: ```yaml - id: dsh-2origin name: dsh-2origin config: workspaceRoot: C:/absolute/project/path stateFile: demo/my-task/task.origin.json freezeDir: .2origin/frozen ``` All configured file paths are relative to `workspaceRoot`. Traversal and symlink escape are refused. ## DSH tools - `dsh_2origin_status` — compact projection, counts, verified-fact count, and recorded-vs-computed hash integrity. -

Read the full READMERepository license: MIT

dsh-2origin DSH plugin questions

How do I install dsh-2origin?

Run `dsh plugin --profile <name> add github:dongsheng123132/dsh-2origin` in your DSH environment. Then configure the workspace in your plugin config YAML with `workspaceRoot`, `stateFile`, and `freezeDir`.

What does the freeze tool do?

`dsh_2origin_freeze` creates a content-addressed snapshot of the current state file, using an expected hash for optimistic locking. It refuses stale state and verifies the snapshot by reading it back. Repeated identical requests are idempotent.

Can I use the MCP server to freeze state?

No, the MCP server intentionally does not expose freeze. It only provides inline verification (`state_proof` and `state_diff_proof`) without filesystem writes. Freeze is only available via the CLI and DSH tool surfaces.

What is the difference between a regular diff and dsh_2origin_diff?

`dsh_2origin_diff` performs a semantic diff that ignores version, timestamp, actor, and stored hash fields. It only reports changes in actual content. The candidate document must be a complete JSON file.

Does this plugin modify the live task state?

No, the plugin deliberately does not update the live state. Freeze writes to a separate snapshot directory. Live-state mutation is left to the owning system to avoid creating a second truth.