diff --git a/BACKLOG.md b/BACKLOG.md index 70a092c..b93f3cf 100644 --- a/BACKLOG.md +++ b/BACKLOG.md @@ -771,7 +771,10 @@ somebody restarts the right service on every machine. The rule from here on: cluster's, kept in the store, changed through ctl, the console or the web, audited, and in force on every control plane within seconds.** -### E1. Cluster settings in the store (L) — in progress +### E1. Cluster settings in the store (L) — done 2026-10-05 +Live on the PoC (140, 150): imported as version 1; a guard change applied on +both without a restart; a router change restarted the standby at once and the +leader 30s later with /health answering throughout; rollback did the same. - Table `cluster_settings` (versioned YAML document, who and why). The cluster-wide part of server.yaml lives there; server.yaml keeps the per-machine keys only (listeners, TLS paths, store DSN, secrets, tracing, diff --git a/internal/cli/guard.go b/internal/cli/guard.go index a68af36..d99ab6c 100644 --- a/internal/cli/guard.go +++ b/internal/cli/guard.go @@ -14,7 +14,8 @@ func newGuardCmd(client func() *ctlClient, asJSON *bool) *cobra.Command { c := &cobra.Command{ Use: "guard", Short: "Guardrail policies: which apply where", - Long: "Policies are defined in server.yaml under guard.policies — what requests and\n" + + Long: "Policies are defined in the cluster's settings under guard.policies\n" + + "(llmgw ctl config edit; in force everywhere within seconds) — what requests and\n" + "answers are checked for (personal data, secrets, prompt injection, patterns,\n" + "tools) and what is done: flag, redact or block. guard.default applies to\n" + "every request; attach others to an organization, team, project, user or\n" +