Follow the work from code to screen

Shared explanations of the platform, its contracts and its renderer.

The same source material supports the collector, artist and institution guides. Use these chapters to check an identifier, renderer input or platform behavior.

From code to screen

1. Code post: a transaction and its event history identify content posted to a code page.
2. Art project: the project references that code-post transaction and records its settings.
3. Edition mint: a mint transaction creates an edition with project, edition and token identifiers.
4. Browser rendering: the viewer retrieves the program and supplies edition inputs. The program creates the visual or interactive work.

The browser runs the JavaScript. Metadata and preview images help other services describe an edition; they do not replace its program and inputs.

Reference chapters

• Contracts and identity: addresses, code-page ownership, edition IDs and royalty managers.
• Script reference: renderer contexts, inputs, lifecycle and metadata conventions.
• Storage and metadata: historical source, metadata modes, downloads and verification.
• Current and proposed features: current functionality and prospective extensions.

Authors can also consult seeds, controls, project management and royalties. Reconstruction guidance lives in conservation and archives.

Check a claim against its source

Identify chain, contract, project and block or observation date before treating ownership, price or configuration as current. Use deployed source and project settings to establish permissions. A future feature description is not evidence of a deployed integration.

The LLM index exposes this same chapter structure. Preserve artist credit, distinguish observed behavior from proposed changes, and state the scope of reconstruction tests.