akslcw/dsh-negative-ledger

README excerpt

dsh-negative-ledger A negative-knowledge ledger for coding agents. It records only disproven paths — failed commands, missing files, rejected approaches, unavailable APIs — together with the evidence behind each conclusion and the conditions under which a retry becomes legitimate. When the evidence changes, the conclusion is invalidated automatically. 中文 What it is not - Not memory : no positive knowledge, no semantic recall. - Not a cache : it stores conclusions, not tool results. - Not a bug regression tracker : it covers any tool call and file read, not just fix attempts. The core loop 1. A tool call fails (non-zero exit, FS NOT FOUND , …) → a negative fact is recorded with outcome witnesses (exit code, error code) and precondition witnesses (file state from DSH's fs/observed ). 2. The next identical attempt matches the fact's fingerprint (normalized command + cwd, or file path). 3. While every precondition witness is unchanged, the attempt is warned ( warn mode) or denied ( block mode). 4. Any precondition change marks the fact stale — the reminder is withdrawn and the retry is allowed. A successful retry marks it resolved . The differentiation: a DSH-native, evidence-bound per…

Category