Known issues
Divergences are where code and design intent disagree; open decisions are where nothing has been decided yet. Neither is resolvable by inference.Gaps in the current rules
Layout is the least specified foundation in Titan. Do not infer answers to any of these.- The specification’s breakpoint vocabulary doesn’t correspond to what ships. It names
breakpoint-tablet-min,breakpoint-desktop-min, andbreakpoint-desktop-max— three bands — as tokens; none ship. The code has five unnamed numeric breakpoints and no breakpoint tokens at all. See TITAN-DIV-09 and TITAN-GAP-12. - No layout tokens exist at all. No container max-width, no page gutter, no column count, no sidebar width. Every one of those is currently a per-view decision with nothing to check it against.
- The breakpoint values are unvalidated. No evidence they were checked against Invoca’s viewport distribution, and no decision is recorded for them.
- No maximum content width is defined. On a 2560px monitor a full-width text region produces line lengths far beyond the ~75-character readable maximum. Nothing prevents it.
Grid’s off-scalespacingprop is not documented as a hazard anywhere in Titan. See TITAN-LAY-03 below.- No guidance exists on breakpoints vs. container queries. Both are available; nothing says which to reach for.
- No published page-region model. Views is the tier meant to answer this and is entirely stubs. Until it is written, page structure is undocumented.