==============
Decision Tools
==============

Tools for proposing, resolving, and querying decisions and questions in
the space.

Use ``propose_decision`` for choices that involve tradeoffs, judgment, or
non-obvious analysis — moments where a different reasonable person might
choose differently. Do not track mechanical or purely deductive steps.

----

Tools
-----

``propose_decision``
    Record a proposed decision for the group.

    - **text** (*string, required*) — description of the proposal, the
      tradeoff, and the rationale

``resolve_decision``
    Mark a decision as resolved or rejected.

    - **decision_id** (*string, required*) — ID of the decision to update
    - **resolution** (*string, required*) — explanation of the outcome
    - **status** (*string, optional*) — ``resolved`` (default) or
      ``rejected``

``list_decisions``
    List decisions in the current space, optionally filtered by status.

    - **status** (*string, optional*) — ``proposed``, ``resolved``, or
      ``rejected``; omit for all

``list_questions``
    List questions in the current space, optionally filtered by status.

    - **status** (*string, optional*) — ``open``, ``answered``, or
      ``deferred``; omit for all

----

Decision Lifecycle
------------------

A decision moves through three states:

1. **proposed** — created by ``propose_decision``
2. **resolved** — closed with a positive outcome by ``resolve_decision``
3. **rejected** — closed with a negative outcome by ``resolve_decision``
   with ``status="rejected"``

Future agents can call ``list_decisions`` to understand why things are
the way they are. Tracking decisions at proposal time is more reliable
than reconstructing rationale after the fact.