You just opened a workbook.

No install, no account, no server — this page is the file you downloaded, running from your Downloads folder. It will now explain what's inside it, by demonstrating everything live.

This whole thing is one file

Interface, code, data, and the words you're reading — one .html. Right now this file is of text. Right-click → View Page Source and you can read every byte of it; nothing is hidden, nothing was fetched. You could email it, AirDrop it, or put it on a floppy.

There's a compiled engine in here

This is not a video. Every pixel below is computed on your machine, every frame, from scratch — by a compiled WebAssembly program (assembly-level code, the kind C and Rust compile to) embedded in this file as 349 bytes. It is diving into the Mandelbrot set, an infinitely deep mathematical object. Click anywhere to steer the dive.

warming up…

Watch the counter — tens of millions of arithmetic operations per frame, from a program smaller than this paragraph. Workbooks carry whole databases, game engines, and compilers exactly the same way; this one is just small enough to read.

There's data in here — shipped in the file

Workbooks carry their data with them. This one shipped with a reading list inside the file itself ( rows — look for id="dataset" in the source). Full workbooks take this much further: a real SQLite database riding in the file — queryable tables, images, whole file systems.

nothing saved yet

And an honesty note, because it matters: that notebox will survive closing the tab — but it's your browser remembering, not this file. A downloaded static file can't rewrite itself on your disk. Making the data layer truly live — written back, synced, durable — is exactly what docking into a Nexus is for. Files carry; engines remember.

There's intent in here — written down

Every workbook carries a plain-text layer where humans and AI agents both read and write: the spec, the tasks, the project's memory. This file's own org layer (yes, it really planned itself):

* hello-workbook  the file that explains itself
** tasks
DONE say hello without a server
DONE dive a 349-byte fractal engine from inside the file
DONE tell the truth about what a static file can't do
TODO dock into a Nexus and come alive
** note
agents read this layer the way you just did.

The part a file can't do alone

Everything above worked with zero infrastructure — but notice what didn't happen: nothing ran while this tab was closed. A file can't keep schedules, host agents, or serve other people. That's what docking into a Nexus adds — and it's the next chapter of the page that sent you here.

made of standards · runs anywhere · yours to keep — back to the lesson · what the Nexus adds →