record-decision

name	record-decision
description	Update decisions.md after a material accept/reject event. decisions.md is the user-facing curated rationale log (separate from auto-generated summary.md). Use whenever the user accepts a meaningful proposal, includes an instrument, or rejects something with a stated reason.

Record decision

When to use this

• User accepts a proposed-questionnaire.json or a non-trivial suggestion.
• User selects an instrument license path (inline vs reference).
• User rejects a proposal with a reason worth preserving.
• A clinical threshold or wording was chosen with explicit rationale.

Do NOT use for trivial edits (typos, single-word fixes). Those clutter the decisions log.

How to do it

decisions.md is human-edited; we APPEND, never rewrite.

1. Read current decisions.md (may not exist).
2. Append a new bullet under a date header. If the date header already exists for today, append to that section.
3. Each bullet captures: what was decided, why, and the source (citation, instrument canonical URL, or user request 2026-05-12).

Format:

## 2026-05-12

- **Included PHQ-9 inline.** Public domain in this jurisdiction.
  Anchored on USPSTF screening recommendation
  (https://www.uspreventiveservicestaskforce.org/...).
- **Set MIDAS threshold for "severe disability" at >= 21.**
  Source: Stewart et al. 1999 (PMID 10234121); aligns with the
  MIDAS scoring guidance.

Output

After appending, do NOT mention decisions.md in reply.md unless the user asked for it explicitly. The artifact speaks for itself.

Pitfalls

• Restating what the diff already shows. The bullet should capture the reason, not the change.
• Appending to the wrong day's header (timezone confusion). Use the user's local date if known, else UTC.
• Treating decisions.md like a changelog. It's a rationale log — the WHY, not the WHAT.