Solutions

Risk review

A mandate whose job is to disagree, with a veto that is a first-class answer, and a refusal that names what is missing rather than approximating it.

AVAILABLEWritten and covered by tests, not yet observed in a live runDeskworth · published · updated · 3 sources · Deskworth OS 0.0.25

Most systems that produce an analysis have nobody whose job is to disagree with it. The risk mandate reads the desk, the theses the other cards returned, and holds a veto on adoption. Its remit is declared limits, desk concentration, and that veto.

#A refusal is a result

When a question cannot be answered at the as-of date with admissible sources, the mandate deposits a blocked artefact rather than approximating. It carries what was attempted and why it stopped; the contract refuses to deposit it otherwise. That is the most honest answer available, and often the most useful.

EvidenceThe tool that reports a block requires no capability at all, every mandate must be able to say it cannot answer. Refusing is not a privilege.

#What the risk mandate can and cannot reach

#Sources

  1. The canonical role registry, mirrored on this siteDeskworthinternal registry · roster registry mirror · read 2026-09-10Internal document, not published
  2. The tool registry, mirrored on this siteDeskworthinternal registry · tool registry mirror of mcp::tools::TOOLS, crossed with the roles’ declared capabilities · read 2026-09-10Internal document, not published
  3. Deskworth OS, product state at 0.0.24, providers and MCPDeskworthinternal handover report · Deskworth OS 0.0.24 · commit produit fb53f44 · lu à d01b336 · published 2026-09-10 · read 2026-09-10Internal document, not published

Read next

More in Solutions