The Thread Book One

by A.L. Wolf

The Thread is waking. And it remembers their blood.

Cal Voss has always felt wrong—seeing what others can’t, hearing whispers no one else hears. But now the visions are worsening, pulling him deeper into the hunt. He feels the stalk, the blade’s bite, the final shudder of breath—and a sick pleasure that isn’t his. Each time he returns, it’s harder to tell if he’s escaping the killer…or becoming him.

After the latest vision, Cal meets Eva—a stranger drawn to the scene by the same pull, bound to him by both blood and curse. They are hybrids—born of Wardsworn light and Bloodbound darkness, heirs to a power sealed deep in the Thread—an ancient bond Silas Voss, a Bloodbound commander, intends to weaponize for his own dominion.

But Silas isn’t the only one hunting them. Detective Reyes is already closing in, following a pattern no one else sees and closing in on the killer—and the two people she can’t decide are suspects, victims, or something far worse.

To stop the murders, Cal, Eva, and Reyes must follow a trail of bodies and face the the deeper they step into the Thread, the more it rewrites who they are.

And if the Thread completes, Cal and Eva won’t just belong to it—they’ll belong to the killer who claimed it.

A supernatural crime thriller where murder, magic, and family legacy collide—perfect for readers who crave dark fantasy woven through modern suspense.

396 pages, Kindle Edition

Published August 14, 2025

Reviews

[Marc *Dark Reader with a Thousand Young! Iä!* · Rating 1 out of 5]

Fact: this book is not AI-generated. I know this because the author said so.

Story time . . .

See, one day I added this book to a Listopia list, "AI-generated books released in August 2025". I made this and other lists to track a tiny portion of the AI books put out endlessly on Amazon and other online book markets, to help readers avoid such things (because who wants to read an AI-generated book, right?) and to keep track of trends in the creation of such things, like cover art that shifted from Midjourney to ChatGPT's latest image generator as the AI of choice for such things within days of the latter's release. When I would see new books promoted somewhere that showed strong signs of AI-generation, including cover art and text, I would add it to such a list.

