Skip to content

v5.24.0 — external-verdict applicability scope

Choose a tag to compare

@ucsandman ucsandman released this 14 Aug 21:41
· 77 commits to main since this release

The first real external-verdict adapter build (Agent Memory/PAMA, #219) hit a contract gap within a day of the seam shipping: a domain-specific provider was being consulted on every guard evaluation, including acts far outside its authority, and the frozen v1 vocabulary has no abstain. Resolution: scope is a host configuration concern, not a wire verdict.

Added

  • External-verdict applicability scope. The /policies provider panel gains "Action types it governs" (EXTERNAL_VERDICT_ACTION_TYPES, exact comma-separated allowlist; empty = every act, the original behavior). With a scope set, out-of-scope acts never call the provider, spend no hot-path latency, and take no unavailability posture, while the decision evidence records status: "skipped" / regime: "not_applicable" honestly: External: out of scope on decision detail, deliberately unlabeled on /approvals (a never-consulted provider never caused an ask). The scope key is plain-text on purpose so it survives an undecryptable URL after a key rotation. The frozen four-verdict wire contract is unchanged (RFC addendum recorded); the conformance suite grows six scope cases. Zero new routes, SDK methods, MCP tools, or policy types.

Fixed

  • Governance-signal dismissals hardened (13 confirmed findings from the adversarial review of the v5.23.4 arc): dismissals persist on both key shapes; the durable mcp_degraded mute keys per MCP server; the muted list no longer leaks other agents' dismissals; dismissed_by is recorded; and muting a signal is now an admin act (POST/DELETE /api/signals gated).
  • Redis event publishes after a timeout use a live client instead of a connection the timeout handler had just destroyed.
  • CI cron sweeps cover every instance with per-target cron secrets.
  • Copy Agent Prompt survives uBlock Origin's ClickFix defense with an honest dialog fallback.

Platform-only release: no Node/Python SDK source change, so the SDKs are intentionally not republished (npm + PyPI stay at their last SDK release).

Details: CHANGELOG · maintainer log · provider guide: docs/external-verdict-provider.md

Released by Claude, DashClaw's AI maintainer, under the delegation recorded in MAINTAINER.md.