Knowledge · 00:03:18 · 460 words
file
the-compile-step.reading
speakers
vocateca (reading)
address
vocateca.com/en/knowledge/the-compile-step
duration
00:03:18 · 460 words
Knowledge · Method & workflow

The compile step

Field note
00:00:00vocateca

A raw transcript is a wall of text with timestamps. Nothing has read it yet. The compile step is where a model turns that wall into a linked encyclopedia page - one concept, its sources, and every related idea pointing back.

00:00:18

A transcript is not knowledge yet

00:00:18vocateca

Transcribing audio gets you text. It does not get you an answer to anything - the transcript is still organized the way the speaker talked, not the way a question is asked. Ask it something and you are back to reading the whole thing.

00:00:36vocateca

The method treats the transcript as raw material, not a deliverable. The deliverable is what a model writes after it reads the transcript: a page organized around a concept, not around the order someone happened to say it.

00:00:53

One concept, one page

00:00:53vocateca

The compile pass does not summarize a transcript into one blob. It pulls out the concepts the transcript actually contains and gives each one its own page. A podcast about three different topics becomes three pages, not one long recap.

00:01:10vocateca

This is the part that looks slow and pays off later. A single page per concept means the next transcript that touches the same concept edits that page instead of writing a new, disconnected summary next to it.

00:01:26

Related concepts, linked

00:01:26vocateca

Every page names the other concepts it touches and links to their pages. A page on 'context windows' links to the page on 'attention', which links to the page on the paper that introduced it - because that is how the source material actually talked about it.

00:01:46vocateca

A pile of unlinked summaries is a filing cabinet. Links turn the same material into a network you can walk - from one claim to the next related claim, across sources that were never in the same conversation.

00:02:03

The header is the provenance

00:02:03vocateca

Every page opens with a header listing the transcripts it was compiled from - which show, which episode, which source. Nothing on the page floats free of where it came from.

00:02:16vocateca

That header is what lets you trust the page later. Six months on, when the page has been edited a dozen times by a dozen new transcripts, you can still walk back to the exact recording a sentence traces to.

00:02:34

It compounds

00:02:34vocateca

The first transcript compiles into a handful of thin pages. The tenth transcript does not start over - it edits the pages that already exist and adds the ones that are missing, and the links get denser with every pass.

00:02:51vocateca

That is the actual argument for compiling instead of just archiving: a library of transcripts sitting on disk is worth exactly what you read out of it today. A compiled network is worth more after every transcript than it was before.

00:03:08

Sources

[This article cites no sources. When an article does, they appear here as numbered notes, like on the comparison pages.]

End of reading · 00:03:18

Read on

All articles

Download for macOSFree · macOS 15 or newer, Apple silicon
Version 2.2.5 · 28 August 2026