L = Loom-style long-form (screenshare + portrait bubble), 5–12 min

S = short-form vertical (screenshare top / you bottom), 45–90 s

Most L videos have 1–3 natural S cuts; they are listed under each.

1. Feature inventory (grouped by what the viewer cares about)

A. Identity & ownership

Cryptographic key instead of login ("you don't log in, you exist in the network")

Onboarding / key creation on desktop

Devices (account settings → devices)

Vault: sign in on web sites with your account key; session management

Verifiable, signed authorship on every change and comment

Self-hostable identity server (mentioned on site)

B. Writing (the editor)

Block editor: Paragraph, Heading, Code, Math, Image, Video, File, Web Embed, Table, Grid, Button, Card, Embed, Query, "New document" from slash menu

Drafts, discard changes, leave-draft guard, duplicate document

Import: Markdown (with visibility selection), web page import, PDF import (agent skill)

Document attributes/metadata (:attributes)

C. Links that never break (the core differentiator)

Fine-grained links: block, block + children, exact text range

Versioned links (?v=)

Embeds of whole doc / section / paragraph / word, optionally version-pinned

Cards

Bidirectional references → Citations view (:activity/citations)

Mentions (with notifications)

Community archival: referenced content is stored locally, redistributable, verifiable by CID + signature

D. Publishing & sites

Publish to a hyper.media subdomain or custom domain from the desktop app

Site settings: identity, navigation, members, writers, email subscribers, agents

Directories / folders, :directory, :all-documents

Web experience (Seed Web): SSR, mobile panel sheet, :feed, :explore

Self-host a site (Docker) / deploy from your own fork (your blog post)

E. Discussion & collaboration

Comments in context (block-level), discussions, comment deletion, comment version history

Capabilities & permissions (UCAN-inspired): grant writer access per space/path

Collaborators (:collaborators), path="*" site-wide collaborators

Open editing: branch someone else's document, "your version", owner can merge back

Version history, diff, restore version (your XState post), useIsLatest, draft rebase

Activity view

F. Structure & discovery

Query blocks (dynamic lists; fork has author + publish-date filters)

Explore / search (hybrid keyword + semantic, RRF), sort modes

Library (all / subscribed / bookmarks, grouped by site), Recents, Bookmarks

Feed

Profiles: :profile, :membership, :followers, :following

G. Community & reach

Subscriptions (joined spaces) and email subscribers ("Subscribe / Unsubscribe anytime")

Notifications: desktop inbox (all / unread), title-bar count, email notifications (mentions, discussions)

Community showcase (Develop Seed Hypermedia, Ethosfera, Nodos de Conocimiento)

H. Local-first & P2P

Content lives on your devices; works offline; syncs P2P (libp2p/IPFS)

Node = "your local brain"; replication across community nodes

Deleted content / recovery

Sync settings

I. Protocol, developers & AI

Hypermedia protocol (Change/Ref/Capability/Comment blobs, CBOR signed envelopes)

Hypermedia Explorer (explore.hyper.media) — raw data

HTTPS/JSON REST API, P2P API, signed data

Seed CLI

Agent Skill for LLM agents

Seed Agents (desktop): agent servers, sessions, triggers, memory, tools, prompt

API inspector, custom block types, custom frontends, planned TS library

Open source (GitHub), Discord

2. Proposed publishing order

Logic: why → 5-minute win → daily writing → the differentiator (links) → structure → collaboration → community → trust/ownership → developers/AI → real-world showcases. Each video should be watchable alone, but every one ends with a pointer to the next.

Arc 0 — Why Seed exists (publish first, keeps working as evergreen intro)

What is Seed Hypermedia? (in 4 minutes) — L The web has no native versioning, deep links, identity or permissions. Seed = open-source app; Hypermedia = open protocol. Show a live site, a signed version, a block-level link. End with "download the app".

S: "The web never got version history. We fixed that."

S: "You don't log in to Seed. You exist in the network."

Who is this for? — S x3 (research communities, open-source projects, learning communities / civic networks). One use case each, 60 s, reusing the knowledge-bases page copy.

Arc 1 — Zero to published (the golden path)

Install Seed and create your identity — L Download, onboarding, key creation, what a key means, backup. Mention devices.

S: "Your identity is a key, not an email"

Your first document → live website in 5 minutes — L New doc, title, a few blocks, publish to a hyper.media subdomain, open it on the phone.

S: "Doc to website in 60 seconds"

Give your site a custom domain — L (short) Site settings → identity/domain. Why this matters for ownership (Seed Web page: "retain control even if Seed servers disappear").

Arc 2 — Writing every day

The editor tour: blocks, slash menu, drag & drop — L Paragraph, headings, lists, code, math, table, grid, button, media (image/video/file), web embed.

S: "Math + code blocks" / "Grid layouts" / "Buttons in documents"

