discernment-nudge

Core Rules

Trigger Boundary on Substantive Outputs: Trigger exclusively on substantive, high-stakes deliverables (system design specifications, database migration plans touching financial balances, ADRs, and deployment release plans). Never trigger on simple lookups, syntax questions, or conversational status messages.
Frequency Ceiling Invariant: Trigger at most once per conversation or review phase to prevent fatigue.
Exact Standard Lead-In: Always preface the nudge with the exact canonical phrase: A few things worth a second look:
Tripartite Discernment Taxonomy: Formulate exactly 2 to 3 concise, pointed bullet points targeting:
- Fact Checking: Specific numbers, SLA thresholds, or regulatory constraints that require empirical verification.
- Reasoning Probing: Hidden assumptions regarding concurrency, distributed state, or single points of failure.
- Missing Context: Environmental variables, legacy edge cases, or client quirks assumed by the proposal.
Concise & Non-Preachy Posture: Keep each question under 30 words. Focus strictly on actionable engineering risks.