VTX 1 · core · beta draft d03
VTX 1 Wire Specification: core
Resolved gaps (review of 11 October 2026)#
A gap review of the previous draft and the outline found 25 open items: class A gaps would let two conforming v1 implementations disagree (18 items), class B left a v1 goal incomplete (5), and class C was missing from every release (2). All 25 are resolved in draft d01; the table keeps the record of what each one was. Four of them needed a decision, taken as follows: the reference web client runs on an independent origin and servers check Origin; identifiers carry the draft number until freeze; the roadmap gains push wake-ups, exec, port forwarding, session recording, raw keys and enrolment in v2, the A2UI component subset in v1, and brokering, app lists, multi-monitor and surface accessibility in v3; and v1 serial runs PPP under the TLS-over-TCP binding, with bare-metal ARQ experimental. The version labels in this record are those of the time; since draft d03, the v2 and v3 work is extensions of VTX 1.
| # | Gap | Class | Fix in draft d01 |
|---|---|---|---|
| 1 | No application interface (§7, §9, §12) | A | One JSON Lines stream between application and server (stdio, or WebSocket vtx-app1) carrying ops, zone requests and results, intents, input, scene errors and session events, with its own schema |
| 2 | Fallback rendering unspecified (§9) | B | Normative rendering of layer 2 into grids or VT bytes; typed answers become intents; on plain terminals, approvals live in a reserved status line |
| 3 | DANE has no procedure (§2, §5) | A | TLSA at _port._udp or _tcp of the SVCB target, DANE-EE and DANE-TA per RFC 7671, validated DNSSEC; a secure mismatch is fatal, otherwise WebPKI |
| 4 | URI grammar and SVCB details (§5) | A | RFC 3986 grammar without userinfo; target is path plus query; SNI uses the origin host; race vtxq1 and vtx1 per RFC 8305 |
| 5 | Browser client trust (§2, §12) | B | Zone guarantees hold only for client code the server does not serve; serve the reference web client from an independent origin; servers check Origin |
| 6 | OIDC redirect and nonce (§5) | A | Fixed loopback and web redirect URIs; a host-bound nonce derived from a WELCOME seed, which browsers and load balancers can compute |
| 7 | Intents lost or doubled on resume (§6, §11) | A | Sequence numbers on INTENT, PASTE and composition commits; READY reports the last one delivered; the client re-sends the rest |
| 8 | Beta drafts indistinguishable on the wire (§1, §16) | A | Draft-numbered tokens such as vtx1-d01 until freeze; bare tokens reserved for the frozen version |
| 9 | Grid size not tied to layout (§8) | A | Grid size (fill or fixed) and a RESIZE event per grid; the VT engine resizes the PTY on RESIZE |
| 10 | VT engine profile too thin (§8) | B | TERM, COLORTERM, LANG; mouse, focus and synchronized-output modes; colour queries; titles, bell, OSC 52; Kitty and sixel images deferred to v2 |
| 11 | Grid terminal semantics (§8) | A | A per-style op and inline styles, a soft-wrap flag, scrollback clear, Hyper and AltGr modifiers, the unshifted key, palette theming rule |
| 12 | Focus rules (§9, §11) | A | Initial focus order, modal focus trap, and a server focus op that respects a user's recent focus change |
| 13 | Session end and roaming (§6, §14) | A | A session_ended code with exit status; default linger 0; reconnect only to the same host; resume from another device by the signed-in owner |
| 14 | Handshake state machine (§5) | A | Allowed frames per phase; 10 s HELLO and 120 s sign-in timeouts; at most 5 attempts; a fresh WebAuthn challenge per retry |
| 15 | Size limits and request floods (§7, §11–§13) | A | max_update and max_clip limits; continuation frames for PASTE and INTENT; at most 8 pending zone requests |
| 16 | Conformance and registries (§1, §16) | A | Conformance classes with mandatory auth methods; known-answer test vectors; the missing IANA entries and registries |
| 17 | Formatter and field semantics (§9) | A | Placeholder syntax, CLDR plurals, I-Regexp, lengths in graphemes, value types per field, RFC 3339 dates, and a time zone in HELLO |
| 18 | Catalog scoping and versions (§9) | A | A default catalog, prefixed types for other catalogs, immutable catalog URIs with extends, a core icon list |
| 19 | State after CAPS and resume (§4, §5, §10) | A | Channels 3 and 5 open when their capability is added; limits, locale and time zone renegotiable; resources re-offered after READY |
| 20 | Control characters and text direction (§8, §9) | A | Control characters invalid in scene text; bidi and zero-width characters shown in code; lang and dir props |
| 21 | Reaching a detached user (roadmap) | C | v2 notify: content-free push wake-ups (Web Push, APNs, FCM) when an approval is pending |
| 22 | Component states (§9) | B | disabled, busy, readonly and error props; a block markdown component; stable table row keys |
| 23 | Accessibility semantics (§7, §9) | B | Live regions for log and status, description, charts exposed as tables, grids as terminal documents, and role mappings per platform (Section 9) |
| 24 | Transport binding details (§2) | A | v1 serial means PPP carrying TLS over TCP; Noise shows the key fingerprint and disables webauthn and oidc; QUIC stream minimums and reset rules |
| 25 | SSH and RDS replacement features (roadmap) | C | v1: vtx-a2ui for the component subset. v2: remote exec, port forwarding, session recording, raw public keys and enrolment, A2UI media. v3: brokering, app lists, multi-monitor, surface accessibility |