Drafts, discard, duplicate, and never losing work — L (short) Local drafts, leave-draft guard, discard changes, duplicate doc.

Bring your existing content in — L Markdown import (with visibility choice), web page import, PDF import via agent skill.

S: "Import a whole Markdown folder into Seed"

Arc 3 — Links that never break (the "aha" arc — the heart of the series)

Link to a paragraph, a sentence, a word — L Fine-grained links, copy-link submenu, open on web, the highlight.

S: "Link to a single sentence on any page"

Versioned links: reference something that can never change — L (short) ?v=, why it matters for debates and research.

Embeds and cards: reuse without copying — L Embed a whole doc / section / paragraph, pinned vs. latest version, cards.

S: "Embed instead of copy-paste"

Citations: every link is two-way — L Citations view, seeing who referenced your work, mentions.

S: "See who's citing you"

Why links on Seed don't rot — L (short, mostly talking) Community archival: your node stores what you reference; verify by CID + signature.

Arc 4 — Structure and discovery

Folders, directories and site navigation — L Directory view, folders, navigation settings, all-documents.

Query blocks: living lists that update themselves — L Blog index, "latest updates", filters (author, date), sort.

S: "A blog index that maintains itself"

Search, Explore, Library, Bookmarks, Recents — L Hybrid keyword + semantic search, Explore sorting, library modes, feed.

S: "Semantic search across every site you follow"

Arc 5 — Collaboration

Comments in context — L Block-level comments, discussions, replies, editing/deleting, comment history, mobile web comments.

S: "Comment on the exact sentence"

Inviting collaborators: writers, members, capabilities — L Site settings → members/writers, granting write on a path, collaborators view. Brief "how capabilities work" (UCAN-inspired).

Version history, diff, and restore — L History timeline, authorship per change, diff, restore (your "buttons are workflows" story is a nice cameo).

S: "Every change is signed by its author"

Open editing: make your version of anyone's document — L Branching a doc you can't edit, publishing your version, owner merging it back (Git analogy). Draft rebase when both changed.

S: "Fork a web page"

How the Seed team uses Seed — L seedteamtalks: lobby, issues, projects, meeting notes, updates, workflows, roadmap. Real dogfooding.

Arc 6 — Community & reach

Subscribe, follow, and the feed — L Joined spaces, subscribe button on web, feed, profiles/followers/following.

Notifications: desktop inbox and email — L (short) Mentions, discussions, read/unread, email notification setup, email subscribers for your readers.

Community showcase — L Ethosfera, Nodos de Conocimiento, seed.horacioh.com as personal blog. Interview-style optional.

Arc 7 — Trust, ownership, local-first (deeper "why", after people have used it)

Local-first: your knowledge works offline and syncs P2P — L Turn off wifi, keep writing, reconnect, watch sync. Joined spaces replication, sync settings, deleted content recovery.

Sign in on the web with your key: the Vault — L Vault session on a site, devices, why the server never sees your key.

Verify authorship yourself (no trust in Seed required) — L (short) Open a version in Hypermedia Explorer, show signature + CID.

Self-host your site / deploy from your own fork — L Docker deploy, custom domain, "make your Seed site truly yours" (your existing post).

Arc 8 — Developers & AI

The Hypermedia protocol in 10 minutes — L Change / Ref / Capability / Comment blobs, signed envelopes, IPFS/CRDT, why Git is the model.

Hypermedia Explorer + HTTPS API + CLI — L Browse raw data, hit the JSON API, run the Seed CLI against a site.

Seed Agents: AI that lives inside your knowledge base — L Agent servers, sessions, triggers, memory, tools, prompt; site-level agents; the Agent Skill for external LLM agents; API inspector.

S: "An agent that reads your whole site"

Build on Hypermedia: custom frontends and custom block types — L How-to-start-building page, planned TS library, GitHub, Discord.

3. Cadence & packaging suggestions

Publish Arc 0 + Arc 1 together (5 videos) so a newcomer can go from "what is this" to "I have a site" the day they discover the channel. Everything after can be 1 L + 2 S per week.

Arc 3 is the one that converts people; consider a playlist title like "Links that never break" and cross-promote it from every other video.

Shorts: cut them from the long recordings; each long video's "S" line above is the hook. Aim for 1 idea per short, end on the site URL.

Every long video: same 10 s cold open (one sentence of the problem + the demo result), then the demo, then "next video →".

Re-record 1 and 4 when the UI changes materially; keep the rest as-is (version-pin the docs you demo so the links in descriptions never break — a nice meta-point).

Keep a companion Seed document per video (transcript + links) on seed.hyper.media/blog and link to it; it doubles as a demo of publishing and citations.

4. Things to confirm before scripting

Whether the Community Showcase entries (Ethosfera, Nodos de Conocimiento) are OK to feature.