The sections taking place on Cetia-243, the Empire’s capital, didn’t behave like normal chapters.

On paper, they were chapters, same as anything else, a block of story with a beginning and an end. But when I’d come back to them in revision, they felt… bigger than the container I was putting them in. They carried more pomp. More spiritual pressure. More ceremony in the air. Even when nothing “supernatural” was happening, the scenes still read like a kind of ritual. Like the empire itself was speaking through incense, architecture, and protocol.

And that made the word chapter feel wrong.

The word “chapter” is functional. Neutral. Modern. It’s a label that says, “Here is the next unit of narrative.” Cetia-243 wanted something that said “this is a movement,” or “this is a piece of liturgy,” or “this is what it sounds like when power stops being paperwork and becomes religion.”

That’s where Harmonic Bar came from.

In music, a bar is a measure, a frame for cadence. It’s structure, but it’s also emotion, repetition, motif, the slow build of meaning through pattern. A bar holds a phrase the way an altar holds a vow. Once I started using Harmonic Bar as the label, the work clicked into place. Suddenly, those sections had a name that matched what they were doing.

The best part is that it dovetailed perfectly with the Sovereign Chorus.

The Chorus isn’t just a cool piece of worldbuilding jargon for me, it’s the operating system of Cetia-243. Governance isn’t only political, it’s performed. Authority isn’t merely issued, it’s invoked. Faith and policy braid together until you can’t tell where one ends and the other begins. People don’t just rule, they are witnessed. They are echoed. They are sung into legitimacy.

So a “chapter” didn’t feel like enough. But a Harmonic Bar did. It implied that each section wasn’t only advancing the plot, it was carrying a note in a larger composition.

And yeah, I still flip between Chapter and Harmonic Bar, because the setting flips. Caldereth is all mud under the nails and consequences you can’t wash off. Cetia-243 is polished stone, bright banners, and cloak-and-dagger politics, where the performance is half the power. The name needed to shift with the gravity of the place.

Some parts of The Veiled Core Chronicles want to move like a knife, fast, intimate, bloody, human. Some parts want to move like a hymn, slow and elevated and heavy with meaning. Caldereth, for example, tends to read like boots on stone and breath in cold air. Cetia-243 reads like a procession. Like stained glass. Like a court that understands religion as technology.

Naming it Harmonic Bar was my way of admitting what the pages were already telling me.

This isn’t just a sequence of events. It’s a chorus. And Cetia-243 doesn’t speak in chapters. It speaks in measures.

— J.A. Raithe

Everything is fine. The scene is doing what it’s supposed to do. The characters are hitting the beats. I’m moving through it with that pleasant sense of momentum, like, yes, this is working.

Then an hour later I stop and think, wait.

How did we get here.

And “here” is usually a place I did not plan for. A door that was never supposed to open. A line that lands harder than it should. A choice that makes perfect sense for the character, and absolutely wrecks the outline I was so proud of yesterday.

Sometimes it’s dramatic. Sometimes it’s small. But the feeling is always the same. The scene ran away, and now my character is standing on a ledge I didn’t build a staircase for.

This is the part that sounds like a problem, and it is, but it’s also one of the best signs a story has a pulse.

Because a runaway scene usually means the character is behaving honestly. They’re making the choice they would actually make, not the choice that makes my life easiest. And once that happens, the story stops being a plan and starts being an event.

Still, you can’t just shrug and let the book drive itself into a ditch. So you hit the real question.

Do you rewind, or do you follow it.

I used to treat it like a fork in the road. Either you back up and force the scene to behave, or you commit to the new direction and accept the chaos.

Now I think it’s a little more like triage.

First I ask, did the scene run away because it got more true, or because I got sloppy.

Those are not the same thing.

Sometimes a scene “runs away” because I’m tired and I let a character do something convenient, or melodramatic, or cool-looking, and it feels exciting in the moment, but it doesn’t fit the world or the person. That’s not a runaway scene, that’s sugar. It hits fast and then it makes everything feel worse.

