From d9544603804c7cd4f6505a6b226c12e9623c7261 Mon Sep 17 00:00:00 2001 From: Matt Vollmer Date: Wed, 8 Apr 2026 19:55:56 -0400 Subject: [PATCH] docs: rename "Security implications" to "Security posture" (#24181) Renames the "Security implications" section to "Security posture" and reframes the intro paragraph. "Implications" reads as a caveat or warning; the section actually describes built-in structural guarantees of the control plane architecture. > PR generated with Coder Agents --- docs/ai-coder/agents/architecture.md | 7 ++++--- 1 file changed, 4 insertions(+), 3 deletions(-) diff --git a/docs/ai-coder/agents/architecture.md b/docs/ai-coder/agents/architecture.md index 11501b0b54..ec4f0917c5 100644 --- a/docs/ai-coder/agents/architecture.md +++ b/docs/ai-coder/agents/architecture.md @@ -233,10 +233,11 @@ Because state lives in the database: - The agent can resume work by targeting a new workspace and continuing from the last git branch or checkpoint. -## Security implications +## Security posture -The control plane architecture provides several security advantages for AI -coding workflows. +The control plane architecture provides built-in security properties for AI +coding workflows. These are structural guarantees, not configuration options — +they hold by default for every agent session. ### No API keys in workspaces