vtx.foundation draft d03

VTX 1 · core · beta draft d03

VTX 1 Wire Specification: core

Oct 11, 2026, revised Nov 16, 202639 pagesALPN vtx1-d03MIT licence

§18Fallback rendering

A server must show layer 2 content to clients that cannot render it: a cell client without the core catalog, and a plain terminal reached over SSH or a serial line with no VTX client at all. The server then renders the content itself.

  • For a cell client, the server renders each region into a grid of the client's width, using the fallback column of the core catalog table (Section 9), and each node's fallback for other types.
  • For a plain terminal, it writes the same lines as VT bytes, using only what the terminal named by TERM supports.
  • Widths follow the grapheme and width rules of Section 8. Text wraps at word boundaries; table columns shrink to fit and their cells end in … when cut.
  • When the scene changes, the server redraws only the lines that changed, in place.
  • On a cell client, the server keeps the grid's last row for prompts and answers. The rows above it show the content and scroll with PageUp and PageDown.

Input. Keyboard answers become the same INTENTs a component client would send, with the same source, region, values and seq, so the application cannot tell the difference. Menus take numbers, forms prompt for one field after another, checkboxes take y or n, and Escape cancels a form or closes an overlay.

Approvals on plain terminals. With no trusted zone, the server keeps the bottom line as a status line, with a scroll region (DECSTBM) above it, and asks there. A high-risk approval needs the request ID typed in full, not just y. uv approvals are answered unsupported. Such an approval is only as trustworthy as the server and the path to the terminal; applications that need proof of the user's intent require a VTX client.