dsh-plan-lattice

Evidence-gated work graph for long-horizon DeepSeek Harness agents.

Every plan mutation earns its context. No parent completes before its evidence reconciles.

dsh-plan-lattice is an independent community plugin for DeepSeek Harness. It implements the "Fractal Ledger" method: begin with a small project tree, recursively split only the active frontier into atomic leaves, and make each meaningful change prove that the agent has just read the current project contract.

It is designed for the failure mode where a long-running agent starts with a good plan, discovers new constraints during implementation, and quietly keeps executing an obsolete version of that plan.

What It Enforces

The plugin makes four rules executable rather than advisory:

1. Context contract. A project names its background, product, and architecture documents explicitly. lattice_open and lattice_refresh_context read every document in full, return their content to the agent, and issue a revision-bound SHA-256 receipt. Oversized context fails closed rather than being silently truncated.
2. Freshness receipt. Adding, splitting, editing, archiving, checking out, and checkpointing a node all reread the complete contract. The operation is refused when the receipt is stale, from another session, or when any tracked document changed since it was issued.
3. Recursive work graph. The workspace ledger has stable node ids, an append-only audit history, compare-and-set revisions, a small branching policy, and evidence attached to each leaf. It is not a replace-all todo list or a workflow scheduler.
4. Reconciliation gate. A configured write tool needs an active leaf lease. After each successful guarded action, the next guarded action is denied until lattice_checkpoint records evidence. A parent becomes complete only when every live child is complete, at which point it receives derived reconciliation evidence.

The default shape is at most two top-level nodes and five children per nested node. That deliberately keeps a dynamic task understandable instead of spawning an uncontrolled task swarm. These limits are configurable; they are not a promise of parallelism.

Why This Is Different

Harness already provides plan mode, a same-session goal, and a per-turn flat todo list. Ecosystem plugins also cover Markdown specifications, plan review, workflow graphs, and task scheduling. Plan Lattice does not replace them.

Its narrow ownership point is the missing hard boundary between reading the current project contract and changing or advancing a recursive plan. The ledger records only structure, references, timestamps, and content digests; it does not copy the context documents into project storage.