Move the cursor · the corpus becomes a codex
ventures

Creator Codex

A creator's own videos, made into a course they can sell.

In progress
What it is

Their videos, in teaching order. Their words between them. Theirs to sell.

Creator Codex turns a small creator's catalog of short videos into a finished course they can sell, then helps them open it and grow it if they want that.

The machine underneath is a harvester: it transcribes a whole catalog on one Mac and finds the argument running under the tips. From that comes the course: the videos in teaching order under plain names, the words that open, bridge and close each module in the creator's voice, a month of practice per module, and the page that sells it.

Every quote is checked against the video it came from, and all of it belongs to the creator.

It opens as a course that runs without them, or as a Skool community they lead.

Three steps, each optional: the build, a clean handoff; setting it up on their platform; and growing it together once it has paying members.

The road ahead

The machine is built. The first course is ready. The first sale is next.

Open threads

Which creators want a course that runs without them and which want a community they lead, and how much of the monthly work one person can carry.

From the repository

A catalog goes in. A Codex comes out.

  1. 00 · LIST

    Find the videos

    A lister walks a creator’s account and writes down its video posts, so a later run only picks up what is new.

  2. 01 · FETCH

    Pull the audio

    Each video’s audio is fetched once and recorded, so nothing is downloaded twice.

  3. 02 · TRANSCRIBE

    Transcribe it locally

    whisper.cpp runs on the same Mac, with the creator’s own vocabulary — names, products, coined terms — held in front of every window so proper nouns come out right.

  4. 03 · WRITE

    One transcript per video

    Timestamped markdown, numbered by upload date, each headed with its title, link, likes, date and duration.

  5. 04 · DISTILL

    The corpus and the frameworks

    Transcripts become chunks on the creator’s own pause structure, a frameworks registry whose names stay stable across runs, a lexicon of the phrases that recur across videos, and the statistics the Codex draws on.

  6. 05 · JUDGE

    Only what a reading can settle

    Two calls per video: which framework it carries, and whether it turns a myth on the viewer’s own life or decodes a text for its own sake. Everything mechanical is finished first, so the reading works from one short worksheet instead of forty transcripts — which is what makes a wide pass affordable.

  7. 06 · CODEX

    The document builds itself

    Nine folios — the thesis, the method, the resonance map, the frameworks, the voice, the sources, what to make next, the course already recorded, and the whole searchable corpus. Seven are derived outright from the transcripts. Two are a reading, and where the reading has not been done the page says so rather than inventing it.

$0
cost of a run
1
Mac, nothing hosted
6.3×
realtime, transcribing
9
folios, generated
0
Python packages

It is idempotent on purpose: a video already fetched is skipped without touching the network, audio that has a transcript is never transcribed again, and the markdown is regenerated every run.

One registry drives the whole thing, so a roster of creators is a batch rather than a queue of hand-builds. And the arithmetic behind any claim the Codex makes is re-derived from the corpus every run — a finding that only holds for two flattering videos is caught here, before it ever reaches the person it is about.

The worked example

The Expanded Codex, made from my own saved videos.

18 ideas I kept, each taken further: the principle underneath, where it comes from, what it pulls against, and a thirty-day experiment. Pointed at a creator’s catalog, this is their course, half written.

Read the Expanded Codex ↗

Lineage — Autonomous company, the idea Creator Codex is the first product of.
Shipped
  1. A claim-checking step now re-derives the arithmetic behind any finding before it ships, and caught an overstated one in the first draft.
  2. The Codex document now generates itself from a creator's catalog — eight folios, with every figure recomputed from the transcripts on each run, so nothing on the page can drift from the evidence under it.
  3. The page now shows what the harvester actually does, stage by stage
Everything done, across all the projects →