Most AI writing tools want to join the writing. KRW starts after the draft exists. It reads your manuscript like an attentive editor, surfaces the few passages worth a second look, and remembers what you tell it. The more you use it, the quieter it gets.
Mara kept the lantern low as she crossed the ruined nave. The glass underfoot gave back almost no sound. At the altar she stopped, not because of the body, but because of the impossible neatness of it. Someone had arranged the dead boy's hands.
The first time she saw Daniel after the fire, he smiled in It made her distrust the kindness before she trusted the grief.
Outside, bells were already starting.
KRW isn't scoring your text. It's learning how your manuscript should be read. Every time you dismiss, explain, or defer, the next scan gets smarter. That's the whole loop.
Mara kept the lantern low as she crossed the ruined nave. The glass underfoot gave back almost no sound.
The first time she saw Daniel after the fire, he smiled in exactly the same way and she distrusted the kindness before she trusted the grief.
Outside, bells were already starting. Not an alarm. A welcome.
The highlighted line is not a mistake. It is how this narrator judges people before the story proves her wrong.
She kept walking past the chapel entrance, where someone had left candles burning in glass jars.
She smiled the way people do when they have already forgiven themselves. The warmth in her expression was aimed at no one in particular.
It was a small chapel. The kind of place that always smelled like stone.
Voice: This sharpens character judgment while potentially flattening ambiguity. Worth attention, but not necessarily wrong.
Click Explain why, Got it, or Later on the left. Each one shapes how the AI reads future passages. That's the kaizen loop: small acts of attention, compounding.
KRW is for the stretch after a draft exists and before it goes to anyone else. It reads your manuscript like an attentive first reader, surfaces the passages worth a second look, and remembers what you tell it was deliberate.
No blank-page takeover. No prompt theater. No trying to co-author your manuscript. KRW starts after a draft exists and helps you see it more clearly.
Tell the system why something's deliberate and it remembers. That one decision shapes how every future scan reads your book.
Not like operating software. One panel open at a time. No sidebars. No layout shifts. The manuscript is the interface.
Everything here exists to keep you in the manuscript. Read, respond, move on.
The AI reads each chapter and marks a handful of passages. Not hundreds. Just the ones worth your attention.
Dismiss a mark and the system reduces similar noise. Teach it why something's intentional and it remembers across every future scan.
Tab through marks, Enter to open, D to dismiss, T to teach, F to flag. You don't have to leave the text.
No sidebars. No drawers. Notes expand inline, right where the mark is. Open one, the last one closes.
After the chapter-level scans, a cross-chapter pass catches the bigger patterns: continuity gaps, repeated motifs, pacing across the arc.
Too much voice feedback? Turn it off. Only care about pacing today? Show just that. You shape the pass to fit the revision you're doing.
Tap for the table of contents, swipe between chapters. The reading experience carries over to smaller screens.
Save your marks, export a revised manuscript, or pull a DOCX with comments. Your editorial conversation doesn't disappear.
KRW fits the stretch between finishing a draft and sending it to an editor or beta reader. It's for the author who wants developmental-level feedback before the manuscript leaves their hands, and who cares about preserving voice as much as improving clarity.
KRW stays narrow on purpose: a better first reader for revision.
Writers need a product that is clear about where manuscript text lives, when it gets sent, and what happens in between.
Your manuscript, marks, and dictionary stay in your browser. KRW does not keep a server-side copy of your draft.
When you run a scan or interpretation, only the relevant text is sent over HTTPS through a stateless proxy to the provider you chose. Requests are forwarded, not stored.
Your key stays in browser storage and is used only for the request you triggered. It is not kept in a server-side database.
You can always see what the AI flagged, what you taught it, and what got dismissed. No hidden background passes. No mystery state.
KRW is designed to feel closer to reading than to managing software. The manuscript stays at the center, and the technical pieces stay as small and quiet as possible.
The point is not to impress you with architecture. The point is to keep revision feeling direct: open the manuscript, run a pass, respond to what matters, keep moving.
No. KRW gives you feedback before your pages go to other humans. It's a first reader, not the final authority. Think of it as the pass you do before the pass that matters.
No. It reads your manuscript and marks what's worth attention. You decide what to do about it. The goal is to help you see your own draft more clearly, not to rewrite it.
Most writing tools show up at the drafting stage. KRW shows up later, during revision. It focuses on reading the manuscript you already wrote, then reducing repeat noise as it learns your intent.
That's the whole point of the teach loop. Explain an intentional choice once and the system carries that context into every future scan. It shouldn't flag the same thing twice.
Get an access link by email, or open the current build right now.
One email with your access link. No newsletter unless you ask for it.
