/nw-typesafe-system-one

name: nw-typesafe-system-one
description: "Use Jev System One for every supported, authorized semantic judgment when available: relevance selection, handoff preflight, evidence mapping, finding clustering, and confidence-gated escalation."
user-invocable: false
disable-model-invocation: true

TypeSafe System One for Delivery

**Kind**: KNOWLEDGE. For every supported task-level semantic question, MUST use Jev when authorized and available. Resolve mechanical facts with local code. Loading this skill alone is not service use. This policy applies in every user project where nWave is active, not only the framework repository.

Boundary

Jev is a remote System One service. It receives `state` and typed questions and returns a structured `Choice`, `Score`, or `Noul` with probabilities. It does not write code, reason through a delivery, prove a property, execute a command, or replace a human or independent reviewer.

A supported question has permitted evidence, explicit criteria and a typed answer that the decision owner will actually use. Confidence, simplicity and predicted savings are not reasons to skip it. Decompose larger reasoning tasks into their supported subquestions; do not disguise synthesis or proof as a forced choice.

Jev is authorized by default: do not ask the user for authorization again. The only authorization gate is an explicit refusal, `--jev unauthorized` on the call or `"jev": "unauthorized"` in the repository or global configuration. When refused, do not transmit and retain that limitation. `TYPESAFE_API_KEY` is only a technical prerequisite for the service to work; it is never authorization or consent. Jev is remote, not telemetry.

Check service capability at the first eligible question. If the key, permitted invocation path or service is unavailable, record `typesafe: unavailable` and continue locally. Never fabricate a call, widen role permissions, retry blindly or block delivery on service failure. A malformed request is a caller defect, not an unavailable-service exemption. Repair a known defect before a new attempt; an unresolved defect remains explicit and local work can continue.

Do not call Jev for arithmetic, hashes, dates, parsing, schema checks, command execution or symbol resolution. Use their deterministic tools.

Minimize transmitted state. Exclude credentials, secrets, personal data, private findings, source-blind material, confidential account/host/resource identifiers and secret-bearing logs. Source/test/consumer fragments may be sent only within explicit authorized review scope; do not send repository dumps, historical grader/baseline material or producer evidence to an independent assessment. If redaction removes needed relationships, classify insufficient and work locally. Record returned model, input/output tokens, duration and cost when actually available; unknown cost is not zero.

The LLM owns orchestration. nwdes constructs handoffs and documents without choosing steps. Jev supplies bounded judgments; code owns identities, arithmetic, schema checks, policy, and actions.

Mandatory invocation routine

1. Identify the task-level semantic question, its owner and permitted evidence. Do not recursively classify whether a classification needs classification. 2. Reuse an applicable result only within the same decision-owner and independence boundary. Otherwise batch independent questions over the same compact state and invoke the existing client. A question counts once per relevant revision, not once per sentence or reformulation. 3. Inspect the distribution and raw answer, check relevant original evidence, and record the resulting local action with the request/result. A low-confidence or `insufficient` answer calls for reasoning or a discriminator, not blind trust.

python <this-skill>/scripts/jev_decide.py --request request.json --output result.json

A role that may not write files (for example a reviewer) passes `-` for both `--request` and `--output`, supplying the request JSON on stdin (a heredoc); the raw response is printed on stdout, so no file is created and every write prohibition of the role still holds.

Run the client from a shell command, with the heredoc in that same command. A tool kernel, for example a Python eval kernel, may not inherit the session environment that holds the key, and then the client reports exit 3.

Request fields are exactly `state`, `model`, and non-empty `questions`. Use the configured supported model; retained calls currently use `jev-1.13.0`. Include `insufficient` where legitimate. Service responses are judgments, not proof.

Keep owner and revision receipts in the local record. If permitted ownership context is needed in the transmitted evidence, place it inside `state`; `owner`, `role`, and `revision` are not extra root request keys. A validation failure returns unchanged to the requesting owner, who corrects its own request. The caller never strips keys or rewrites an independent question to make it pass.

For a choice, `type` is lowercase `"choice"`. The keys of `criteria` are the answer labels, and each value describes when that answer applies. They are not scoring dimensions. This complete request illustrates the wire format:

For `"score"`, `criteria` is a nonempty ordered array of rubric levels, not an object of dimensions. Ask one Score per relevant item/dimension with anchored levels. For `"noul"`, criteria may be omitted/null or an object of `true`/`false` descriptions. Choice criteria is a label object. Preserve role-authored request and raw response; the existing client validates the actual wire contract.

{
  "model": "jev-1.13.0",
  "state": {"need": "Notify state changes", "candidates": {"A": "Event subscription", "B": "String formatter"}},
  "questions": {
    "relevance": {
      "type": "choice",
      "instructions": "Which candidate directly supports the stated need?",
      "criteria": {
        "A": "Event subscription directly suppo