dsh-health-readout

Overview

Declarative health readout for DSH: declare where to read, what counts as healthy, and which verdict each reading maps to. Read-only — it composes readings, it never becomes a new source of truth.

README / EN

Package documentation

Registry summary

Declarative health readout for DSH: declare where to read, what counts as healthy, and which verdict each reading maps to. Read-only — it composes readings, it never becomes a new source of truth.

dsh.pub verifies the pinned bundle contract, runtime facts, and distribution semantics. The complete README remains in the source repository.

Read the full README on GitHub

LIMITATIONS

Known limitations

- **No cross-line folding.** A reading is one value from one place. "How many records are still open" means folding several JSONL lines into a state, which is a query, not a reading. Point the spec at a file that already carries that number (a derived snapshot) and keep the fold in whatever produced it — this plugin composes readings, it does not become a query engine. - **No history.** Every reading is one sample of the present. Trends need a recorder, and a recorder is a writer — out of scope for a readout. - **No `changed-within` operator.** Comparing to a previous value requires state; see above. - **`unknown` is noisy by design.** A missing file moves the verdict. That is the intended trade: silence about a blind spot is more expensive than a loud report about one. - **A spec may read any file the dsh process can read.** That is the trust model: the user writes the spec, the user owns the paths. - **Host-only.** No browser half, no settings UI; the verdict reaches the model as a tool result.

dsh-health-readout