Anti-context-loss
HTML you can keep.
After the chat closes, the canvas mutates, the share link rots — useful AI work shouldn't die there. A Capsule is one sealed HTML file that survives across tools, time, sessions, and platform churn.
Canvas, Artifacts, html-docs, Workplane do the live editing. htmlbin, MinDev, llms.txt do hosting and discovery. Capsule is the seal step in between — what an artifact becomes when the live work is done.
What it is
One file. Manifest, data, style, root, runtime — all inlined.
AI tools emit HTML by default: reports, dashboards, notes, demos. A Capsule is what that HTML becomes when it's sealed for keeping. The same envelope whether an LLM, a build script, or a human authored it — readable in five years, on any device, without a server.
How it's shaped
Five required blocks. Twelve rules. Zero ambiguity.
<!-- A valid Capsule, in outline --> <script id="capsule-manifest" type="application/json"> { "uuid": "...", "title": "...", ... } </script> <script id="capsule-data" type="application/json"> { ... your snapshot, free-form ... } </script> <style id="capsule-style"> ... </style> <main id="capsule-root"> <!-- the readable artifact, pre-rendered --> </main> <script id="capsule-runtime"> ... </script>
Anatomy · one file, five inline blocks
What this is not
Three lines of fence-posting.
- Not a standard you have to comply with. A loose discipline.
- Not anti-platform. Anti-context-loss.
- Not finished. Active research.
About this page
This page is itself a Capsule per Core v0.3.0. Five required blocks, all inline. No network, no analytics. v2 — forked from the original landing sketch; v0.3.0 applies the HTML Capsule design system.
Loading manifest…