The deck system, rebuilt.

1What the master renders today, beside the same slide rebuilt

Left: M02 · The Problem as RelayCTX - Deck Slides exports it on 2026-09-10, reproduced from the file's own geometry and fonts. Right: the same canon copy through the proposed renderer. Same words. The difference is the system.

2One model, two renderers, one checker

The direction of truth is unchanged: canon, then master, then cuts. What changes is that every arrow becomes a script with a source, and every output is checked before it leaves. Erik's two rules survive as things a build can enforce: the builder builds the master, and the model comes first.

3Flow 9, rendered by the proposed system

Introduction+ (OPEN, shared in confidence): M01 · M02 · M03 · M04 · M06 · M07 · M08 · M09 · M05. Copy verbatim from the Master Copy Deck with the adaptations already governed on the living Introduction; M08 at its canon-ready v3. The provenance line above each slide is what the speaker note carries; nothing reaches a face. Present this cut to see the same stages fullscreen with notes and the one beat each slide is allowed.

Why this cut has no interior drenched moment

The guide's budget is bookends plus at most one interior moment, earned by the slide with the number or claim that deserves the room. The Elevate cut ships M09 with its figure off, so the round has not earned it. The first draft of this page gave the moment to M08 v3 instead, with 25,000+ in amber, and the review of the ElevateIP deck (carried by relay D7EHHS9559) ruled the same composition out on that deck: a big traction number immediately walked back by “majority founder-operated” reads as inflate-then-deflate. So the number sits inside the evidence and the cut runs bookends only. The rule the renderer follows: the moment follows the figure, and a figure that needs a caveat is not a hero. Flip the M09 toggle on and the round takes the moment, with amber on the figure, exactly as the living Introduction renders it.

4The deck that presents itself

A Google Slides file is one thing: a file. The rendered deck above is three: the page an investor scrolls on a gated surface, the screen Erik projects, and the PDF the festival profile carries. Present mode is the part a Slides file cannot be, and it is governed by the motion register rather than by taste.

5The slide model, the flow file, the checker

Built the same day, in this repo: the archetypes are decks/_system/relay-deck.css, the inventory is decks/templates/, the master is decks/master/, the recipes are flows.json, and scripts/build_deck.py cuts a flow and runs the checks below. The master carries the model as data attributes on each slide today; the one-file-per-M-ID form shown here is the port the board proposal asks for.

id: M06
title: How It Moves
gate: OPEN            # the checker reads this
version: 3
date: 2026-06-04
archetype: T04        # Flow
kicker: How it moves
headline: Context that travels.
figure:
  kind: flow
  steps:
    - { name: Send,    text: "Package the context of your work…" }
    - { name: Route,   text: "Relay carries it under your rules…" }
    - { name: Receive, text: "It arrives where it's needed…" }
  chip: { code: A4K9R2, note: "one Code carries it…" }
quote: "No integration project. No platform switch…"
notes: |
  Three beats, then the Code. Never name the envelope,
  the payload, or how routing decides.
rules:
  - "Zero mechanism below the NDA gate."

flow: introduction-plus         # Flow 9
gate: OPEN                      # the ceiling
slides: [M01, M02, M03, M04, M06, M07, M08, M09, M05]
toggles: { M09.figure: off }
vars:
  framing: Investor introduction
  date: September 2026
recipient: null                 # set → stamped export + sent-log row

6Slides stays. It becomes an output.

Erik's rules are kept whole. “Built with the builder against our master template” becomes the builder builds the master. “Master first” becomes model first: the master and every cut regenerate from it, so a derived deck can never carry a fact the model does not.

7The plan, and the five calls that gate it

• Now · before Sept 15Ship the Elevate cut as it standsMerge the Elevate branch after the five sign-off asks; upload the v1 PDF; log it. Register the HTML renderer as a governed path in the deck register, not an exception. Resolve the M44 collision before the additions land.
• Phase 1 · about two weeksThe model and Renderer APort the canon from Drive into git with the reconciliation and additions applied in the port, so the paste job becomes a reviewable PR. Flows as files. The renderer generalised from the living page and this specimen. The checker in CI. Flow 9 and Flow 10 re-cut from the model.
• Phase 2Renderer BThe Apps Script exporter, committed, fed by the model. Rebuild the Slides master, regenerate the INDEX slide, retire Syne, Comfortaa and the unset theme font. Same file ID; every register link holds.
• Phase 3The deck that presents itselfFigures for the NDA families (M10, M20, M21, M40, M41, M44). Present mode with notes and beats on the gated living pages. Stamped per-recipient exports with automatic sent-log rows. Flow 2, never cut because M21 was never re-cut, built for the first time.

Decisions, all Erik's

1. Source of truth for canon. Drive doc (today) or git slide model (proposed). This one unlocks the rest.
2. The Slides master: source or output. Both of Erik's rules survive either way; only one of them can be enforced.
3. Wordmark on slide faces. RelayCTX (today) or Relay (copy gate). The renderer needs a value.
4. The drenched treatment (RCTX-96). This page and the living Introduction both assume bookends plus one earned interior moment. Ratify or change it before Phase 1 encodes it.
5. receive vs claim. Canon locks receive (June); the copy gate and the product say claim (July). This page keeps canon verbatim; the checker reports rather than fails. Not resolved here.