What makes an argument hold together

The book

I've been working on a book for the better part of a year, mostly in the evenings and on weekends. It's about textual criticism of the Bible, the kind of scholarship that's been widely accepted in the academy for over a century but has barely made it across the threshold of most religious communities. The Documentary Hypothesis, the hypothetical Q source behind the synoptic gospels, the Dead Sea Scrolls and how they line up against the Masoretic text, the choice the Septuagint translators made about a single Hebrew word in Isaiah and what that choice did to two thousand years of Christmas theology. Each of these threads is its own dense literature. They overlap in some places and contradict in others. Some of them only make sense if certain other sub-claims hold up first.

The work so far has been almost entirely research and structure. Reading sources, gathering evidence, mapping how it all fits together, watching the argument shift as I go. The chapter structure has only just clicked into place, which means the actual writing is about to start.

Two ways in

My thinking tends to happen in one of two modes, and this book has pulled me through both of them.

In the first mode, the work is natural. I gather evidence, sort through it, sit with it for a while, and at some point a thesis starts to emerge from the material itself. The reading shows me what the argument should be, rather than the other way around. In the second mode, I already have the thesis, usually half-formed from prior reading or from gut feeling, and my job is to gather evidence and counter-evidence and run the thesis through its paces to see what survives.

This book has been both modes at once. I started with a strong intuition about why the textual critical findings haven't reached most religious communities, and over the past year I've been gathering the evidence to test that intuition. The actual case I want to make has been shifting under me the whole time as the sources push back. Some of what I thought I would argue, I now don't. Some of what I now want to argue, I didn't expect to.

In either mode, the structural problem is the same. I have dozens of threads, and they only matter if they fit together into a single argument that holds.

The professor in my back pocket

This is the problem warrantd was built to solve, and the book is the reason I built it. The structure had been slipping out of my head faster than I could put it back, and I needed a place where the skeleton could live outside of me.

The thesis sits at the top. The sub-claims branch under it. The evidence and the sources hang off the sub-claims. When I drop a new source into the project, the tool gives me a clean read of what the author is actually arguing and how their position maps to mine. When I add a sub-claim, I can see what evidence supports it and what doesn't. When something I add contradicts something I established earlier, the consistency check catches it.

When I find a weak spot, I ask the tool to discover sources that support the claim or argue against it, so I can either strengthen what I have or rethink the claim entirely. The counter-arguments stop hiding in my peripheral vision. They surface, and I can address them or revise around them while the structure is still soft enough to change.

I'm in the driver's seat the whole time. The argument is mine. The book is mine. But the professor who used to live down the hall, the one I'd knock on the door of when I wasn't sure whether my reading of the Septuagint was defensible, is in my back pocket now. Available when I want them, silent when I don't.

The writing is mine

The chapter structure is finally in place, and the arduous part is about to start. That's the part I've been waiting for, the part where the voice goes, where the prose finds its rhythm, where the book stops being a research project and becomes a book.

Asking an AI for three paragraphs of competent prose on any topic now takes about ten seconds. The cost of fluent writing has fallen close to zero, which means fluency on its own no longer distinguishes good books from bad ones. What does is structural rigor: every claim earned, every counter-argument addressed instead of avoided, the skeleton holding from the first page to the last.

For months the book had been slowing down, the structure getting harder to hold in my head with every new source. warrantd is what brought it back to life. Once I had the tool I'd been trying to build, the chapter structure I'd been chasing for the better part of a year clicked into place in a matter of weeks.

The writing itself is mine to do. My voice, my prose, my decisions about what stays and what gets cut. The platform never had any business doing that part, and it doesn't try. What it does is keep the structure visible to me as I work, and I'm about to find out how much that matters when the prose starts.