Progress0/0
Phase 1

## Set up the canvas

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

Drop everything in `features/` onto the canvas.

show detail ▾

New tabs appear including Compose — the tab you'll use heavily in this stream.

Phase 2

## Load the tour

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

Drop the three tone stylesheets from `stylesheets/`.

Drop `stream/stream-knowledge-tree.xml` and all six `chunk-knowledge-*.xml` files.

Open Streams. Confirm "knowledge-tree — 6 chunks · all verified ✓".

Phase 3

## Author atomic sections (chunks 1-2)

Read chunk 1 in your preferred tone (Tree → chunk-knowledge-1.xml → pick xsl:tone-public).

Read chunk 2. Author `section-evens.xml`: number A1, title "Even numbers as compositions", lay register, one paragraph.

show detail ▾

    source id: section-evens.xml
    number:    A1
    title:     Even numbers as compositions
    register:  lay
    paragraph: (your idea about even numbers as stable compositional structures)

SEND TO TREE.

Author `section-primes.xml`: number A2, title "Primes as transitions", lay register, one paragraph.

Author `section-glyphs.xml`: number A3, title "Digit glyphs as bounded volumes", lay register, one paragraph.

show detail ▾

You now have three atomic sections — independently addressable, signable, includable in any composition.

Phase 4

## Compose a book (chunks 3-4)

Read chunk 3. Click PASTE. Paste the book stub.

show detail ▾

    <book id="first-book" title="Three ideas on number">
      <metadata><author>Your name</author></metadata>
      <include ref="mr://section-evens.xml/"/>
      <include ref="mr://section-primes.xml/"/>
      <include ref="mr://section-glyphs.xml/"/>
    </book>

If your section source ids differ, update the include refs to match. Click PROCESS.

Read chunk 4. Tree → click your book source. The compose:include reader renders the book with all three sections assembled inline.

show detail ▾

The book is LIVE. Re-author any section (same source id replaces the previous); switch back to the book; it reflects the change. The book references; it doesn't copy.

Phase 5

## Fork + diff (chunk 5)

Read chunk 5. Open Compose. Pick the Fork operation.

Source: `section-evens.xml`. New source id: `section-evens-revised.xml`. FORK.

show detail ▾

The new source is a clone of the original with one addition: a `<fork-source ref="mr://section-evens.xml/" timestamp="..."/>` child that records the lineage.

Open Author tab. Re-author `section-evens-revised.xml` with revised content.

show detail ▾

The fork now diverges from the original. The original section-evens.xml still says what it said; the fork says your revised thing. Anyone walking the lineage can trace which came from which.

Phase 6

## Diff + bundle (chunk 6)

Read chunk 6. Compose tab → Diff operation. Source A: `section-evens.xml`. Source B: `section-evens-revised.xml`. DIFF.

show detail ▾

The output shows the structural delta between original and fork — which paragraphs changed, added, removed. This diff is itself an addressable region you can sign and bundle.

Sign tab. Sign your atomic sections, your book, your fork.

show detail ▾

Each signature attaches to its source root. Forks carry both their fork-source lineage and your signature — derivation and attribution at once.

Bundle tab. EXPORT BUNDLE XML (or HTML).

show detail ▾

The bundle contains your whole knowledge tree: three atomic sections, the book composition, the forked variant with its fork-source lineage, your signatures on each. A recipient drops the bundle and inherits the entire derivation network.

You're done. The derivation network is yours to extend or share.

show detail ▾

A recipient can: fork your fork (lineage deepens), include your sections in their own books, sign their additions, diff against your originals. Each operation extends the graph; each new region carries its provenance forward.

## Knowledge tree shipped.

Atomic sections · live composition via include · cryptographic fork lineage · diff-visible divergence · all in one bundle.