An interface is data, not application code.

Drag the file into a browser window. The canvas boots showing just the Tree tab and a drop zone.

Multi-select all the feature XMLs and drag them onto the canvas drop zone. The header counter goes to "8 features". New tabs appear: Streams, Identities, Sign, Transforms, Endpoints, Compose, Schemas, Console, Bundle.

Gives name attribution on the tour author's chunk signatures.

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

Stream declaration first, then chunks. Order of chunk drops doesn't matter — each carries its seq attribute.

Seven green ticks. If any reds, refresh the canvas and re-drop.

To flick tones: click a different tone reader radio in the Inspector. Same chunk, three voices.

Drop it via drag-and-drop or PASTE. The Tree shows a new source whose root is <workflow id="daily-research-log"> with five steps.

Inspect the structure: drill into the workflow source. You'll see step children, each with title and instruction elements. Plain data, no behaviour.

The Transforms tab now lists "workflow" with match patterns for <workflow> and <step>. The readers registry gains an xsl:workflow entry.

The render area switches from structural tree view to a styled checklist with the workflow title, numbered steps, and instructions.

Click back to xml-structural to see the data view. Flick between to feel the separation: same data, different rendering.

source id: completion-1.xml
number:    C1
title:     completion of step 1
register:  lay
paragraph: (what you did to frame today's question)

SEND TO TREE.

If you don't actually want to do AI consultation right now, write a placeholder like "would consult endpoint X with my question Y" — the demo is the pattern, not the AI call.

Even a placeholder works for the demo. The point is to produce a signed artifact per workflow step.

You now have five completion sources matching the five steps. Each is an addressable region.

Type your name, CREATE. Keypair generated in your browser.

For each: pick the source from the dropdown, leave path blank, click SIGN. Each completion gets a signature element verifying authorship.

Optional: sign the workflow source too, declaring "this is my authentic workflow definition".

The bundle wraps your workflow definition, the stylesheet, your completions, your signatures, the tour chunks, and the public keys needed for verification — all in one file.

A recipient drops the bundle into their canvas. The workflow renders the same way it did for you. Your signed completions appear as evidence. They can verify everything end-to-end without contacting you or any service.

The pattern generalizes: forms, surveys, intake questionnaires, multi-step processes, collaborative checklists. Anywhere the interface needs to travel — between organizations, across time, beyond any platform — declarative XML + stylesheets + signed responses is the right shape.