Handoff must show both extreme-long and extreme-short content

What it is

If the package only shows “Jane Doe” and a one-line title, that comfortable sample is what gets built. Extreme-length content frames are paired screens for the same slot: one with the shortest content the product will display, one with the longest. A note that says “watch the length” does not count. Wrapping, collapsed centering, and a single glyph floating in a large field are discrete layout modes; if they never appear in the file, they are not treated as states the code must honor.

This is about the two ends of length inside a slot, not about whether a collection has members, and not about how an empty board talks when loading fails.

Why it happens

Design tools fill with content that looks finished: a two-character name, a title that fits, a description that stops mid-card. The eye reads that frame as the interface; engineering writes constraints against the visible structure — size, line count, alignment tuned to the comfortable string. When length departs, no second geometry was declared. Short copy glues a title to its metadata, or leaves a large numeral adrift. Long copy shoves a neighboring action off the card, or turns a single-line label into two lines and wrecks the row baseline.

The ends do not substitute for each other. Ship only the long frame and the implementation locks a filled height; short content then leaves a vacant hole. Ship only the short frame and the implementation locks a single line; long content can only clip or burst. Both geometries have to be present so they become two branches rather than an average.

Where it stops holding

Fields whose length is nailed by a protocol — a six-digit code, a three-letter currency — have no extrema to draw; inventing them is a fake edge. Icon-only and chart-only slots move the problem into graphic scale, not text frames. Print at a fixed trim is a crop problem; on a scrolling screen, “give the long frame” is not “forbid scrolling.” User-generated paste can be arbitrarily long: the extreme you draw is the display ceiling the product accepts, not the attack-payload ceiling. Input limits belong elsewhere.

Applying it

• For every slot that eats live data, ship two frames that share spacing and alignment: shortest displayable content, longest displayable content.
• Put both frames on the same page of the package. Do not leave the happy path in the flow and hide the extrema on a private board.
• Do not fake length with repeated glyphs. Use the shape that slot actually sees: a compound family name, a ticket title with a subtitle.
• Paste a real shortest record and a real longest record into the built UI and overlay them on the two frames. Line count, alignment, and neighboring controls should match. If only the happy path matches, the slot has not shipped its ends.

Related

• Same group: R2.05.2 Zero, one, and many each need their own defined layout · R2.05.3 Whatever is left unspecified will be invented by the implementer · R2.05.4 Bound values come from real distributions, not imagined extremes · R2.05.5 Overflow behavior must be specified separately by content type · R2.05.6 Stacked edge cases need their own frames
• Adjacent: R2.01 Annotation and asset export · S1.01 Text Expansion and Layout Resilience
• Search terms: extreme-length content frames · content extrema · handoff length samples