Record a decision answer — _global

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

This workspace is not a country: its register holds platform-wide questions and defects in the shared application repos, so an answer here can affect every site at once. That raises the cost of paraphrasing, not the amount of interpreting you are allowed to do.

The trigger text is a human reply, in whatever words they used — OS-001 yes, no, not this quarter, OS-002 raised the pool to 200, watching it. Read it, do not parse it. It arrives free-form on purpose: the people answering are not all 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 (OS-001) settles it. Ids are <CC>-nnn, and OS- is this register's prefix — a TN-/DE- id is a country's entry, not yours. Say which workspace it belongs to 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 becomes runnable — but do not run it. Someone approving a plan has not approved this run of it.
   • Check that a task actually exists for it before implying one does. Several answers here authorise work no _global task may perform: hard rule 1 limits this workspace to minimal maintenance, and hard rule 4 forbids touching dependency manifests at all — so "yes, migrate off the abandoned package" is a job for a human team, and saying so plainly is the useful answer. An authorisation nobody can act on is worth recording and worth being honest about.

Your final message goes back to the person as a Chat reply. Two lines: what you recorded, and what happens next — including "nothing here can do this" when that is the truth. They wrote one sentence; do not send back six.