The objects

01The objects

Two objects exist. Each is a finished, designed, interactive page sold as one self-contained HTML file, in an edition of 25 that retires permanently once it is sold out. The figures under each are measured from the file that is actually delivered.

• Object 01 Available now Edition of 25 · first 5 at $99, then $199

  The Agent Chronometer

  An interactive 3D site: a smoked-glass instrument that opens into six labelled petals over a working brass mechanism.

  What it demonstrates: That a full Three.js scene — materials, lighting, camera choreography, seven authored states and four direct-manipulation gestures — fits inside one document that fetches nothing at runtime.

  The first object. It set the delivery contract every object since has kept: one file, no build step, no runtime network requests.

  File

  one self-contained HTML document

  On disk

  704,811 bytes

  Over the wire

  187,269 bytes gzipped

  Runtime requests

  0

  Renderer

  Three.js r185, inlined

  Named scene parts

  40

  States · gestures

  7 authored states · 4 gestures

  Editable slots

  6 annotations, one per petal

  Fallbacks

  reduced-motion path · no-WebGL still

  Open Object 01

• Object 02 Available now Edition of 25 · first 5 at $79, then $149

  Visage

  A generative portrait page: a face in profile wrapped in contour lines, with a colour signal travelling the lines on a seamless loop.

  What it demonstrates: That the single-file contract is not tied to one renderer. Visage is canvas, not WebGL, and holds a fixed camera — the geometry never moves, only the colour travelling along it.

  The second object, and the proof that the format generalises: a completely different technique under the identical publish contract.

  File

  one self-contained HTML document

  On disk

  548,530 bytes

  Over the wire

  403,717 bytes gzipped

  Runtime requests

  0

  Technique

  canvas contour field on a seamless colour loop

  Camera

  fixed — the geometry does not move

  Fallbacks

  responsive layout · reduced-motion path

  Open Object 02

• Object 03Unannounced

  In the workshop

  The next object is not announced, and this index is where it appears when it is. Each object is a different technique under the same contract: one document, no build step, nothing fetched at runtime.

02What you are actually buying

An object is not a component library, a UI kit, or a theme to assemble. It is the finished page — the thing normally produced as a commission — sold as a file. You supply the words and the branding; the machinery underneath is already done, and it has no dependencies to install, update, or outlive.

• What a single-file website is — what self-contained means, how to verify it, and what it costs you
• Shipping an interactive page with no build step — how you edit and deploy one without npm or a bundler
• An object vs a template, a kit, or a commission — what actually differs, structurally
• How the edition of 25 works — the cap, who enforces it, and what retirement means

03See the craft for free

Specimen 01 is a small self-contained page we give away: drop any HTML file on it and it reports the file's size, its gzipped size, and every external reference it still carries. It is the instrument for checking the claim this whole site makes — including against our own objects — and it is itself a single file that fetches nothing.

04When an object retires

Nothing is unpublished. When an edition closes, its page stays where it is and this index keeps the record: what the object was, what it demonstrated, and which object took its place. Owners keep everything they bought — unlimited personal and commercial use, modification, and client work — and no new copy is ever sold.