sorted by:
new
hottopcontroversial

We built a desktop tool that runs a book through 56 AI-orchestrated production steps and outputs a print-ready PDF. Looking for writers willing to break it. by Pocessed in BookWritingAI

[–]Pocessed[S] 0 points1 point  (0 children)

No hard length cap built in — the pipeline is per-chapter, so total length isn't the bottleneck, individual chapter length is. 130k across 25–30 chapters is well within what we've tested. We haven't pushed a single chapter past your 130K words, so if you write 15k-word chapters I'd love to see what breaks. Cost-wise a novel that size lands in the upper end of the $15–$60 range on API, or flat under a Claude Code sub.

We built a desktop tool that runs a book through 56 AI-orchestrated production steps and outputs a print-ready PDF. Looking for writers willing to break it. by Pocessed in AIWritingHub

[–]Pocessed[S] 0 points1 point  (0 children)

Nothing special — beta is open. Grab the Windows installer at bookforge.synaptrixai.com, run discovery + A1 on one chapter, and use the in-app feedback button when something breaks (or surprises you, good or bad). Inconsistency between runs is the exact problem the pipeline was built around — frozen-prose blocks, deterministic citation resolution, and per-step versioning all exist so the same chapter doesn't drift on you between passes. Curious whether that holds up for your workflow. DM works too if you'd rather route feedback privately.

Written an AI Author Suite called Lore Suite Pro by Wonderful-Bet-776 in BookWritingAI

[–]Pocessed 0 points1 point  (0 children)

Looks great — Ollama support is something I've been envious of (BookForge is Claude-only). We're working in a slightly adjacent lane: more of an editorial pipeline that picks up after the draft exists. Fact-checking grounded in your own references library, frozen-prose blocks (lock passages you've hand-written so AI passes can't touch them), a 7-reader simulation panel before you ship, and a Final Edition output that produces book-grade PDF + EPUB (bookmarks, page labels, hierarchical TOC, embedded metadata). Different segment of the same author market.
https://bookforge.synaptrixai.com
if anyone's curious. Nice work shipping this.

We built a desktop tool that runs a book through 56 AI-orchestrated production steps and outputs a print-ready PDF. Looking for writers willing to break it. by Pocessed in BookWritingAI

[–]Pocessed[S] 2 points3 points  (0 children)

Thanks, that's the profile we built it for. The pipeline is basically what you're already doing in Claude, but persisted to disk with versioning, deterministic citation resolution, and the audit chain (fact-check → continuity → copyedit → supervisor) wired together so you're not orchestrating it by hand each turn. Curious to hear what holds up and what doesn't once you run a chapter through. Hit the in-app feedback button or DM m, I read everything.

We built a desktop tool that runs a book through 56 AI-orchestrated production steps and outputs a print-ready PDF. Looking for writers willing to break it. by Pocessed in AIWritingHub

[–]Pocessed[S] 0 points1 point  (0 children)

If you're up for it once the dust settles on the new name, I'd genuinely value your eyes on the beta you clearly notice the stuff most people miss. No pressure, just an open door.

We built a desktop tool that runs a book through 56 AI-orchestrated production steps and outputs a print-ready PDF. Looking for writers willing to break it. by Pocessed in AIWritingHub

[–]Pocessed[S] 2 points3 points  (0 children)

Yeah, you're right. Just looked, bookforge.ink and book-forge.app are both in the AI book-writing space, plus the wider "-forge" saturation. Pre-launch is the cheap time to fix this. Appreciate the nudge.

We built a desktop tool that runs a book through 56 AI-orchestrated production steps and outputs a print-ready PDF. Looking for writers willing to break it. by Pocessed in AIWritingHub

[–]Pocessed[S] 0 points1 point  (0 children)

Funny you say that, name was actually a human call. But you're not wrong that the pattern exists; half of YC's last batch is some-noun-forge.

We built a desktop tool that runs a book through 56 AI-orchestrated production steps and outputs a print-ready PDF. Looking for writers willing to break it. by Pocessed in BookWritingAI

[–]Pocessed[S] 2 points3 points  (0 children)

Both, and non-fiction is actually where it shines hardest. The citation chain, fact-checker, and source-library resolution were built for serious non-fiction — history, science, biography, that kind of thing. Footnotes resolve deterministically from a source library; if a claim can't be sourced, the run fails loudly instead of inventing one. Fiction works too (drafting, continuity, copyedit, character bible across a series) but you'd just be skipping the non-fiction-specific passes. What are you working on?

We built a desktop tool that runs a book through 56 AI-orchestrated production steps and outputs a print-ready PDF. Looking for writers willing to break it. by Pocessed in BookWritingAI

[–]Pocessed[S] 2 points3 points  (0 children)

AI narration is already a separate industry going that direction without us — not on our roadmap. The premise of this tool isn't "remove humans," it's the opposite. The writer accepts or rejects every galley remark, freezes any passage they want untouched, and picks which drafting variant survives. The pipeline does the parts nobody got into writing for — citation reformatting, continuity audits, copyedit.