# M-12 — Security priority stack + blast radius
# Category: MUST (Phase F)
# Kapitel: 18 – Security für Coding-Agents
# Anker: Priorisierung Secrets → Isolation → Enterprise → Klassifikation → Scan+Oversight; Enterprise ≠ Architektur
# Orientierung: 16:9 landscape
# Didaktik: Vertikale Priorität links + schrumpfender Blast Radius rechts; unvergessliche Security-Reihenfolge.
# Caption (DE): Security-Priorität: Secrets und Isolation vor Enterprise-Kontrollen; Blast Radius visualisieren.
# Ziel-Asset: assets/illustrations/M-12-security-priority-stack.jpg
# Gate0: Imagine→SVG (zwei Panels + konzentrische Kreise)
# Language: English (Gemini / Imagen)
# Usage: paste entire prompt body below into Gemini
# Complements: M-10 (isolation stages only) — does NOT replace it

--- PROMPT START ---
Create a premium security priority infographic, 16:9 landscape, for a professional practice book on coding-agent security.

OUTPUT SPECS:
- 16:9 landscape; flat-vector editorial; soft depth; print-ready; grayscale-safe
- Serious, calm security figure — pragmatic, not fear marketing

TOPIC:
Prioritize security controls correctly. Secrets out of context and runtime isolation beat decorative enterprise controls. Blast radius shrinks as isolation hardens. Enterprise tooling is not a substitute for architecture.

TITLE (exact):
Security priority stack
SUBTITLE (exact):
secrets first — enterprise is not architecture

COLOR / STYLE:
- Background #F8FAFC; navy #0B1F33; slate #334155
- Priority 1–2: risk red #DC2626 → amber #D97706 urgency
- Mid: teal #0D9488
- Best isolation: green #16A34A
- Soft blue #2563EB optional for scanning tier
- Flat vector; no neon cyberpunk

COMPOSITION — TWO PANELS:

LEFT (~55%): vertical numbered priority stack (1 at top = highest priority):

1. "Secrets never in context"
   sub: "vault inject · no paste"
2. "Runtime isolation"
   sub: "workspace · container · microVM"
3. "Enterprise contract"
   sub: "Privacy / ZDR · content exclusion"
4. "Source classification"
   sub: "who may give which code"
5. "Scan + human oversight"
   sub: "safety net · not architecture"

Number badges 1–5 unique, teal or navy filled circles. Stack clearly ordered top = first priority.

RIGHT (~40%): concentric blast-radius rings (or nested circles):
- OUTER large red circle label: "Host + secrets"
- MIDDLE medium amber/teal circle: "Container"
- INNER small green circle: "Hardened microVM · no secrets"

Visual rule: damage radius clearly shrinks outward→inward (outer worst, inner best). Optional tiny note: "smaller radius = safer default"

CALLOUT CHIP (one, amber or navy):
"Enterprise ≠ architecture"

TYPOGRAPHY:
- English only; short labels; no policy paragraphs
- No vendor sandbox product names as heroes
- No fake exploit screenshots

ALLOWED TEXT:
- Title / subtitle
- Stack items 1–5 with short subs as above
- Ring labels: Host + secrets · Container · Hardened microVM · no secrets
- Chip: Enterprise ≠ architecture
- Optional: smaller radius = safer default

NEGATIVE:
- skulls, hacker stereotypes, robots, brand logos, watermarks, neon matrices, German paragraphs

FINAL SELF-CHECK:
Priority 1 is secrets. Isolation before enterprise. Concentric rings shrink to green hardened microVM. Callout Enterprise ≠ architecture present.
--- PROMPT END ---

# Follow-up edit:
# Keep 1=Secrets top. Rings: outer red host → inner green microVM.
# Preserve Enterprise ≠ architecture chip.
# Align with M-10 vocabulary (Host / Container / Hardened) without duplicating M-10’s four-stage strip.
