clarify-data

Define what the system knows and what crosses its boundaries — a conceptual entity diagram, field-level ER + YAML contract sheet when persistence exists, endpoint map / cross-boundary sequences when interfaces exist; error taxonomy cross-checked against failure scenarios. Invoke ONLY when the user names clarify-data or clarity-flow enters the data step; never self-activate from a data-model remark.