But when it runs away because the character is being themselves, that’s different. That’s the story discovering its own logic.

Then I ask a second question.

Is this new position a dead end, or is it just unfamiliar terrain.

Because a character “trapped” in a situation I didn’t anticipate isn’t always a problem. Sometimes it’s the exact pressure the story needed. Sometimes it’s the moment the book gets teeth.

The catch is that I’m writing with an outline in my head, even if it’s loose. I had other plans. Certain scenes were supposed to happen in a certain order. Certain reveals were supposed to arrive with clean timing.

Runaway scenes don’t care about my plans. They care about cause and effect.

So the real decision becomes this.

Do I protect the outline, or do I protect the truth of the character.

When I choose the outline, I rewind. I go back to the last decision that caused the scene to sprint off course. I don’t delete it because it was “wrong,” I delete it because it made the story less honest. I put the character back at the last point where they still had options, and I rewrite until the scene feels inevitable again.

When I choose the character, I follow the scene to its conclusion. I let it play out, even if it breaks things. Especially if it breaks things. Then I take a deep breath, look at the rubble, and rebuild the plan around what now has to be true.

That last part is the cost people don’t mention. Following the runaway scene means paying for it later. It means rewriting the next chapters. It means moving reveals. It means accepting that the story you thought you were writing is not the story you’re writing anymore.

But it also means you’ve found something alive.

If I’ve learned anything, it’s that forcing a story back onto the old rails rarely makes it better. It makes it cleaner, maybe. More predictable. More obedient. But not better.

The best compromise I’ve found is this.

I don’t decide immediately.

If a scene runs away, I let it run, at least to the end of the chapter. I want to see what it’s trying to become before I kill it. Sometimes the ending proves it was a mistake. Sometimes the ending proves it was the story telling the truth.

Then I step back and ask, what did this scene just make possible that wasn’t possible before, and what did it just make impossible that I was counting on.

If the trade is worth it, I keep it and I adapt. If the trade is poison, I rewind without guilt.

Because outlines are plans. Characters are people, at least while they’re on the page.

And sometimes the most important job isn’t to control the scene.

It’s to recognize when the story just revealed what it actually wants to be.

—J.A. Raithe

Marro and Eralius have always been that for me.

In the Veiled Core Chronicles, they’re tied to some of the biggest shifts in the empire, faith fracturing, power consolidating, the whole world tilting under the weight of Arath-Bar. But when I think about them, I don’t start with thrones or doctrine.

I start with honey cakes.

A fifteen-year-old boy and a thirteen-year-old girl in the sunshine, laughing like the world is simple. It’s the sweetest moment in the entire universe, and that’s exactly why it hurts. Because once you know what’s coming, you can’t read that scene without feeling the shadow behind it.

Before the Scale is a prequel piece built around three moments.

First, the sweetness, the kids, the easy trust, the kind of closeness that feels permanent when you’re young.

Then the turn, Marro on the dais, announcing what she’s become, and the room realizing the rules have changed. Including Eralius.

And finally, the Board, where Marro stops being a person the room can dismiss, and becomes a presence the room has to rearrange itself around.

This backstory is, to me, the sweetest and most bitter part of the whole Veiled Core universe. Not because it’s dramatic, it is, but because it’s personal. Because the love doesn’t vanish, it just stops belonging to them.

If you’ve read The Nine Who Remembered, this sits right beside it as another “artifact” from inside the world, a glimpse of what faith and power look like up close.

And if you’re new to the Veiled Core Chronicles, this is a clean entry point; it won’t explain everything, but it will show you the heart of it.

Read Before the Scale here.

The book was done. Edited, formatted, ready for the world. I was satisfied. I was moving on.

Except Anna wasn't done with me.

She kept showing up. Not on the page, not in notes or outlines, but in the quiet hours when I wasn't trying to write. I'd be driving, or making coffee, or lying in that half-sleep where your brain decides to solve problems you didn't ask it to solve, and she'd be there. Not the Anna from the station. The other one. The one from before. The soldier who hadn't crossed the line yet but was standing close enough to feel the heat coming off it.

