hype-discipline-pairing

name	hype-discipline-pairing
description	Welds bold forecasts to plain limits, one real verification habit, paradox framing (capable yet brittle), and honest benchmark skepticism. Use when writing about agents, autonomy, or LLMs and preserving trust in the same breath as excitement.

Hype–Discipline Pairing

Distilled pattern: keep radical forecasts credible by locking arms with boring engineering in the same narrative pass.

When to use

• You are excited about autonomy, speed, or a new default workflow.
• You can already hear the “but it hallucinates” replies.

Steps

1. Grant the limitation plainly — Stochastic, opaque, wrong sometimes. No mysticism.
2. Name one guardrail you actually use — Tests-first, review gates, typed boundaries, human approval on writes, etc.
3. Tie guardrail to the new workflow — Explain why the old guardrail morphs (e.g., tests become the contract for agents).
4. One sentence on misuse — What should people not automate yet?
5. Package paradox — When the tech is both surprisingly capable and surprisingly brittle, say both in one breath (same paragraph). Readers trust the forecast more than pure cheer or pure doom.
6. Eval skepticism — If benchmarks diverged from felt reality this year, name the gap and what you use instead (demos, production metrics, task suites). This is discipline for claims about intelligence, not a dismissal of measurement.

Anti-patterns

• “Just vibe” with no verification story.
• Safety theater (long lists of principles, zero practices).

Output shape

• Bold claim.
• One paragraph: limits.
• One paragraph: your default verification habit.
• One line: non-goals.