What Does "Interlined" Actually Mean?

Thu May 14

Foundational series, post 1 of 5.

The name doesn't come from software. It doesn't come from bookbinding or manuscript tradition.

It comes from public transit.

Specifically from the way transit agencies solve the problem of moving people through a shared corridor without making them transfer vehicles every few stops. Once you see the parallel, it's difficult to unsee.

How Transit Interlining Works

In New York, the A and C trains share the same physical track through Manhattan — Washington Heights down through Midtown, 42nd Street, 34th, West 4th, all the way through lower Manhattan. Same stations. Same corridor. Same infrastructure. Then they split. The A runs express to the Rockaways and Ozone Park. The C goes local to Euclid Avenue in Brooklyn. They're interlined through the shared trunk. After the branch, they're separate routes heading to completely different parts of the city.

The E train makes it more interesting. It runs its own line through Queens, then merges onto that shared Manhattan trunk at 50th Street in Midtown — riding it south through 42nd, 34th, 14th, West 4th, and Canal before peeling off to World Trade Center. It doesn't use the whole trunk. It enters at one point, exits at another. The shared section is still the interlined section. The E just hops on and off at different points than the A and C do.

Same pattern on Queens Boulevard — E, F, M, and R trains sharing a long trunk through Queens before diverging, some continuing into Manhattan via different routes, others terminating earlier.

That's interlining. A shared trunk that multiple routes use together. The routes diverge. The infrastructure in the middle is common property.

And there's one more detail worth knowing: a single vehicle can serve multiple routes through that shared section. A bus finishes one route and continues directly as a different route number — no depot run, no new vehicle. The vehicle itself carries the continuity between the two routes. The operational connection is the interline.

Why This Maps to Writing

Writing at any real volume isn't a series of independent pieces.

It's a transit system.

A raw idea you capture today is the first stop on a line. The draft you write next week draws on it — shares infrastructure with it. The finished post is the endpoint the route was always heading toward. And between the capture and the published piece, other things join the trunk: a research snippet, an older post you linked for context, a series of observations that all run through the same thematic corridor before each one branches off to its own conclusion.

An interlined entry is a unit of content that participates in that kind of shared infrastructure. It doesn't float in isolation. It shares structural track with the entries it came from, the entries it links to, the series it belongs to, and the tags that mark it as part of a common corridor.

When entries are interlined, moving between them is like riding a through-route. You're on connected infrastructure. Not making a separate transfer.

Most writing tools work the opposite way. A note in Obsidian and a post in Ghost are at completely different stations with no shared track. Getting from one to the other means leaving one system entirely and entering another. There's no interlined section. Everything is a transfer.

What the Branching Looks Like

In the transit model, what branches off the trunk can go to very different places — and that's fine, because the shared section is what mattered.

In InterlinedList, a single entry might branch in several directions:

A raw capture from January branches into a series post in March and a research note for a completely different series
A published post branches into a follow-up linked to it, a tag list grouping it with a dozen related entries, and a research snippet someone saved pointing back at it
A series post shares its trunk — the common topic, the series arc, the linked earlier entries — with every other post in the series, but branches to its own specific argument

The branching is what makes each entry its own thing. The shared trunk — the tags, the links, the series membership — is what makes the corpus navigable.

This is also why a single entry can serve multiple routes at once. A post that belongs to a series, carries three tags, and links to four other entries is interlined with all of those structures simultaneously. Same as a transit vehicle serving multiple routes through a shared segment: operationally connected to several lines, distinct in where it ultimately goes.

The One-Seat Ride

Transit planners talk about the one-seat ride — the ability to travel from origin to destination without switching vehicles. Interlining is what makes one-seat rides possible across what would otherwise be two separate services.

In InterlinedList, the one-seat ride is the ability to go from a raw captured idea all the way to a published, syndicated post without leaving the environment. The capture, the draft, the research, the linked context, the finished piece — all on the same line. You don't transfer to a writing tool, then transfer to a publishing platform, then transfer to a cross-posting tool.

The route runs through.

That's what "interlined" is trying to describe. Not linked in the hyperlink sense. Connected the way a transit system is connected: shared infrastructure, diverging routes, and the ability to travel through without getting off and changing trains.

The "List" Half

The name is two words run together: interlined and list.

Lists are the organizational layer that makes the transit model navigable at scale. Tag lists, series lists, research lists, topic lists. Together they answer the question "what do I have on this corridor, and where does it go" — across everything you've ever collected, drafted, or published, regardless of when.

Without the list layer, a corpus of linked entries is a network map you can traverse but can't survey. With it, you can see all traffic on a given tag, trace the full arc of a series from first stop to last, and keep source material attached to the drafts that draw on it.

The list is what keeps the model usable as your corpus grows past a dozen entries.

What a Session Looks Like

I open the Dashboard. 14 entries in Draft, 3 in Staged, 11 Live. The series I'm currently building — this one — has 2 posts live and 3 in progress. The shared trunk for this series is the Foundational tag and the series membership. Every post branches off that trunk to its own specific question, but they're all on the same line.

I open the draft. In the research panel I've got four entries: two links I bookmarked when thinking through this topic, one raw capture from three weeks ago when the idea first hit me, and one entry from a different series covering adjacent ground. All of them running on the same thematic trunk as this draft. Visible alongside the editor without cluttering what I'm writing.

I write a paragraph that connects to something I published eight months ago. I link to that entry. When this post goes live, that connection is permanent structure — anyone reading can ride the link to the earlier entry, and anyone at the earlier entry will see this one branches from it.

That's an ordinary writing session. The interlined model isn't a ceremony. It's just how the tool works.

The connections are the infrastructure. The entries are the routes. The whole thing runs through.

Next up in this series: why a writing tool has a social feed at all — and why I think separating writing and publishing is what creates the friction, not what solves it.

— Adron