I kept thinking about Kandahar. In Station 13, it's a shadow. A scar that shapes everything Anna does, every decision she makes, every sound she hears in the corridors of that station. You feel it on every page. But I never showed it. I let readers see the wound through the way it bled into her present, and for the novel, that was the right call.

But I realized I wasn't thinking about what the novel needed anymore. I was thinking about what Anna deserved.

She deserved to have her worst night told properly. Not summarized in a psych evaluation. Not reduced to a line in a personnel file. She deserved the full weight of it, the heat and the dust and the moment when everything she believed about herself got tested in ways no training manual covers.

That's what "The Line" is. It's the night everything changed. The classified mission, the impossible choices, and the specific horror of standing in the dark and not knowing whether the threat is outside the wire or standing next to you.

Writing it was different from writing Station 13. The novel lives inside Anna's head. "The Line" lives in her body. Sand in her teeth. The weight of a rifle that suddenly feels wrong in her hands. Sounds that don't match what her eyes are telling her. It's more visceral, more immediate, because the Anna in Kandahar hasn't built the walls yet. She doesn't have coping mechanisms, rituals, or ways to organize the chaos. She just has the chaos. Raw and real and the kind of thing your mind spends years trying to make sense of afterward.

I also needed to tell the story of how the system failed her. The evaluations that followed. The counseling that checked boxes. The moment someone signed a piece of paper that said she was fine, and what "fine" looked like from the inside, versus what it looked like on a form. Because the most terrifying thing about Anna's story isn't what happened in Kandahar or what happened on the station. It's the space between the two, where everyone agreed she was ready, and nobody asked the right questions.

If you've read Station Thirteen, "The Line" is going to change the way you experience that book. You'll hear things differently. You'll understand the weight behind moments that seemed small the first time through. I'll leave it at that, because discovering those connections is part of the experience.

If you haven't read Station 13 yet, "The Line" stands completely on its own. It's a story about a soldier, a night in the desert, and the distance between who we are and who we become when the worst happens. And if it gets under your skin the way it got under mine, there's a space station waiting for you afterward.

I didn't plan to write this story. I thought I was done. But some characters grab you by the collar and drag you back to the desk, and Anna Dimitrovic is nothing if not someone who holds the line.

This was her private story. Now it's shared with you.

The Line is available now at www.JosephRaithe.com/the-line-a-station-13-prequel

Indie publishing is not that version.

Indie publishing is choosing to be an author, and then accidentally hiring yourself for six other jobs.

And the funny part is, you don’t sign up for them in one big decision. They arrive one at a time, each one feeling reasonable on its own. Then one day you look at your calendar and realize you’re running a small company in the cracks between a full-time day job and a family life that already deserves your best energy.

You become a designer, or at least a project manager for design. Covers. Typography. Trim sizes. Audible-friendly square crops. The subtle differences between “looks cool” and “reads instantly at thumbnail size.” You learn more about fonts than you ever expected to learn in this lifetime.

You become a marketing executive, which is a glamorous phrase for trying to answer a question that never really goes away. How do people who would love this book actually find it. That turns into ad experiments, audience guesses, copy tweaks, landing pages, link tracking, and a steady diet of “is this working or am I just feeding the algorithm.”

You become an interviewer, especially if you do audiobooks. You listen for tone, timing, emotional range, and whether a narrator can carry tension without turning every line into a performance. You learn how to talk about a book in the language of voice, pacing, breath, and restraint. You learn that “good voice” and “right voice” are not the same thing.

You become a content creator, which is another phrase that sounds clean until you’re living it. Website updates. Blog posts. Newsletter drafts. Social posts that don’t feel like you’re yelling into the void. Graphics. Pull quotes. Audio snippets. Third-party sites that all want slightly different things and none of them care that you’re doing this after work.

You become tech support. Something always breaks. A link dies. A widget stops rendering. A retailer changes a page layout. An embed script updates. The kind of little problems that can eat an entire evening while your brain keeps whispering, you could be writing right now.

