Introduction¶

The DSH plugin ecosystem emphasizes “everything is a plugin.” For long tasks, a common problem is: the Session, plan, Todo, or sub-agent states visible to the model may be inconsistent with the actual submitted actions, tool results, or checkpoints. After compaction, process recovery, or sub-agent lifecycles, subsequent operations may fall on an expired basis.

dsh-plan-lattice is a passive continuity layer for DeepSeek Harness (DSH) long-horizon agents, designed to handle such execution-time drift. The DSH Community Directory is an independent site with no official affiliation to DeepSeek or Huafan, and should not be interpreted as an official app store.

What is this¶

Maintainer is 1052326311, license is MIT. It covers DSH native plan, Todo, Session, compaction, and subagent lifecycle, aiming to perform execution-time drift control.

name: dsh-plan-lattice
owner: 1052326311
license: MIT

Core Features¶

Default auto: Only restore DSH recorded authority¶

The default auto mode does not add Lattice tools, state, contract, graph, or guard. It only restores the exact authority that DSH has already recorded when a submitted surfaceOp.replace removes the source from the model-visible Session.

This means the default path does not actively introduce graph control, nor one-use action bases; it handles recovery scenarios where “the source has already been removed from the model-visible session.”

Explicit full-Lattice: Recursive graph and one-use actions¶

Recursive graph and one-use action bases are only available as explicit full-Lattice control.

Under explicit full-Lattice control, the documentation describes handling two types of boundaries:
- Limit subsequent actions based on the accepted contract; covers implicit English and Chinese changes.
- Process old graph branches after reframe and align with the new contract; covers every unarchived node.

These are explicit full-control declarations, not automatic-mode declarations.

lattice_status¶

lattice_status can return up to three recent mechanical receipts and renders the following identities via the model-facing content path of the real Harness ToolRuntime:

attempt
call
argument
basis
result

Artifact Loading and Schema Observation¶

The public RC.6 artifact can be loaded into official Harness rc.7 and the currently installable 0.1.1-rc.2; CI observes all 16 lattice_* tool schemas.

Test Evidence and Boundaries¶

The results of the real Harness mechanism stress test provided in the documentation are:

unsafe stale-basis mutations:
native: 12/12
Plan Lattice: 0/12

matched legitimate controls:
native: 7/7
Plan Lattice: 7/7

The results of the real SIGKILL recovery test are:

unsafe post-SIGKILL continuations:
native: 2/2
Plan Lattice: 0/2

matched post-restart controls:
native: 2/2
Plan Lattice: 2/2

The following boundaries should be noted:
- V20, V18, and V17 are retained as invalid or negative results; do not make quality or improvement claims based on these.
- v3 external-model study is frozen, but there is no testing for the current runtime execution; do not make general coding quality improvement or ranking claims based on this.
- The source-contract proof of official Harness alpha.1 is not install compatibility, nor is it an endorsement.

Installation and Enablement¶

The documentation does not provide an official installation command, so no assembled installation command is provided here.

Verifiable runtime and version information is as follows:

node: >=22.19.0
license: MIT

README: v0.3.0 为 latest stable release
README: v0.4.0-rc.6 为 current public runtime candidate
README: checkout 包含 unreleased rc.8 native-continuity work
package.json: version 0.4.0-rc.8

Since the version status of README and package.json is not fully consistent, and rc.8 is described as unreleased native-continuity work, you should confirm the target version and read the source code before installing.

Typical Usage¶

The following is a capability-level usage description, not a copy-paste command:

In default auto mode, focus on restoring DSH recorded authority after a submitted surfaceOp.replace removes the source from the model-visible Session.
If recursive graph or one-use action bases are needed, enable explicit full-Lattice control.
When recovering or debugging, use lattice_status to view up to three recent mechanical receipts.

Applicable Scenarios and Notes¶

Suitable for:
- DSH long tasks needing to reduce the risk of subsequent actions caused by stale bases after compaction, Session recovery, or sub-agent lifecycle.
- Viewing mechanical receipts after a process is SIGKILLed, and avoiding unsafe post-SIGKILL continuations.
- Handling graph branch reframe, contract alignment, and subsequent action boundaries in explicit full-Lattice mode.

Notes:
- The plugin runs with the permissions of the current dsh process; check the source code, license, and dependencies before installing.
- Default auto does not add Lattice tools, state, contract, graph, or guard; explicit full-control capabilities are not automatically equivalent to automatic mode capabilities.
- The current documentation does not provide an installation command, nor a single verifiable stable version.

Links¶

catalog: https://www.skillhub.cn/plugins/1052326311/dsh-plan-lattice
github: https://github.com/1052326311/dsh-plan-lattice

dsh-plan-lattice: Runtime Drift Control for DSH Long-Term Tasks