Repository navigation
chore(platform): release 2.5.4 (guardrails trace tags, 5 s self-check timeout) - #136
Merged
Merged
Conversation
…nUnavailable
On a live cluster 27 of 103 self-check calls (26%) came back empty: all
at exactly 1.5 s, the timeoutMs default; gpt-oss answers in 0.9-1.5 s.
An empty check let the request through even in block mode, and a trace
did not show the mode, the verdict or whether it was enforced.
- every check records a "guardrail self_check <side>" span with
zelkor.guardrail.{mode, verdict, status, enforced, on_unavailable,
latency_ms}, mirrored as Langfuse guardrail_* metadata
- status tells timeout, error and unparseable apart
- selfCheck.timeoutMs default 1500 -> 5000
- selfCheck.onUnavailable: allow (default, unchanged) | block refuses in
block mode when a check has no verdict; ignored in log mode
- docs: the new key and the trace fields
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
… timeout) - charts, first-party image tags, Zelkor Dockerfile bases and example charts at 2.5.4; example chart dependencies rebuilt - profiles/values-production.yaml at tag 2.5.4, digests empty until the signed release run - THIRD_PARTY_NOTICES: 2.5.4 row (no third-party changes) Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
S-gate against the 2.5.4 candidate on the production-shaped lab: default self-check mode (log), the guardrail-refusal cases (S-12, S-13, S-81, UAT-12, drop-in harmful) under the selfCheck.input: block opt-in, and S-71/72/73 under a temporary tool-policy overlay. File paths removed. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Release 2.5.4 (PATCH): guardrails self-check fixes found by reading the 2.5.3 traces on the production-shaped lab.
timeoutMsdefault, while gpt-oss answers in 0.9–1.5 s. A check with no answer let the request through, even inblockmode.selfCheck.timeoutMsdefault goes from 1500 to 5000.selfCheck.onUnavailable:allow(default, unchanged) orblock, which refuses inblockmode when a check gets no verdict. It is ignored inlogmode.guardrail self_check <side>span withzelkor.guardrail.{mode, verdict, status, enforced, on_unavailable, latency_ms}, mirrored as Langfuseguardrail_*metadata.docs/nemo-guardrails.mddocuments the new key and the trace fields.Verification on the production-shaped lab
verdict=block enforced=Falseblock+onUnavailable: block, timeout forced to 10 msguardrail_unavailableloggedblock🤖 Generated with Claude Code