The objection in this case started with some rando new account "Ben Cohen" complaining that the list was defamatory. Ben claimed it wasn't about any one book. Very quickly after that, a thread by the author of this book was posted to the Librarians group asking to remove her book from this list. Ben chimed in there also, then his account disappeared completely. What are you gonna do? Anyway, the author's complaint was, "This inclusion is unfounded, misleading, and is spreading misinformation which damages the reputation of authors, and undermines the trust of the community. The inclusion is based purely on opinion, not fact, and it risks unfairly discouraging readers from engaging with these works." (https://www.goodreads.com/topic/show/...). Further, "My book does not belong on that list. I base my request on fact, unlike the user who is defaming those on his list." Strangely it was similar language to Ben's complaints, but I'm sure there's no connection between them. In any case, the book was removed from that list. That's fine. I looked at the book's cover again and thought I could have made a mistake. It happens. It looked like it had that grainy fabric texture of ChatGPT but the image design was unusual for ChatGPT book covers at the time. I did not look inside the book again at that time. I don't care to make anyone angry, and what do I care if the book is on that list or not, really?

The astute GR user may note that this book is again on that particular list, but that wasn't me. That was other voters.

Anyway, comparing the book cover now to some others from books that show a ton of commonalities with AI slop, it looks quite definitely like a ChatGPT-generated cover:



That's fine, that's just the cover, right? That doesn't necessarily meant the book itself is AI-generated, right? What's important is that the author agrees that AI books are BAD. It would be BAD to label a book as AI-generated, because this would discourage readers, because AI books are BAD. So if a book is AI-generated, it should NOT be read. This is the crux of the argument, right? Because if it was fine for a book to be AI-generated, then there would be no problem identifying it as such, yeah?

So it's a good thing this book's content isn't AI-generated.

Although . . .

It's odd, then, that this book uses negative parallelism so extensively. It's a weird thing that AI "writing" does a lot, saying, "Not this. That!" or "Not just this. This other thing". This is well documented in reliable sources, e.g. https://en.wikipedia.org/wiki/Wikiped..., and I noticed it for myself long ago in a number of AI slop books like The Weaver’s Awakening, The Orphan's Destiny, and many (many!) others. Like, this book includes all of the following passages in just the free preview section, spending an awful lot of time telling the reader what things are not:

When whole, the Thread becomes not only a bond—but a leash.
[. . .]
He wiped the blade against his shirt—no rush, no reverence—then crouched beside the dying man. Not to witness. To ensure.
[. . .]
The body sagged. The hush that followed didn’t mourn him. It erased him. The spiral glowed faintly on cooling skin—not a signature of death, but a mark of dominion.
[. . .]
The hunger in his blood quieted—not sated, merely waiting.
[. . .]
But this death was not the end. It was a signal.
[. . .]
Already it was coiling tighter around the one shaped not by love, but by control—
[. . .]
The spiral pulsed on his palm—not just a symbol, but a signature.
[. . .]
The air shifted—no breeze, just presence. Cold. Invasive.
[. . .]
The rituals she refreshed each dusk had begun to falter. Not from time—from him.
[. . .]
Silas was Bloodbound—a product of the ancient order that passed magic through blood, binding kin not by affection, but by domination.
[. . .]
A force that wanted to shape, not shield.
[. . .]
They wouldn’t just follow. They’d become something new. Not Bloodbound. Not Wardsworn. Something untested. Powerful.
[. . .]
It hadn’t been fair. It hadn’t been clean. But it had been necessary.
[. . .]
Kaelenmor was meant to hold against intrusion—not reunion.
[. . .]
Lillian moved to the last ward— Not a shield. A flare.
[. . .]
The porch creaked—no echo this time. No memory. Just arrival.
[. . .]
Eyes not made for expression, but for measuring. For hunting. They didn’t merely watch. They devoured.
[. . .]
A flicker touched his mouth—not a smile, but the ghost of one.
[. . .]
“Where. Are. They.” Not a question—a command.
[. . .]
His words moved through the spiral carved into her skin—etched not by his hand, but by blood.
[. . .]
Together, they didn’t ask. They rewrote.
[. . .]
Lillian’s magic stirred—not memory, but instinct.
[. . .]
Something shifted behind his gaze. Not surprise. Strategy.
[. . .]
“That hope—they’ll return. Not just to the magic. To you.”
[. . .]
He exhaled—not impatient. Resolved.
[. . .]
“Breaking the seal won’t give you control,” she said. “It was cast to protect them. Not just from you. From what you wanted them to become.”
[. . .]
“One hears the wards—no training, no trigger. She carries my magic like it was etched into her bones.”
[. . .]
“They aren’t yours to shape. Not Wardsworn. Not Bloodbound. They’re something else—
[. . .]
Silas stilled. Not rage—Hunger.
[. . .]
“Control doesn’t need chains. Just purpose.
[. . .]
“Blood remembers,” he intoned. “It doesn’t ask permission.” Another beat. “I don’t need their consent. I just need him.”
[. . .]
He pressed his cheek to hers. Not tender. Not mournful. Just control.
[. . .]
Lillian’s vision blurred—not from weakness, but fury.
[. . .]
Not to summon. To spark.
[. . .]
But she edged closer—not to shatter, to thin the boundary. Just enough.
[. . .]
She didn’t resist. She let it in.
[. . .]
But the moment had shifted. Not ruthless. Ritual.
[. . .]
And Lillian went still. Not bound. Not his. Never again.

NB: this brings us only to the end of Chapter 1 with these examples. It goes on in the same fashion. It's a lot!

There's also a very strange clipped style used heavily throughout the text, one loaded with constant supposed melodrama and dire pronouncements but lacking in substance, paired with an excessive use of hard returns, creating an endless stream of sentence fragments with each on a new line of text. This is paired with a lot of extra line breaks in between ... paragraphs? It's hard to tell what the style is trying to communicate with the line spacing, which I don't think I've ever seen used quite to this extent in a novel, although I have seen it in AI chatbot text windows. By sheer coincidence, I'm sure! Because the author was clear, this book is not AI-generated, remember.

To ease into examples of this style from this book, first I want to share a couple passages from other books that I believe ARE AI-generated, unlike this one. Examine this passage from Skyfall Rebellion by Jeffrey Stanley, taken from the sampling of ChatGPT cover art above. Pay attention more to the paragraphing than the prose but also the prose:

Not a weapon. Not a cure.

A becoming.
=====================
The first of them rose from the crater in silence.
Their eyes shimmered with fractured time.
Their bones hummed with something deeper than sound.

They were called monsters.
But they called themselves Echoes.

Because they carried memory in their marrow.
Because they spoke the names of the forgotten in their sleep.
Because they refused to let pain be wasted.

They bound themselves not with chains, but resonance.

They did not rebuild the old cities.
They did not mimic the arks.

They listened.

To the ground.
To each other.
To the pulse that had always been there—buried beneath the noise of empire.
=================================
Now, the sky is cracked.

The arks drift, shadows of their former selves.
The world below stirs with new breath.

And in the ruins, a whisper rises—not of vengeance, but of remembering.

The war did not end.

It transformed.

And what comes next does not ask to rule.
It asks to endure.

It asks to speak the names that were stolen.
It asks to sing what was silenced.

It asks—

Will you listen?

Here's a shorter sample, this time from Faster Than Thought: Book I of the SOVRIN Threshold Trilogy:

"Something's off," he said quietly. "I can feel it."

Lena didn't respond. She was staring at the last simulation frame.

It didn't show a system collapse.

It showed silence.

Like the sim hadn't failed... it had reached an endpoint.

And something, or someone, was waiting on the other side.

The simulation hadn't failed. That was what kept circling in Lena's mind as she cross-checked every timestamp and boundary signature.

Drivesim Twelve had completed its process.

It hadn't crashed, hadn't looped, hadn't hit a numerical instability and died.

It had run and concluded.

The logs didn't reflect a failure state.

They reflected... closure.

Do you see what I mean about excessive paragraph spacing, constant negative statements that are then... dramatically resolved?

Let's take a look at this book now, The Thread:

It hadn't vanished. Just sunk deeper.

He called it a scar. A rash. Bad lighting.
Anything but what it was.

Because when the visions returned, so did the heat—
low. Rhythmic. Alive.
Not a wound.
A brand.
[. . .]
Symbols she'd drawn without thinking—idle etchings, at first.
Then they began to hum.

They hadn't meant anything. Not really. But some night, they pulsed louder—like they remembered something she didn't.

A quiet ritual.
Protection by instinct, not instruction.
Something old, rising through her hands.
Proof that magic wasn't just story.
It was survival.

These weren't just sigils.
They were anchors.

Her eyes drifted shut.
The hum didn't silence the noise—
but it held it still.
[. . .]
She felt it radiating from them—
that golden pulse of affection,
of togetherness,
of two people wrapped in their own little world.

It wasn't flashy.
It wasn't loud.
It was just... real.

And God, how she longed for that.

It wasn't the romance or the touch she craved—
it was the closeness.
[. . .]
She didn't know his name.
Couldn't picture his face.
But the shape of his mind pressed close—
frayed at the edges, and somehow known.

Not Mara.
Not a stranger.

Deeper.
Bound.

Not a threat—
but something breaking beside her.

Wolf's bold new innovation is to push this style even further, splitting lines even within sentences instead of waiting for each period like a schmuck before hitting "enter".

Of course, everyone harps on about em-dashes being a sign of AI writing, which I don't agree with at all. I've long been a fan of the em-dash, it interrupts so delightfully. This book clearly takes this to heart. In addition to the examples already shown, there are passages like this one that make artistic, judicious use of the em-dash:

Cold air.
Dim candlelight.

Shadows stretched across a symbol-laced floor—sharp, precise.
For a moment, he traced the geometry—clean, deliberate, too exact to be random.
Etchings curled through the old wood like veins—alive beneath the surface.

The scent of lavendar lingered beneath the dust—warm, cloying, edged with something burned.

He wasn't part of this.
And yet he was here—drawn into a place he's never set foot.

See, that is exactly the right amount of em-dashery.

Anyway, there you have it. Sure, it's a difficult style to rally behind, rendering the book utterly intolerable and unreadable, but at least it's not AI-generated. I know it's not, because the author said this book didn't belong on a list of AI-generated books published in August 2025. The book was published in August 2025, so it can only be the AI part. that she objected to. Not AI-generated!

Unless...

No, it couldn't be that a person who would publish an AI-generated book would not want that feature to be known, would they? Because it would drive away readers? And, it couldn't possibly be that the author belongs to that group of people I have seen online differentiating between AI-"generated" and AI-"assisted", could it? I mean, can you believe that some people think that because they contributed some ideas or gave direction to a generative AI model, rather than letting it just churn out any old slop without further input, that puts their book into a different category? Or that they think since you can't "logically" "prove" a book was created using AI after the fact, because pointing to all of the rank deficiencies present in the book that are also insanely common in undeniably AI-generated fiction, isn't iron-clad "proof" and to merely express your personal certainty based on an unhealthy degree of unforced exposure to AI slop books before and since, is not allowed because it might somehow cast a poor light on a book?

Nope, that can't be it all.

[Stephanie Dunigan · Rating 1 out of 5]

I won this book in a Goodreads giveaway. This is my honest opinion. I was excited to read this, but it became very difficult to understand. I felt obligated to finish this since it was given to me, otherwise I would have DNF’d it after the first few chapters. I had a hard time understanding it.

[Kari · Rating 1 out of 5]

Pros:
-
Cons:
- Unapologetically, unrepentantly AI-generated.
- ChatGPT "punchy thriller" writing. Every line. All. Disconnected story. No link. Just nonsense.
- Amateur writer/AI spaced lines to pad out pages.
Comments:
Some AI writing is more difficult to detect and takes repeated exposure and context clues to hone in on. This one is blatant from the get-go, with the "author" generating that disgusting, insufferable way of GPT 4o creating "meaning". It's about as meaningful as saying something like, "The sun rose. It painted the sky with a waking blue—but the revolt didn't stick. Faded. Screaming. And Neptune knew its prison. Watching. Waiting. Not breathing—just bread".
God forbid anyone is suckered into buying a paper or hard copy of this, with all the extra spacing shoved in. That said, this book would be Exhibit A for:
- Making it illegal to waste precious resources.
- Banning self-inflicted torture via words.
- 310% tax rate on anyone attempting to profit off of generative AI and a $500 fine for every successful sale.

[Kat · Rating 1 out of 5]

I won this book in a Goodreads giveaway. My opinions are my own.

DNF at about 20%. I just couldn't go any further.

The prose is fragmented and strangely written, with ellipses, dashes, and non-traditional paragraphing. For a brief period, I thought it might be written in verse, but the language isn't nearly strong enough to support that theory. I was nearly a quarter of the way into the book, nothing was really happening, and it was just very strange. I'm not opposed to strange, and I'm not opposed to non-traditional, but this was not a cohesive work. Nothing was there to pull me in and make me want to continue.

[Jessica · Rating 5 out of 5]

It was a great book that a friend recommended to me. Fast read, and exciting. I would recommend it to anyone who likes that kind of book. I'm not sure where all the AI accusations are coming from, but I suppose trolls are everywhere now. It's a shame.

[Shelly Moon · Rating 1 out of 5]

Did not finish. I got a few chapters in and nothing was making sense. The staccato writing style was nerve-wracking. I had high hopes, but they were quickly dashed. Maybe I am just not the right audience for this one?

[Lacrima Mundi · Rating 1 out of 5]

This screams already in the blurb: AI "written" and it doesn't get better once you start reading the sample.

[Landon · Rating 5 out of 5]

It was a good story by a first-time author. Well written and fast paced. A few great twists with a nice cliff-hanger ending to line up the second book.

[Courtney Pityer · Rating 5 out of 5]

I won this in a giveaway