Guardrails in the console: attach and detach on a branch, where each applies from, and a column
Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
This commit is contained in:
1 parent
02aac84ca5
commit
d55472c00a
5 files changed
+159
-3
No files matched your search
@@ -321,6 +321,15 @@ documented, left to `scaling.min`.
|
||||
(`context.WithoutCancel`, like `saveThread`) and only records.
|
||||
|
||||
### B4. Config, metrics, UI (S)
|
||||
**Done (branch `guardrails-b`):** library in server.yaml, attachments via
|
||||
`ctl guard`, the console's **Guardrails…** with "applies from" marks, and
|
||||
the portal's `/admin/guard`; the metrics and alerts below (judge latency
|
||||
labelled by model only at the judge; the check latency by stage); `ctl
|
||||
request` shows the verdict; the chat page says "stopped by policy"; the
|
||||
profile lists effective policies; docs/guardrails.md and data.md written;
|
||||
the access log carries action, stage and policy only. Attaching from the
|
||||
portal is not done — the page shows; the console and ctl change.
|
||||
|
||||
- Gateway-level policy library in `server.yaml` under `guard:` (see the
|
||||
YAML in the review, reproduced in `docs/guardrails.md` to be written);
|
||||
attachments to scopes in the store via `llmgw keys guard`, the console
|
||||
|
||||
Reference in new issue
Block a user