---
name: reduce-semantic-risk
description: Review or refine forecast specification questions and terms to bound semantic risk; use before using a forecast specification or when auditing resolution rules, exceptions, and resolver discretion.
---

# Reduce semantic risk

Review only plausible ambiguities or missing rules that could change the
outcome. Make ordinary cases mechanical with observable conditions and explicit
rules for relevant boundaries, inputs, calculations, source precedence, and
revisions.

For exceptional cases, replace open-ended judgment with narrow triggers,
evidence requirements, fallback order, escalation, deadlines, correction
windows, and finality where they matter. If an event cannot be enumerated, use
a constrained meta-rule that identifies the decision-maker, governing
principles, remedies, and how the original forecasting intent is preserved.

Present each unresolved issue with its semantic risk, the smallest rule that
bounds it, and any decision the user must make. State the residual risk.

Do not invent facts, authorities, sources, deadlines, or preferences; add
remote edge cases; rewrite the intended event; change approved sources without
agreement; expand into trading, payout, full-contract, or legal-compliance
review; or claim semantic risk can be eliminated. Follow the active record's
server-wide language and approval rules.