## Exact components need an exact check, not singleton containment of a rounded enclosure What happened: the independently evaluated expression 5*sqrt(729/25) straddled 27 by about 1e-191. Containing that numerical enclosure in the exact singleton stored as 27 failed, despite agreement of the mathematics. The checker was repaired by simplifying rational c algebraically before ball evaluation; no stored coefficient changed. It now retains exact27 and checks containment for all511 values. What the skill says now: preserve exact values and check the stored interval; finite narrow balls are required. It does not specifically address this possible failure of an independent checker at exact singleton entries. What it should say: when an independently computed enclosure straddles an exact stored value, resolve exactness by a proved algebraic identity or an independent exact computation; finite numerical overlap alone cannot prove an exact singleton, and failure of enclosure containment alone does not establish a wrong exact value. Evidence: T737 at (a,b)=(15,30), independent.py's rational-c cancellation, independent-results.json, readback-results.json. The independent arithmetic construction and local cube identities fix the positive sign. This is a proposal for human review, not a live skill edit.