And somehow, through all of this, you still have to be the author.

You still have to protect the part of your life where you sit down and make something out of nothing, because that’s the only part that can’t be outsourced by sheer stubbornness and late nights. The cover can be improved later. The ad copy can be rewritten. The website can be patched. The story, the actual next book, only exists if you give it hours.

That’s the tension indie authors live inside. The work that gets you readers competes with the work that makes the next thing worth reading.

When you’re doing this with a family and a full-time job, it gets even sharper. Your time isn’t “free time.” It’s time you’re borrowing. From sleep. From weekends. From the quiet parts of the day that should probably belong to the people you love, or to your own sanity.

So you learn to get practical.

You learn which tasks actually move the needle, and which ones just feel productive. You learn to build systems so you don’t have to reinvent everything every launch. You learn that some days the best win is writing 300 words and not letting the business side swallow the whole evening.

You also learn something else, and this is the part I didn’t expect.

You learn pride in the messy, unglamorous parts.

Because indie publishing is a lot of extra work, yes. But it’s also ownership. It’s agency. It’s choosing the cover that fits the book, not the cover that fits a committee’s guess. It’s finding the narrator who understands the tone. It’s building a direct path between you and the reader. It’s being close enough to the whole machine that you can change it when it isn’t serving the story.

Some nights it’s exhausting. Some nights it’s thrilling. Most nights it’s both.

And if you’re in the middle of it, juggling the day job, the family, the life, and the quiet insistence that you still want to write, I’ll say the thing that helped me most.

You’re not failing because it feels like a lot.

It is a lot.

You’re doing the author job and the publishing job at the same time. The only way it works is by deciding, again and again, that the story still gets a seat at the table.

And I wouldn’t change a thing. These stories are in my bones now. The thought of not completing the journey doesn’t exist.

—J.A. Raithe

Every book I’ve written started the same way, with a question that burrowed into my brain and refused to leave until I followed it somewhere.

Station 13 began with security cameras. I was thinking about how much we trust technology to show us the truth. We mount cameras in our homes, our businesses, our streets, and we treat what they capture like objective reality. But what if the camera was wrong? What if what you saw on the screen and what was actually happening diverged, and you had to choose which reality to trust?

The first version was smaller, domestic, claustrophobic, a woman alone in her home, watching feeds that didn’t match what she heard through the walls. But the question kept growing. I moved it into space, onto a remote station, and gave it to Commander Anna Dimitrovic. I surrounded her with a crew she loved like family. Then I made her choose between what she saw and what she believed, knowing the wrong choice would cost lives.

Writing Anna broke something open in me. I had to live inside a mind that was either seeing clearly while everyone else was blind, or shattering while believing itself whole. I wrote the ending and I still don’t know which one she was. That uncertainty stayed with me.

The Shepherd Descends came from ’Oumuamua. When that object passed through our solar system in 2017, one of the theories that surfaced was the uncomfortable one: what if it wasn’t natural? Most people brushed it aside. I couldn’t stop turning it over in my head.

Not the science of it. The humanity of it. How we would react. Would we reach for cooperation or competition? Would our factions and nations find common ground, or would first contact become another arena for the same territorial games we’ve always played?

I wrote The Shepherd Descends as an observer, watching us the way a scientist watches an experiment: clinical, patient, evaluating whether we could be trusted with neighbors. Seeing her catalog our fear responses and cooperation percentages forced me to look at our species from the outside. The view wasn’t always flattering. But there was hope in it too, in the scientists sharing data despite restrictions, in the kids drawing pictures while governments postured. We’re capable of being better than our worst impulses. Whether we choose to be is the question the book asks.

The Veiled Core Chronicles is different. The others gestated for months. This one has been living in my head for twenty years.

It started with a single image: pieces on a game board, except the pieces were alive. They could think. They could feel. They could suffer and love and die. And the players moving them didn’t care, because to them, losing a piece was just a setback in a larger game. That haunted me, the indifference of the hand that moves you while your entire world burns.

