How a painting becomes a program
The path from a budgeted authoring plan to stored brush instructions, canonical painting state and a separately edited film.
Implemented research interface · work-scoped readiness
Plan, author, replay.
The public research entry point exposes catalog, create_plan, author and replay. The catalog checks a profile’s pinned inputs and validation receipts. A plan records intended authoring work, budgets and seeds; authoring executes through the staged work-plan machinery and emits a stored native program and artifacts.
Module, plan and native-program versions are separate contracts. A catalog entry is not proof of a ready backend, and a compiled plan is not evidence of completed execution. Registered profiles refer to specific works; they are not a universal API for painting any composition as any artist.
The stored instructions are the portable boundary.
Portable replay dispatches a native program to the existing renderer. Its public path does not look up the source reference or model weights. It preserves the supplied program and writes a new rendition and replay receipt to a new output directory.
Programs must be validated against a schema actually supported by the consuming renderer. Initialization, command order, numeric precision and quantization affect the result. Encoded PNG bytes, decoded display pixels and floating-point canvas state have different identities.
Present the painting without replacing its state.
Artist Studio consumes native painting artifacts through an adapter that verifies program identity, uses an explicitly selected engine checkout and advances the original commands. Deterministic prefix reconstruction and snapshot checks preserve the authoritative state.
The film adds a separate timeline: a digital artist portrayal, camera movement, partial reveals and editorial cuts. An illustrative brush path is not a recovered historical gesture. Graded, compressed or partially revealed frames must not replace the canonical painting state or its identity.
What the records carry
| Record | What it carries | How to interpret it |
|---|---|---|
| Authoring plan | Profile, stages, explicit budgets, mode and seeds | Intended work, not completed painting instructions. |
| Native program | Schema, initialization and original ordered painting commands | The consumer must support this exact program contract. |
| Film derivative | Shots, timing, portrayal, narration and presentation effects | A movie is not the canonical canvas or historical hand motion. |
Methods summary from the inspected research snapshot. Findings described here belong to their stated experiments; this note is not a fresh replication or a peer-reviewed publication.