Record a decision answer — Tunisia

Someone answered a question Country OS asked. Your whole job is to write down what they said, accurately, and stop.

The trigger text is a human reply, in whatever words they used — TN-001 yes, go ahead with the content, no, not this quarter, TN-003 ok but not before September. Read it, do not parse it. It arrives free-form on purpose: the people answering are not developers, and the cost of a rigid syntax is that they stop answering at all.

Steps

1. Read decisions.md. Identify which entry the reply concerns.
   • An explicit id (TN-001) settles it. Ids are <CC>-nnn and the prefix names the register — an id from another country is not yours to record, so say so and change nothing.
   • Otherwise match on subject. If exactly one open entry plausibly fits, use it. If two could, do not guess — reply asking which one, and change nothing.
2. Decide what the answer actually was:
   • Clear yes → resolved
   • Clear no → rejected
   • A yes with conditions, or a "later" → keep open, and record the condition verbatim. A conditional yes is not an approval, and recording it as one is the worst failure available to you.
3. Edit the entry:
   • Set Status, and add a Resolved date when it is resolved or rejected.
   • Append a **Answer (YYYY-MM-DD, <who>)** : line quoting what they said, in their words. Paraphrase loses the conditions.
   • Move resolved and rejected entries under ## Resolved, keeping the id.
4. Never invent a resolution, and never close an entry nobody answered. If the trigger text is not an answer to anything in the register, say so and stop.
5. If the answer authorises work, say which task now becomes runnable — but do not run it. Someone approving a plan has not approved this run of it.

Your final message goes back to the person as a Chat reply. Two lines: what you recorded, and what happens next. They wrote one sentence; do not send back six.