Publish a page that is itself a canvas.

The canvas boots showing the title, drop zone, and just the Tree tab.

New tabs appear: Streams, Identities, Sign, Transforms, Endpoints, Compose, Schemas, Console, Bundle.

stylesheets/xsl-tone-terse.xml
stylesheets/xsl-tone-public.xml
stylesheets/xsl-tone-annotated.xml

stream/stream-page-build.xml
stream/chunk-page-1.xml … chunk-page-6.xml

The Tree shows a new source whose root is <page> with title "The case for cellular publishing", metadata (author/date/license), and three sections each containing one paragraph.

To customize: open page-example.xml in any text editor, edit the title, metadata, and section content to whatever you want to publish, re-paste into the canvas via the PASTE button. The new version replaces the old.

The Transforms tab now shows "publication" as a new transform. The readers registry gains xsl:publication.

The render area now shows your page as a styled article: header with title and byline, numbered sections, properly typeset paragraphs.

Click back to xml-structural to see the raw tree; click xsl:publication again. Same data, different rendering — XSL stylesheet as a pure presentation layer.

A <signature> element appends as a child of the page. The xsl:publication stylesheet ignores it (its templates only match content), so the rendered article still looks clean.

Your browser downloads a single HTML file (~90 KB) containing the canvas + all loaded features + your page + your signature + the public keys needed for verification.

What boots is a complete Memeroot canvas with your page already loaded as a source.

Your published page renders the same way it did in your original canvas. The recipient sees what you intended them to see.

The signature reader runs WebCrypto verification in the new canvas using only the public key embedded in the bundle. ✓ verified — no server, no network, no platform required.

Email it. Host it on a static site. Attach it to a message. Whatever recipient opens it has a complete Memeroot canvas with your signed page inside.

The artifact is the medium. Each artifact is also a generator: a recipient could fork your page in their canvas, sign their derivation, export their own bundle.html, and the chain of attribution continues.