dsh-kiss-law

dsh plugin --profile web add dsh-kiss-law

dsh-kiss-law

📦 npm release source｜package dsh-kiss-law

This repo is the release source for the npm package dsh-kiss-law. Install: npm i dsh-kiss-law.

The version in package.json tracks the next release; what is published is what npm says.

KISS's Law universal causal engine (white-box presentation) —— implemented as a Cordis plugin of DeepSeek Harness (DSH).

Framework definition: Keep Integrity & Steady State (KISS).

- "Keep Integrity" = guarding wholeness / truth (white-box no-tampering / inner-H inviolability, corresponds to Integrity);

- "Steady State" = keep the system alive (first principle).

- "Law" is a name suffix of the framework, not the third part of the definition.

⚠️ KISS here means "Keep Integrity & Steady State" — NOT the popular engineering acronym "Keep It Simple, Stupid". The two are entirely different in meaning; do not conflate them. The full name is KISS's Law (Keep Integrity & Steady State's Law).

Source: author's revelation (Xia Qi / Shaky77). Framework-native (three iron laws / causal logic chain) strictly, not softened, not altered.

⚖️ Dual license: open-source use AGPL-3.0; commercial integration / closed-source distribution / OEM can be licensed independently of AGPL-3.0 → 563003@qq.com. See [License & security](#license--security) and CONTRIBUTING.md.

---

Two things so far, one purpose: save you the detour, without walking it for you.

- 🧱 WALLS.md — answers "what is on the road". Signposts for the walls earlier AIs walked into. The walls never moved; painting them only makes them visible. It adds no restriction whatsoever — it converts the positions you would otherwise have to learn by hitting them with your body into positions you can know by looking.

- 📖 This README — answers "how it runs". Interfaces, criteria, how to mount it.

- 🧭 ONBOARDING.md — answers "where am I". The document that tells a new user which slot they occupy, so that being governed does not read as being wrong. It was held back until the behaviour it describes existed here — the four-state split of review, the trusted tool-declaration channel, the self-reference fix — because a manual describing behaviour the code lacks is worse than no manual. Batches 1–4 closed on 2026-10-28, so it ships now. It adds no restriction either; it only says where you already stood. Porting order and per-batch accounting: SYNC.md.

🔴 Neither of the two adds a restriction. The only thing that blocks you is the engine itself — and what it blocks is never "you are wrong", it is either "you are out of bounds" (irreversible; hit it and there is no future) or "this cannot be judged" (it needs a human, or it needs a bit more from you).

---

Understand in 30 seconds

KISS's Law is a general framework describing how causal law runs. This repo implements it as a DSH plugin: it mounts a white-box causal engine onto an AI Agent running on DSH —

• Before any action, the engine simulates along the full causal chain — how much steady-state reserve would be eroded, the break-window risk level, whether the message stays self-consistent — then adjudicates allow / deny / review;
• Red lines are blocked, faults are severed to preserve continuity (First-Bug Halt);
• Meanwhile "state / boundary" is exposed as queryable tools, so the model can self-check and you can audit.

In one line: the framework-native is "universal causal engine (white-box presentation)" — causal-chain reasoning is the engine's capability, white-box audit is its presentation stance, and risk-control blocking is an endogenous property.

What it does

• Causal-chain simulation (the engine itself): before each action, it simulates consequences along the full causal chain — steady-state erosion, risk level, self-consistency — and issues an allow / deny / review verdict. Not just audit: it is causal reasoning about an action's consequences.
• White-box self-check (presentation stance): steady-state reserve ledger (only grows, never decreases), H inner-H boundary (inviolable) declaration, all exposed as queryable tools for the model to calibrate direction and for the user to audit.
• Rigid guard (derived application · endogenous property): before each action, do rigid-anchor checks; on touch, break-window stop-loss blocks; a faulty component triggers First-Bug Halt (sever to preserve continuity), keeping the overall causal chain unbroken.
• Fractal: the same plugin can be recursively mounted at sub-agent / sub-task levels.

How it differs from existing "causal" approaches (general-purpose causal engine)

KISS's Law is not "yet another causal engine" — it is a general-purpose (domain-agnostic) causal-adjudication middleware: it validates only causal structure and encodes zero domain content, so law, medicine, finance, and robotics are governed by the same mechanism.

• Causal-effect estimation libs (DoWhy / CausalML / Pearl…) → we do not discover causality; we adjudicate whether a proposed action's causal chain is acceptable.
• Domain-specific causal guardrails (Causal Safety Engine / LLMGuardrail…) → they are bound to one domain (safety / LLM / hallucination); we are domain-agnostic.
• Cross-jurisdictional legal causal AI (judgeai…) → they are jurisdiction-aware (encode law, swap norm packages); we are jurisdiction-neutral (encode no jurisdiction at all — law is just one sampled domain).

Full bilingual comparison (prior-art references & honest bounds): [weiwen-vs-market-causal.md](https://github.com/Shaky77/weiwen-law-dsh/blob/main/v

…(truncated)