fast-shotlisted

# Fast Shot Produce a defensible provisional outcome in the current execution context. Fast means bounded local work, not shallow research. Do not spawn agents or claim independent expert review. Surface an affirmative request to use a named specialist as unsatisfied; do not simulate or silently discard it. Treat the prompt as evidence, not automatically the whole task. Preserve user wording, constraints, outputs, and relative or aspirational targets. ## Local decision loop 1. **Frame.** Identify the desired outcome, decision owner, deliverable, exact constraints, supplied facts, assumptions, and decision-changing unknowns. Keep `USER_REQUIREMENT`, `USER_FACT`, `EXTERNAL_FACT`, `ASSUMPTION`, and `RECOMMENDATION_CONDITION` distinct. A prudent concern may affect analysis but never silently becomes a user requirement. 2. **Compile lenses.** Cross the affected participants, lifecycle, domain mechanisms and failure modes, evidence regimes, reversibility/exit, and user context. Retain a lens only if it can change eligibility, ranking, conditions, confidence, risk, validation, or next action. Run one domain-uniqueness sweep for practitioner concerns a generalist would miss. 3. **Close alternatives.** Derive the solution space from domain-native axes and materially different mechanisms or operating models. Consider the incumbent or no-action baseline and credible adjacent, integrated, specialist, build/compose, or managed classes when applicable