§6 The VER-F wire profile

The atproto lexicon org.verstandard.record is a projection of the VER Record onto a federation transport. It is a separate artifact with a separate lifecycle, frozen alongside 1.0.0 at standards/ver/1.0.0/wire-profile/ because deployed producers reference it.

The wire profile has no versioning or negotiation mechanism today (finding WIRE-15) — one unversioned NSID, no capability field. The 1.1 draft's strategy (§14.1) is a hybrid: the collection NSID stays stable across VER 1.x; verVersion and cpnpVersion are REQUIRED on the wire and are the negotiation signal; identity- and security-critical structures stay closed; and extensibility is exactly one namespaced ext map that consumers MUST ignore when unrecognised. A new NSID is minted only for a breaking wire major, at which point two NSIDs coexist for a stated dual-publish window. None of this affects the Record standard: a VER-F 2 lexicon still carries VER 1.x Records, and the wire profile's major does not imply the Record standard's.

Wire-profile records MUST propagate verVersion and cpnpVersion from the Record being projected rather than defaulting them (findings WIRE-13, WIRE-14). A defaulted cpnpVersion is a claim about which pixel_hash universe a digest belongs to, and defaulting it is how a consumer ends up comparing hashes across universes.