For two decades, I kept building. The game became The Board. The players became the Archons. The pieces became soldiers fighting wars they didn’t understand for reasons they’d never be told. And at the center of it all was a single scene: a woman in white armor crashing through a church wall to save nine soldiers who were about to die. She didn’t know she’d just been summoned into existence. She didn’t know her memories were fabrications. She didn’t know she was a piece, placed on the board by a player who saw her as a raised stake in an ongoing wager.

Writing that scene, finally, after twenty years of carrying it, felt like exhaling a breath I didn’t know I’d been holding.

I understand now that all three books ask the same question from different angles: what if the thing we assume is true isn’t? What if reality isn’t what we perceive? What if we aren’t alone? What if our existence itself was manufactured for someone else’s purpose?

I write across genres because the questions don’t care about genre. They just want to be explored.

If you’ve read any of my books, you’ve trusted me with your time and your imagination. I don’t take that lightly. These stories cost me something to write. I hope that investment shows on the page.

And if you’re wondering which book to start with, pick the question that won’t let you go.

—J.A. Raithe

What if we don't have to explain everything?

I've been chewing on that question for years. Science-fantasy is the name we give to fiction that lives in that space. It wears the gear of science fiction: starships, alien worlds, advanced technology. But it refuses to evacuate mystery. It leaves room for the numinous and the transcendent, for things that won't sit still long enough to be reduced to equations and engineering diagrams. And far from being a compromise or a failure of rigor, that blend has produced some of the most enduring works in speculative fiction.

Take Frank Herbert's Dune. Yes, there are spacecraft and shields and stillsuits, and Herbert clearly understood the mechanics of his setting. But the story's real current runs through prescience, ancestral memory, and a messiah whose power cannot be separated from the religious framework that surrounds him. Herbert wasn't confused about what kind of book he was writing. He knew that some truths arrive wearing myth.

Gene Wolfe took the idea even further with The Book of the New Sun. It's set in a far future where technology has become indistinguishable from magic, not because it's advanced, but because understanding has been broken and scattered. Wolfe builds a world where the reader can never be fully certain what's miraculous and what's mechanical. That uncertainty isn't a flaw to be corrected; it's the point. Wolfe was a deeply Catholic writer, and his fiction reflects a universe where mystery is not a temporary problem; it's part of the architecture. I still think about that book at odd moments. It left splinters.

Then there's Warhammer 40,000, which pushes the fusion to operatic extremes. Gothic cathedrals drift through space. A corpse-god powers an empire through psychic sacrifice. Demons pour through holes in reality. If plausibility is your only yardstick, it's the wrong tool for the job. What 40K delivers, when it's at its best, is scale you can feel in your ribs, awe welded to horror, the sense that the universe is vast and terrible and stranger than the human mind can fully metabolize.

Even Star Wars belongs to this lineage, popcorn reputation and all. The Force isn't a gadget. It isn't a system diagram. It's a spiritual dimension that hyperdrives and blasters exist alongside rather than replace. And every attempt to explain it too neatly, to pin it down with pseudo-biology or procedural lore, tends to shrink it. The Force works because it remains larger than the characters, and larger than us.

What connects these works isn't laziness or a failure to think things through. Yes, "handwave" writing exists, and it's often thin. But science-fantasy isn't handwaving; it's a deliberate aesthetic. It's the recognition that certain kinds of stories—stories about transcendence, about the limits of human understanding, about encounters with the truly alien—require space for the irreducible. Hard science fiction can do many things beautifully, but it often struggles to evoke the sacred without turning it into a mechanism. Science-fantasy doesn't have that limitation.

This is the tradition I write in. Or try to, anyway.

When I started The Veiled Core Chronicles, I knew I wanted to explore what happens when humanity encounters intelligences so old and so vast that fully understanding them might be impossible. Not because they're poorly conceived, but because some things genuinely exceed our cognitive bandwidth. The ancient AIs in those books aren't puzzles with a tidy solution. They're presences to be confronted, and surviving that confrontation changes you in ways you can't entirely predict or control.

