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
betaThe wire format may still change. Every transport identifier carries the draft number, so peers built from different drafts never connect.

This document specifies the core of VTX version 1 on the wire: transports, framing, channels, handshake, scene operations, input, resources and the trusted zone. It implements the decisions recorded in the VTX spec outline. Surfaces, audio, video, themes, redirection and the rest are extensions of VTX 1, each in its own document; this one defines the core every peer implements and the extension points the extensions use (Section 19 lists them).

§1Status and conventions

This is the VTX 1 core specification, beta draft d03. The wire format may still change during the beta, so every transport identifier carries the draft number: ALPN vtx1-d03 and vtxq1-d03, WebSocket subprotocol vtx1-d03, SSH subsystem vtx-d03@vtx.foundation and Noise prologue vtx1-d03. Peers built from different drafts therefore never connect and misread each other. Each extension carries its own draft number, which peers name in the drafts capability during the beta. When the core is frozen, the bare tokens (vtx1, vtxq1, vtx@vtx.foundation) take over; this document uses those names throughout. After the freeze, a breaking change requires a new major version and new tokens. Sections 17–19 define the application interface, fallback rendering and conformance.

Feature freeze. As of draft d02 (15 November 2026), the core is feature-complete. Draft d03 changes no frame or rule of the core: it moves the transport tokens to d03 and makes the extensions, until then grouped as v2 and v3, extensions of VTX 1, each with a conformance profile and a status (Section 19). Until the wire format freezes, the core takes only fixes that implementations, beta measurements or review turn up; new features go into extensions. The wire format freezes once independent implementations interoperate, beta deployments have measured flow control and the transports, an outside security review has been answered, and IANA has registered the port, ALPN IDs, WebSocket subprotocols and URI scheme. The bare tokens then replace the draft-numbered ones. Each extension freezes on its own, once it is stable.

Revision of 16 November 2026. Changes that keep every d03 peer compatible, so the transport tokens stay at d03: passkeys may be used from clients on other origins that the server lists (Section 5); integral JSON numbers outside the CBOR integer range stay floats in the text form (Section 7); READY may name the signed-in user for the trusted zone, an optional field that older peers ignore (Sections 5 and 12); a line of the application interface is an op when it has op (Section 17); and the fallback rendering of status and the prompt row on cell clients are defined (Sections 9 and 18).

The key words MUST, MUST NOT, SHOULD, SHOULD NOT and MAY are to be interpreted as described in BCP 14 (RFC 2119, RFC 8174) when, and only when, they appear in capitals.

Notation

  • Byte layouts use the notation of RFC 9000 §1.3: (i) is a variable-length integer, (..) a variable number of bytes.
  • Variable-length integers use the QUIC encoding (RFC 9000 §16). The two most significant bits of the first byte give a length of 1, 2, 4 or 8 bytes; values range up to 2^62 − 1.
  • CBOR payloads (RFC 8949) are defined in CDDL (RFC 8610). Map keys are text strings in v1.
  • JSON examples use the text form (Section 7).
  • Resource hashes are SHA-256, written sha256: followed by 64 lowercase hex digits.

Terms

Term Meaning
Client The endpoint that renders and collects input
Server The endpoint that hosts sessions and runs applications
Application The program behind a session: a VT program, a VTX app or an AI agent
Session Server-side state that survives individual connections
Channel An ordered flow of frames inside a connection
Frame The unit of transmission: channel, type, length, payload
Scene The tree of nodes the client renders
Node One element of the scene, identified by a string ID
Region A layer 2 container with its own data model
Op One scene operation, such as open or cells
Intent A typed user action sent from client to application
Trusted zone Client-drawn UI that no server content can draw into or imitate