October 2026 documentation updates

2 October 2026 — guardrail configuration guidance

The public documentation now covers the latest policy-builder and pattern configuration changes. This is a documentation update, not a new SDK or server version announcement. The described editor and validation behavior requires a gateway deployment containing these changes; publishing this site does not deploy them.

• Policy-card editing: use Settings for enablement, failure action, severity, summary, redaction replacement, and preset selections. Use Patterns / JSON to inspect generated checks or enable a card override.
• Pattern overrides: an override replaces the card’s generated detectors and lists. The card’s Settings retain control of action, severity, summary, and enabled state. Per-check scopes can narrow the card’s supported stages.
• Saving and publishing: Save details updates the policy draft; Save Policy saves and publishes an existing policy. Create Policy creates a draft that must be published explicitly. Reset to generated settings removes an override. Review the effective configuration and test both matching and allowed examples before publishing.
• Regex validation: policy management validates expressions using the runtime’s Go/RE2 parser. Lookaround and backreferences are unsupported. Invalid configurations return errors when policies are created, updated, published, or rolled back.
• Preset catalog: the new catalog guide explains coverage, examples, and limitations. Authoritative version 2 policy checks retain their saved configuration; legacy builder policies regenerate against the installed catalog and should be reviewed and republished to pin their checks.

See Guardrails and the guardrail pattern catalog.

The homepage and changelog also now identify Python SDK 3.0.0 separately from the Server 2.8.3 compatibility reference, with the RAG migration and redaction-decision notes collected in one release entry.