# Triage record

Capture original report/context; workspace/version; category; impact/frequency/workaround; observed versus reported; duplicate search; readiness; priority rationale; missing input; acceptance; dependencies; next action.

| Readiness | Next step |
| --- | --- |
| Reproducible and bounded | Prepare backlog TSK |
| Missing technical fact | RDT or diagnose experiment |
| Missing owner choice | One focused grill question |
| Duplicate | Link canonical task, retain source |
| Deferred | State reason/owner and revisit trigger |

Example: “High priority because reconnect can duplicate a paid side effect; reproduced on the installed version. Ready after the operation-identity contract is pinned.” Priority is explained by impact and evidence, not the mere presence of a scary exception message.

Do not add Ready/Blocked/Failed as board columns. Preserve the four-column board and encode triage/readiness separately in the body/data. Transitioning Working requires actual owner dispatch, not a triage label.