GAMING VERTICAL

A game is a paradigmatic multi-component work — code, art, music, characters and worlds, plus voice and motion-capture performances — wrapped around large volumes of user-generated content. Games aggregate more distinct rights layers than almost any other medium: copyright in code, art and music; character and world IP; and performers’ rights in voice and motion-capture work. On top of that sits user-generated content — mods, custom levels, in-game creations — whose rights are usually governed by platform terms rather than the studio alone. Generative AI enters as AI-generated in-game assets, AI-driven characters, and tools that remix existing game content.

Component Rights Architecture already fits a multi-layer work like a game. NILP covers voice and motion-capture performers. Source-material records assets that draw on prior work, and output-provenance flags AI-generated assets. Output-licence and the CDR carry use terms and lineage. The gap is structure for user-generated content and performer consent at scale.

1 — User-generated-content rights declaration (QUEUED): how mods and player creations inherit, or depart from, the studio’s rights position. 2 — Performer consent at scale (QUEUED): machine-readable voice and motion-capture consent across large casts. 3 — AI-generated-asset disclosure (QUEUED): declaring which in-game assets are AI-generated and on what terms. 4 — Streaming / derivative permissions (QUEUED): the position on let’s-plays, clips and other derivative uses.

Legal references on this page are to well-established general doctrines only — no specific statutes, section numbers, dates, or figures are asserted. Qualified counsel should review before any of this is treated as authoritative. The field families listed above are not yet specified.

Component Rights Architecture (v3.4) for multi-layer structure. NILP Architecture for performer consent. Output-Provenance Architecture (v3.17) for AI-generated assets. cip.md Generator for operator declarations.