From Real Physics to Drift: How a Stellar Map Built My FTL

From Real Physics to Drift: How a Stellar Map Built My FTL

The reason FTL works the way it does in the Integration isn't mysticism.

It's that I went and looked up how thick a spiral arm actually is.

That sounds like a smaller decision than it turned out to be. Most of the time, in science fiction, FTL is a license — a permission slip the author signs at the start of the book so the plot can move at the speed it needs to move. The drive works because the story requires it to work. The mechanics get a paragraph in chapter two. Nobody asks the chair model number.

In the Integration Era, the FTL system is the chair model number. It exists because real galactic geometry made it exist. The shape of human and Vethari civilization, the position of the frontier, the reason two species missed each other for six centuries — all of it traces back to a number I looked up before I had a plot.

The argument I want to make in this dispatch is simple, and I think most working writers eventually arrive at it: constraints from reality are not the enemy of imagination. They are the most generative material it has.

Here are the numbers, because everything starts with the numbers.

The Orion Arm — the spiral arm Earth sits in — is roughly 3,500 light-years wide. It is not the main attraction. The galaxy's two dominant arms are Perseus and Sagittarius–Carina, and the Orion is a comparatively modest spur running between them. Width is the figure that matters here: 3,500 ly across, give or take.

The distance to the next major spiral arm varies. In the inner galaxy you can find 5,000 light-years of relatively low-density space between arms. In some outer reaches, the figure climbs toward 10,000. Astronomers call this the interarm gap, and it isn't empty — it's just thin. The stellar density drops off, the dust drops with it, and you get a long stretch of comparatively bare sky between the more crowded structures the eye picks out from outside.

That's a real fact. I didn't write it. A graduate student in 1953 drew the first useful map of it, and people have been refining the picture for seventy years.

When I sat down to write Dead Reckoning and started building out the broader Integration Era setting, that picture is what I had on a screen next to my outline. Humans in the Orion Arm, where humans actually are. Vethari in the Sagittarius Arm, the next major structure inward. Six hundred years of Vethari Integration history, a hundred years of human Integration history, two civilizations that had been measured by the same alien system for centuries — and never met.

The interarm gap explains that. It is the only thing that explains it cleanly.

Once the geography is fixed, the FTL system is no longer a free variable. It's an answer to a problem the map is already asking.

You can't have a drive that crosses 8,000 light-years of interarm gap in a weekend. If you do, your two civilizations don't believably miss each other for six hundred years — they meet on Tuesday. You also can't have a drive that crosses one light-year a year, because then nothing about the story functions; nobody goes anywhere on a human timescale. The drive has to operate inside the same window that produced the setting in the first place: fast enough to move a fleet across a sector in weeks, slow enough that the gap between arms is a real obstacle.

What fell out of that constraint, mostly without my permission, is a two-layer FTL system.

The first layer is the jump drive. Coordinate-locked, 20–50 light-years per hop, 30 to 60 minutes of recharge on a military hull, longer on civilian. Pre-Integration technology. Humans built this before activation, the way they built radio and aircraft — through long, unglamorous engineering. It works without the Integration. It works outside the Integration. It is the drive that exists in every chapter set among Purists, in every Houseguard transit, in every fleet operation where the captain doesn't want to know what the system is doing.

The second layer is drift. Integration-enabled, continuous, course-correctable mid-transit. This one is alien. Drift only functions inside the Integration's sphere of influence — wherever the system is "on," drift works. Wherever it isn't, drift fails. And because drift is continuous rather than discrete, you can change your destination after you've left. You can reroute around a Flux Storm. You can chase. You can run. You can do the things a story needs a starship to do when the scene is already in motion.

That second layer didn't come from a fact about the sky. It came from a fact about the Integration. The system shapes the conditions inside its sphere. So of course the version of FTL that exists inside the sphere would use the sphere — would treat the system's measurement and stabilization as a substrate the drive runs on. Drift exists because the Integration exists. Jump exists because the Integration didn't always.

