Skip to content

Releases

v0.1.0 - first public release

Choose a tag to compare

@catsenior507 catsenior507 released this 10 Sep 17:21

First public release.

dsh-policy-strict-gate turns strict_check and the failure journal from tools
the model may use into policy the harness enforces.

A tool the model must remember to call is a tool it will skip exactly when it
matters most — when it is confident, rushing, or already looping. And a check
whose output lands in a tool result can be skimmed, while a check whose refusal
blocks the next write cannot.

Three gates

  1. Repeated failure — the same signature N times queues a notice naming the
    class, the shipped remediation, and the instruction to change something.
    Counted on tools/result, which fires for the pipeline failures that bypass
    post-execute: a denied call, an unknown tool, a call refused by this gate.
  2. Critical paths — a write to a glob-protected path is refused until a Lean
    specification covering it is accepted. Ships off: the glob list is a
    statement about your code that no plugin can guess.
  3. Post-write syntax — every accepted write is followed by the language's own
    check, so a broken edit surfaces at the step that broke it.

Two rules make it a policy rather than an obstruction

Both were forced by tests rather than by design review:

  • A refusal carries the diagnostics. The harness discards a denied call's
    would-be result, so a refusal that only said "blocked" would destroy the
    information needed to satisfy it.
  • The repair path is always open. A write fixing a diagnostic this gate just
    reported is allowed through. Without it the gate deadlocks: it would refuse the
    fix to the very error it is reporting.

Install

dsh plugin --profile web add github:catsenior507/dsh-policy-strict-gate

Requires dsh-tool-strict-check for the critical-path and post-write gates; the
repeated-failure gate works alone.

Verified

72 tests (npm test). test/activation.test.js drives the real cordis
waterfalls
, because a listener registered on the wrong event name throws
nothing — it just makes the policy silently absent.

For the critical-path and post-write gates, also install the checker:
dsh plugin --profile web add github:catsenior507/dsh-tool-strict-check.
The critical-path gate ships OFF — set criticalPaths in the profile's
cordis.patch.yml to enable it. Then restart the host and run
strict_gate_status action=status.