# Memeroot · Page Build **Start here:** open `GUIDE.html` in a browser. Seventeen tick-boxes from "extracted the zip" to a self-contained HTML file you can publish anywhere. Progress saves automatically. ## What this stream demonstrates **The recursive close.** A Memeroot canvas can author content, sign it, and export an HTML bundle that's itself a Memeroot canvas containing the signed content. The artifact is the medium. - **Page**: a `` XML wraps metadata and sections — the publishing primitive - **Stylesheet**: `xsl-publication.xml` matches ``, ``, `
`, `` and renders the page as a styled article - **Signature**: ECDSA-P256 attribution by your identity, attached to the page root - **Bundle**: the entire workspace serialized as a single HTML file that opens as a fresh canvas with your page loaded Open the exported bundle.html in any browser. It boots as a complete canvas. Your page is in the Tree. Your signature verifies via WebCrypto in the new canvas — no server, no network, no platform required. ## What's in this zip ``` memeroot-page-build/ ├── GUIDE.html ← open this first ├── README.md ← you are here ├── canvas/MR-CANVAS-v0.8.html ├── features/ ← ten feature XMLs ├── identity/identity-tour-author.json ├── stylesheets/ │ ├── xsl-tone-{terse,public,annotated}.xml ← for tour chunks │ └── xsl-publication.xml ← renders as article ├── examples/ │ └── page-example.xml ← editable page skeleton └── stream/ ├── stream-page-build.xml └── chunk-page-1.xml … chunk-page-6.xml ``` ## What you publish After completing the tour, you'll have: - A bundle.html (~90 KB) on your downloads folder - Anyone you give it to opens it in any modern browser - They see your page rendered as a styled article - They verify your signature in their browser using only what's embedded in the file - They can fork your page in their canvas and continue the chain This is publishing without the platform. The file IS the publication.