ICCuse/dsh-premise-guard
A post-compaction premise-drift guard for DeepSeek Harness. After a compaction/summary event it re-derives the shadowed span's text from shadowedSeqs (the log keeps every byte), extracts distinctive literal anchors — file paths, quoted literals, key=value pairs, error codes — and checks whether the committed summary still contains them. When a critical anchor has vanished it injects a one-shot notice into the next step naming up to maxAnchors lost anchors and the shadowed seq range, so the model learns the moment a path, value or error string it was relying on is no longer in the summarized context. The README frames this as the missing complement to recall-oriented designs, which make shadowed content reachable only when suspected.
Install
npm install github:ICCuse/dsh-premise-guardREADME Install section quoted verbatim — it states the package is not on npm yet, so you install from the repository with npm install github:ICCuse/dsh-premise-guard (or pnpm add github:ICCuse/dsh-premise-guard), then mount the bundle in the profile's cordis layer with - id: dsh-premise-guard / name: 'dsh-premise-guard'. Registry check 2026-09-16: dsh-premise-guard returns 404 on npm, consistent with the README.
Compatibility
README: it hooks session/event (compaction/summary) and agent/pre-step; config fields maxAnchors (default 5), minAnchorLength (default 6) and maxNoticeChars (default 400) must all be integers >= 1 or the plugin throws at load. Anchor extraction is deterministic and pure — no LLM calls, no new storage. Repo verified 2026-09-16 (0★, MIT, last push 2026-08-14).
Details
- Repo: ICCuse/dsh-premise-guard
- Category: Other
- Stars: 0
- Version: Source/GitHub install (README: not on npm yet)
- Last push: 2026-08-14
- First seen: 2026-08-14
Recent updates
The README documents the hook pair, the anchor logic and the config table rather than a release-by-release table.
FAQ
- How do I install it?
- The README says it is not on npm yet: run npm install github:ICCuse/dsh-premise-guard (or the pnpm equivalent) and then mount the bundle with - id: dsh-premise-guard in the profile's cordis layer.
- What problem does it solve?
- Per the README, nothing else tells the model that a key fact it was relying on just dropped out of the summarized context; this guard turns the compaction summary into a checked handoff.
- Does it call a model or store extra data?
- No — the README says anchor extraction is deterministic and pure, with no LLM calls and no new storage.