diff --git a/backend/guide_qa.py b/backend/guide_qa.py
index 0485046..0ddbe96 100644
--- a/backend/guide_qa.py
+++ b/backend/guide_qa.py
@@ -76,10 +76,10 @@ def ziel_ohne_anker(cards: list[dict], ziele: list[dict]) -> list[str]:
 # ein dichter Sub (viele key_points, Fakten, Beispiel) trägt mehr Text als ein Einzeiler.
 # Die Pipeline (Writer-Vorgabe, Prüfer-Trigger, Fix-Ziel) nutzt DIESELBE Formel mit engerem
 # Band — Messlatte und Fix-Auftrag müssen übereinstimmen, sonst sind Befunde unfixbar.
-BUDGET_BASIS = 200        # Einstieg/Übergang je Sub
-BUDGET_KEY_POINT = 160    # ~1–2 Sätze Erklärung je key_point
-BUDGET_FAKT = 60          # zitierter Fakt, in den Text eingewoben
-BUDGET_BEISPIEL = 250     # ausgearbeitetes Beispiel
+BUDGET_BASIS = 140        # Einstieg/Übergang je Sub
+BUDGET_KEY_POINT = 110    # ~1 Satz Erklärung je key_point
+BUDGET_FAKT = 45          # zitierter Fakt, in den Text eingewoben
+BUDGET_BEISPIEL = 170     # knappes Beispiel
 LAENGE_BAND = (0.35, 1.5) # QA-Toleranz um das Blockbudget
 
 
diff --git a/templates/Prompt/Guide-Writer-Board.md b/templates/Prompt/Guide-Writer-Board.md
index ae7f64b..c417082 100644
--- a/templates/Prompt/Guide-Writer-Board.md
+++ b/templates/Prompt/Guide-Writer-Board.md
@@ -24,7 +24,7 @@ HOW TO WRITE the detailed version — ONE coherent text for a junior who is lear
 - Resolve EVERY technical term at first mention in half a sentence. Use "Prerequisite" hints as anchors, "Hurdle" hints to clear misconceptions up front.
 - Order of the subblocks as in the assignment: first `[beginner]`, then `[advanced]`, then `[expert]`, last `[peripheral]`.
 - The NUMBER of subblocks is the depth signal: many subblocks → the block deserves length; few → keep it short. Never pad.
-- LENGTH TARGET for the detailed version: about {budget} characters total (guideline, not a hard limit — covering ALL learning objectives always beats brevity). Unguided sections came out 2–4× too long and had to be rewritten.
+- LENGTH CAP for the detailed version: {budget} characters total — a HARD ceiling, not a target. Cover EVERY learning objective, but write DENSELY: fewer words, not more; prefer cutting a sentence to adding one. If you approach the cap, tighten — do not spill over. Overshooting gets rewritten.
 - CONCISE: every sentence carries new information. No repetition, no filler, no preamble. When in doubt, leave it out.
 - Show "how" procedures step by step. An example ONLY where it genuinely carries the understanding.
 - If VERIFIED WORKED EXAMPLES are provided above, weave each into its subblock as instructed there; do NOT invent additional worked examples for subblocks that already have one.