Progress0/0
Phase 1

## Set up the canvas

Open `canvas/MR-CANVAS-v0.8.html` in a browser.

show detail ▾

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

Drop every file in `features/` onto the canvas.

show detail ▾

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.

Phase 2

## Load the tour materials

Identities → IMPORT → paste contents of `identity/identity-tour-author.json`.

show detail ▾

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

Drop the three tone stylesheets from `stylesheets/` onto the canvas.

show detail ▾

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

Drop `stream/stream-interface-from-xml.xml` and all seven `chunk-iface-*.xml` files.

show detail ▾

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

Open Streams tab. Confirm "interface-from-xml — 7 chunks · all verified ✓".

show detail ▾

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

Phase 3

## Walk chunks 1-4: see the declarative pattern

Open Tree. Click chunk 1. Pick reader `xsl:tone-public`. Read the orientation.

show detail ▾

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

Read chunk 2. Then drop `examples/workflow-example.xml` onto the canvas.

show detail ▾

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.

Read chunk 3. Drop `stylesheets/xsl-workflow.xml` onto the canvas.

show detail ▾

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

Read chunk 4. In Tree, click the workflow source. Pick reader `xsl:workflow`.

show detail ▾

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.

Phase 4

## Fill in the workflow (chunks 5-6)

Read chunk 5. For step 1 of the workflow ("Frame today's question"), go to Author and create a section: source id `completion-1.xml`, title completion of step 1, lay register, one paragraph describing what you did.

show detail ▾

    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.

Repeat for step 2 (`completion-2.xml`): your initial AI consultation.

show detail ▾

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.

Repeat for step 3 (`completion-3.xml`): critical review notes.

show detail ▾

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

Repeat for step 4 (`completion-4.xml`): source check.

show detail ▾

Repeat for step 5 (`completion-5.xml`): synthesis.

show detail ▾

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

Read chunk 6. Open Identities. CREATE an identity if you don't have one.

show detail ▾

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

Open Sign. Sign each `completion-N.xml` in turn.

show detail ▾

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".

Phase 5

## Ship the interface session

Read chunk 7. Open Bundle. Click EXPORT BUNDLE XML (or HTML).

show detail ▾

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.

You're done. The interface session is portable.

show detail ▾

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.

## Interface session shipped.

Declarative interface · stylesheet renderer · signed responses · transferable as one file.