A.19.CN:10 - Didactic quick cards (one‑liners teams reuse)

1. Numbers travel with their basis. Cite the characteristic and scale editions, bearer, reference or comparison basis, scope/window, and result.
2. If the normalization is not declared, the trend is fiction.
3. The intended result selects the law. Use a weakest-part bound only when its declared dependency model justifies it; a safety label alone selects no fold.
4. Admit → Assert → Act. (CN‑frame admission → RSG StateAssertion → Method step).
5. Relate before reuse. When local meanings differ, establish the exact Bridge, then state the separate receiving use, direction, rule, and tolerated loss.
6. When independence is required, check who made the basis. A later role assignment does not remove self-certification; a sufficient uncertified comparison remains possible when no independent certification is required.
7. Ground each chart value. Name the reference state and coordinate patch. For measured values, cite the applicable measurement method and protocol; for evaluated or otherwise ascribed values, cite their rule and basis.
8. Deprecate in the open. CN‑frame cards carry DRR & retirement plans.
9. Keep characteristics few, meanings sharp. Prefer ≤ 7 characteristics per CN‑frame.
10. Identify the normalization used. Cite its method and instance under A.19.UNM; ordinary mathematical mapping language alone identifies neither.