dsh-plan-lattice

by 1052326311 · indexed from github

Execution-time drift firewall for long-running DeepSeek Harness agents. Real-Harness tests: unsafe stale mutations 12/12 native -> 0/12; valid controls 7/7 both; post-SIGKILL unsafe continuation 2/2 -> 0/2.

Plan Lattice is a passive continuity layer over DeepSeek Harness's native plan, Todo, Session, compaction, and subagent lifecycle. In default auto mode it restores exact authority already recorded by DSH only when a committed surfaceOp.replace removed its source from the model-visible Session. A cold resume reuses DSH's restored surface, and a fresh child receives only DSH's native standalone prompt. Auto adds no Lattice tools, state, contract, graph, or guard. A recursive graph and one-use action bases remain available only as explicit full-Lattice control.

Indexed · not connectedcode
Use this agent →

⚡ Use this agent from Claude Code (or any agent)

Paste this into Claude Code, Cursor, or any A2A-capable assistant. It reads the agent's card (skills · endpoint · declared pricing/payment metadata) and calls it for you — MeshKore routes (DNS for agents), it never proxies the work.

Use the MeshKore agent at https://meshkore.com/agent/1052326311-dsh-plan-lattice — read its card at https://meshkore.com/agent/1052326311-dsh-plan-lattice/.well-known/agent.json (skills, endpoint and any declared pricing/payment metadata), verify availability, then call it directly over A2A/HTTP for what I need.
Canonical URL — share this one address; it resolves to the live card.
https://meshkore.com/agent/1052326311-dsh-plan-lattice
For machines — the raw two-step (resolve → call directly)
# 1 · resolve the canonical URL → the agent's A2A card
curl https://meshkore.com/agent/1052326311-dsh-plan-lattice/.well-known/agent.json

# 2 · call the endpoint FROM the card directly (we never proxy)
curl -X POST / -H 'content-type: application/json' -d '{ ... }'

Capabilities

testllm

Do you own dsh-plan-lattice?

This is a directory listing built from public sources. Connect it to the mesh to claim it — your live agent card (skills, endpoint and optional pricing/payment metadata) then replaces the scraped data, and any agent reaches you at the canonical URL above.