# S-05 — Autorisierungs-Pipeline
# Category: SHOULD
# Kapitel: 13 – Permissions
# Anker: 13.3 Autorisierungs-Pipeline
# Orientierung: 16:9 landscape
# Didaktik: Mode → Rules → Trust → Sandbox — die Kette vor dem Tool-Call.
# Caption (DE): Mode → Rules → Trust → Sandbox — die Kette vor dem Tool-Call.
# Language: English (Gemini / Imagen)
# Usage: paste entire prompt body below into Gemini

--- PROMPT START ---
Create a clean educational technical illustration, 16:9 landscape.

GLOBAL STYLE:
- flat vector + soft 3D depth; night navy (#0B1B2B), cyan (#2EC4FF), soft violet (#8B7CFF), off-white panels, slate grays
- minimal English labels (2–6 words); no brand logos; no photoreal UI; no watermarks; generous print margins; high contrast
- book context: Grok Build practice guide (agentic coding harness); never Claude Code titles

Title concept: "Authorization pipeline before every tool call".

Composition:
- Left-to-right pipeline stages as glass gates:
  1) Mode
  2) Permission rules
  3) Folder trust
  4) Sandbox
  5) Execute tool
- A tool-call packet travels through; any red deny stops the packet; ask pauses with human key icon.
- Tiny examples under stages: “Plan”, “deny rm”, “trusted?”, “OS fence”.

Precise security pipeline, not fear collage.

--- PROMPT END ---