The Shepherd Descends asks similar questions from a different angle. What does transcendence actually cost? When you become something more than human, what do you leave behind, and what follows you? These aren't questions with clean answers, and I didn't want to write books that pretended otherwise. The science-fantasy mode gave me permission to let the mystery breathe, to let the most important things stay partially out of frame, the way they do in real life.

Even The Sporefall Saga, which starts in more familiar apocalyptic territory, operates on the same principle. The alien spores that arrive on Earth aren't just a biological threat. They heal before they erase. They offer something that looks like salvation before revealing its true cost. The horror isn't simply physical; it's existential. Spiritual, even. It's about what consciousness is, and whether it can survive transformation without becoming something unrecognizable.

I didn't arrive at this approach by accident. I came to it because the books that shaped me as a reader lived in this borderland. I wanted the wonder I felt reading Dune for the first time, the unease Wolfe leaves in your mind, the sense of cosmic scale that the best space opera achieves when it stops trying to make the universe comforting. And I found, over and over, that I couldn't get there while staying safely inside fiction that insists on explaining everything.

Science-fantasy isn't a lesser form. It's a recognition that the universe is stranger than our models, that some truths live between knowing and not-knowing, and that great fiction doesn't always owe us answers.

If that's the kind of story you're hungry for, I'd be honored to have you explore my work. If you want mythic scope, ancient intelligences, and mysteries that don't collapse into tidy explanations, start with The Veiled Core Chronicles. If you want first contact filtered through questions of transcendence and cost, The Shepherd Descends is a good doorway. And if you want something intimate and apocalyptic, where salvation and annihilation wear the same face, The Sporefall Saga is waiting.

Not to be explained, but to be felt.

—J.A. Raithe

Station 13 was never going to let you have that comfort.

From the very beginning I knew I did not want a creature that bursts through the bulkhead. I wanted a different kind of horror, the kind that lives in the gap between what you see and what you know, and in the distance between what you remember and what the records say. You cannot shoot that. You can only doubt it, and the longer you doubt, the more it eats you.

This is how I tried to build that feeling.

Start with someone who knows what “normal” looks like

If you are going to break reality for the reader, you have to start by convincing them that someone on the page understands reality very well.

Commander Anna Dimitrovic is not a random person who wandered onto the station. She knows the routines. She knows the systems. She knows what her crew looks like on good days and bad days. When she says, “This is wrong,” it matters, because she is not a habitual alarmist. She is the adult in the room.

That is the first step in designing fear you cannot shoot. You give the reader a stable frame of reference, a person whose judgment feels solid. Then you start putting hairline cracks in that frame and ask the reader to decide whether it is the world that is breaking or the person.

Make the systems lie before the people do

In a lot of science fiction horror, people start acting strange first. Station 13 flips that order. The station lies before the crew does.

Security feeds show movement in an empty corridor. Sensor logs disagree with each other. Audio cuts out at the moments when someone most needs to be heard. None of it is dramatic on its own. A glitchy camera. A miscalibrated sensor. Anyone who has worked with real hardware has seen that.

The trick is in repetition. One glitch is noise. Ten glitches that all happen to land at the worst possible moments start to feel like intention.

You can feel that in Anna’s frustration. She wants something she can point to, a clear fault, a broken cable she can fix. Instead she gets this steady drizzle of almost nothing. Every time she goes to prove a theory, the data is just a little off from what she expects. That slow erosion is the horror.

Never give the reader a clean camera angle

There is a temptation, when you write a scene on a space station, to treat the cameras like magic. You can cut to any angle, show everything, answer every question.

For Station 13 I set a rule for myself. No camera would ever give a comfortable view of exactly what you want to see.

Maybe the feed is shifted slightly out of frame. Maybe it is fogged, or too low resolution to resolve a face. Maybe the right camera is offline, so you are forced to watch through a secondary angle that loses half the scene. Cameras become another unreliable witness, one more voice in the argument instead of the final authority.

