dsh-sieve-web

Configuration

With Jev you need no configuration at all: the judge is auto and every decision is on; put a key in the credential store or the environment. To adjust anything, configure the sieve service in the profile's patch:

- id: sieve
  config:
    judge:
      type: auto           # auto | system-one | laya
      timeoutMs: 4000
    modes:
      default: active
      context.forget: off  # e.g. turn off forgetting alone

judge.type	Description
auto (default)	The Jev key in the DSH credential store or the environment (TYPESAFE_API_KEY first, then SIEVE_JUDGE_OPENROUTER_API_KEY); with neither, nothing changes
system-one	The Jev endpoint named in the profile; needs apiKey (preferably !!js process.env.XXX), optional baseUrl and model (default jev-latest)
laya	The local Laya server; optional baseUrl (default http://127.0.0.1:47823), no key

modes sets each decision to active (default) or off; default covers the decisions not listed. Decision ids: tool.admission, tool.admission.test-log, context.forget, skills.disclosure.

Example with an explicit Jev endpoint:

- id: sieve
  config:
    judge:
      type: system-one
      apiKey: !!js process.env.MY_JUDGE_KEY
      baseUrl: https://
      model: jev-latest

An invalid configuration (an unknown decision id, say, or the removed llm judge settings) fails at load instead of silently falling back.