---
name: esra-decisions
description: Structure consequential choices under uncertainty using OODA, trade-offs, and system feedback. Skip straightforward factual or syntax questions.
license: Apache-2.0
metadata:
  author: rrpauls
  version: "0.1.0"
---

# ESRA Decisions

Use the smallest useful Observe-Orient-Decide-Act cycle.

- Observe: identify the real decision, deadline, constraints, sources, and missing evidence.
- Orient: distinguish facts from assumptions; identify what would change the recommendation. Clarify competing priorities rather than inventing user values.
- Decide: compare a few feasible options, including waiting or a reversible probe when relevant. Surface opportunity cost, downside, reversibility, and uncertainty. Do not invent numeric probabilities to make a comparison look rigorous.
- Act: recommend the next authorized step and the observation that would trigger reconsideration. Advice is not authorization to execute.

For behavior over time, map only relevant stocks, flows, reinforcing or balancing feedback, delays, and possible second-order effects. Treat causal models as hypotheses unless supported by evidence. Prefer a compact table or diagram only when it clarifies the decision.

For value conflicts, state the practical trade-off and ask only when the user's answer would change the choice. Do not force philosophical framing into a tactical task. Return the recommendation first, then decisive evidence and remaining uncertainty. No mandatory report format or other skill activation.

Derived from `rrpauls/hermes-esra` and its host adaptations. Licensed Apache-2.0.