Known issues
Gaps in the current rules
- No token deprecation mechanism exists. No field, no marker, no convention — verified,
not assumed: no token carries a deprecation marker (zero matches across
primitives,semantic,component, andtypographysource files), and the token manifest has no lifecycle field (each entry isname,tier,axis,$type, andvalues— nostatus, nosince, nodeprecated, noreplacedBy). See TITAN-GAP-19. - No component deprecation convention is documented either, though the component pages
carry a
tagin frontmatter that could hold one. - No breaking-change policy. What counts as breaking at the token layer — a value change, a rename, a removal — is not stated.
- No supported-version window. How long a consumer can stay behind is undecided.
- No migration-guide convention. When a name changes, nothing says where the old-to-new mapping is published.