Understand GKG, ONNX and version identifiers
Separate model protocols, package formats and release versions.
V4 and GKG5 describe different things
Model protocol V4 describes the data contract between a model and its framework. GKG4 and GKG5 are deployment container versions. GKG5 adds support for decks, replays, documentation and presets. A GKG5 package can still contain a V4 model; it does not mean the network has become V5.
A model may need companion resources
The vocabulary determines card identity encoding, and runtime semantic assets provide card-semantic lookup data. They need to match the model artifact’s declared requirements. A primary model file without its external weights or companion assets may be insufficient for deployment. Clients verify these requirements within their supported formats.
A UUID tracks identity; a release identifies files
A Core model UUID preserves training identity and related artifacts. Continued training or compatible semantic-resource maintenance can preserve that identity while changing file contents. The community therefore distinguishes the model project, release and file SHA256. A digest compares file contents; it is not an author signature or evidence of playing strength.
Attachment support depends on the client
Decks can be optional imports, and downloaded replays need a reader that supports their format. Presets are currently carried and viewed, not automatically applied. A replay inside a package does not mean the website can rerun the model to generate prediction curves. Displaying recorded predictions and running new inference are separate capabilities.