You can already see what this does to the politics, but I'll say it out loud: the Purists are slower. Not because of ideology. Because of physics. They refused activation, which means they refused the substrate drift runs on, which means they're back on jump drives, which means it takes them longer to get anywhere worth going. Their convoys cross the same distance the Integrated fleet crosses in a third of the time. That isn't a thematic flourish. That's the geometry doing its job.

The interarm gap, once the FTL system is in place, becomes the most important piece of real estate in the setting.

It's the only space neither sphere fully covers. Drift fails there — by definition, because there's no Integration substrate to ride. Jump works, but jump is slow over that distance: you need ten to twelve hops to cross a thin section of the gap, and every hop is a coordinate-locked decision your enemy can predict if they know where you've been. The gap is also where the human and Vethari Integration spheres barely touch at their fringes, and where Flux Storms run hotter and more frequent than anywhere else in known space. Two thinning frontier edges, overlapping. Two systems struggling. Cat 3 and Cat 4 storms running in a corridor where neither civilization has a clean read of the other.

When somebody asks me where first contact had to happen, I don't have to think about the answer. The gap. It had to be the gap. The geography is so insistent that I didn't actually choose it — I just read the map back to myself.

This is the part about constraints that I think a lot of writers underestimate.

A blank page is not, in fact, a generous starting place for worldbuilding. A blank page lets you do anything, which means you have to decide everything, which means most of the decisions you make are slightly wrong because there's nothing pushing back on them. A constraint — a real number, a real distance, a real fact about how the universe is laid out — pushes back. It tells you no. It tells you no in ways that turn out, on the second or third reading, to be telling you something else.

The 3,500-light-year width of the Orion Arm told me no, you don't get to put the Vethari next door. The 5,000-light-year interarm gap told me no, your FTL can't be the kind that makes the gap irrelevant. The fact that drift needs the Integration to work told me no, your Purists don't get the same drives, and your gap doesn't get drift coverage, and your first contact doesn't happen in core space. Every no rearranged the geometry, and every rearrangement produced something I wouldn't have written from a blank page.

The Flux-Storm reroute in Dead Reckoning exists because of an interarm gap I read about in an astronomy paper. The Veldrath fleet's transit speed in Prior Integration — the specific gap between House Veldrath's reach and the Integrated military's reach — exists because of a recharge time I assigned a jump drive based on what a 50-light-year hop probably ought to cost a military reactor. The reason the Vethari took six centuries to find humans is because they couldn't go faster through the gap than physics let them. None of that is window dressing. All of it is the map.

Here's where this gets complicated, because it always does.

The trap with research-driven worldbuilding is that you can become a hostage to your own homework. You can decide that because the Orion Arm is 3,500 light-years wide, every scene needs to mention it; that because the recharge time is 47 minutes for a military hull, every transit needs to display the timer; that the integrity of the research is the reader's problem. It isn't. The reader's problem is the story. The research is the foundation under the story, and foundations are not supposed to be visible.

The two-tier FTL system shows up in maybe six explicit paragraphs across the whole series so far. The interarm gap is named, by name, in two scenes. The rest of the time, the research is doing what a foundation does — sitting under the floor, holding the weight, making the rest of the architecture possible without asking for credit. When a chase scene reroutes around a Flux Storm, the reader doesn't need to know why drift requires Integration coverage. They need to feel the rerouting cost something. The geometry pays that cost in the background.

This is the part you can't shortcut. You have to do the homework. Then you have to put most of it away.

Every chase scene, every "we can't reach them in time," every Flux-Storm reroute traces back to one question I asked a stellar map: how far apart could two civilizations be and still believably miss each other for six hundred years?

The map answered. The drive followed. The politics fell out of the drive. The frontier fell out of the politics. The series I'm writing is, in a real sense, a series built out from a 3,500-light-year figure and a 5,000-to-10,000-light-year gap.

I'd argue this isn't a trick. I'd argue this is how most working speculative settings actually get built — not from inspiration, but from the constraint that arrives first and the architecture that survives it. The "what if" is the cheap part. The how big, how far, how long is the part that decides whether the what-if can carry a story.

What real-world fact would you most want a sci-fi author to honor — and which one do you wish they'd quietly ignore?

Follow the posts to stay current. Subscribe to read the stories where the geometry becomes personal.