That is important, because if I ever gave you a single piece of footage that answered everything, the fear would collapse. The unknown would become a known, and even if that known was terrible, you would be able to aim at it. Instead, every piece of evidence creates two new questions. Something moved. What moved. Someone screamed. Who screamed. Why is it off the edge of the frame.

Let trust decay in small, plausible steps

You can put a knife in someone’s hand and say, “This person is dangerous.” That is simple. What is harder, and more interesting to me, is to make the reader think, “This person might be dangerous, but I am not allowed to be sure.”

So the crew on Station 13 do not suddenly turn into monsters. They misspeak. They forget details. They tell stories that do not quite match the records. They insist they were in one place when the cameras show them somewhere else, or the cameras show nothing at all.

Each incident is survivable on its own. People are tired. Space is stressful. Everyone misremembers something sooner or later. The question that eats at Anna, and at the reader, is not “Did someone lie once.” It is “How many small inconsistencies do you ignore before you admit that you cannot trust anyone else on the station.”

Fear you cannot shoot comes from that slow, sick feeling that the people around you are becoming unreadable. You cannot put a bullet in “I no longer know what you are.”

Anchor the reader in procedure, then weaponize it

One of the fun parts of writing Station 13 was leaning into the procedural side of running a tiny outpost. Checks, logs, maintenance routines, power budgets, resource allotments. If you show enough of that up front, the station starts to feel real. It has rules. It has habits. It feels lived in.

Once all of that is established, you can twist it.

A routine safety check reveals something that should not be there. A scheduled communication window passes in silence. A standard diagnostic returns a result that is almost normal, but not quite. Procedure becomes a measuring tape for wrongness.

Anna is a commander, so her instinct is always to fall back on process. When she starts to see that the process itself is compromised, that the tools she uses to make decisions are no longer trustworthy, that is where her fear spikes. She is not just afraid of what is happening, she is afraid that she can no longer tell whether she is making the right call for her crew.

Again, there is nothing to shoot. The enemy is a pattern of failures.

Put the monster where no weapon can reach

In most fightable horror, the monster is out there. It is in the vents. It is in the sea. It is in the house across the street. You might lose, but at least you can charge at it.

Station 13 keeps asking a different question. What if the real battlefield is in your own mind.

If Anna is wrong, if she is imagining patterns where none exist, then every action she takes in defense of her crew might be the thing that destroys them. If she is right, and something is manipulating reality on the station, then her own thoughts and perceptions are already compromised.

That is a cruel place to put a character, and it is exactly why this story exists. You cannot shoot a monster if the monster is the way you think. You can only grit your teeth and keep trying to reason your way through, knowing that every new piece of evidence might be a trap.

The fear I wanted here is not “something is going to jump out at me,” it is “I might already be lost, and I will not know until it is too late.”

Why write horror like this at all

It would have been much easier to put teeth and claws on the problem. A physical intruder, a parasite, a clear infection. Those stories are valuable and fun and I enjoy them.

Station 13 exists because I keep circling the idea of tests and signals and unseen designers across all my books. The Shepherd Descends looks at what happens when an almost godlike intelligence shows up with a grading rubric for humanity. The Entropy Seed asks whether we were built to fail from the start. The Veiled Core Chronicles shows a society shaped around a dangerous memory that no one fully understands.

In all of those stories, the characters are trying to act inside systems they cannot see. Station 13 shrinks that idea down and turns it into a pressure cooker. One commander, four crew, a metal shell around them, something wrong in the data, and no monster she can point a weapon at.

Fear you cannot shoot is the kind that stays with me after I close the book. It is the kind that feels a lot like real life, where you cannot solve every problem by aiming at the right target. You are stuck making decisions with partial information, hoping your mind is giving you a fair picture of the world.

That is the terror on Station 13. Not just that something might be out there in the dark corridors, but that the person you rely on most, yourself, might not be telling you the truth.

If this kind of horror speaks to you, the kind where the monster might be hiding in the data and in your own doubts, then Station 13 is very much that story. And if you are a writer who enjoys pulling the floor out from under your characters, I hope some of these choices give you a few ideas the next time you want to build a fear no one can shoot.

—J.A. Raithe