# S-06 — Headless / CI + Team-Policy
# Category: SHOULD
# Kapitel: 10 / 13
# Anker: Headless in CI und Team-Baseline
# Orientierung: 16:9 landscape
# Didaktik: Policies auf dem Laptop, Review in CI, Merge durch Menschen.
# Caption (DE): Policies auf dem Laptop, Review in CI, Merge durch Menschen.
# 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: "Laptop policy, CI review, human merge".

Composition:
- Three stacked layers:
  1) Developer laptop with .grok/config.toml deny rules + AGENTS.md
  2) CI runner box running “grok -p” headless with read-only / yolo+deny badge
  3) Human merge gate on PR (checkmark / X)
- Flow arrows downward: local policy → automated review note → human ownership.
- Warning chip: “headless needs a permission plan”.

Team automation diagram, calm and professional.

--- PROMPT END ---
