It reads, not writes
No blank-page takeover. No prompt theater. No trying to co-author the manuscript. The product begins after a draft exists and helps the writer see it more clearly.
Kaizen R/W is built for serious drafts. It surfaces the few passages worth your attention, learns what is intentional, and helps you revise without turning your manuscript into a dashboard.
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 exactly the same way. It made her distrust the kindness before she trusted the grief.
Outside, bells were already starting. Not an alarm. A welcome.
The market is full of drafting assistants, broad writing utilities, grammar layers, and story systems. Kaizen R/W takes a narrower stance: it reads like an attentive editor, not a co-author, and it only interrupts when a passage is worth attention.
No blank-page takeover. No prompt theater. No trying to co-author the manuscript. The product begins after a draft exists and helps the writer see it more clearly.
Teach the system why something is deliberate and that decision becomes part of how future passes interpret the book.
A manuscript should feel like a book, not software. KRW keeps chrome light, opens one panel at a time, and avoids layout shifts that break reading rhythm.
This is the part most products miss. KRW is not just scoring text. It is learning how this manuscript should be read as the author dismisses, explains, and defers.
“She smiled the way people do when they have already forgiven themselves.”
KRW flags the passage because it sharpens character judgment while potentially flattening ambiguity. It is worth attention, but not necessarily wrong.
The author explains that this narrator often makes fast moral judgments that are later revised. KRW stores that preference and feeds it into later prompts so similar phrasing is less likely to be treated as accidental overreach.
Everything here is chosen to support reading flow, author agency, and a calm path through complex drafts.
AI chapter scanning is designed to surface a handful of findings instead of flooding the page.
Teach and dismiss actions feed future prompts, so the system adapts to the manuscript over time.
Tab, Enter, D, T, and F keep the workflow in motion for writers who want to stay in the text.
Inline review expands in place without turning the manuscript into a maze of sidebars and drawers.
Cross-chapter scanning surfaces higher-level observations after the local reading pass is complete.
Hide categories, control noise, and shape the editorial pass to fit the kind of revision you are doing.
Touch TOC, swipe chapter navigation, and responsive panels extend the reading model to smaller screens.
Save your state, export reports, and keep control of the editorial conversation around a draft.
KRW is strongest in the stretch between draft completion and outside editorial feedback. It is built for the author who wants developmental-quality signals before pages leave their hands, and who cares about preserving voice as much as improving clarity.
KRW's lane is narrower and more defensible: a better first reader for revision.
Writers do not just need capable AI. They need a product that feels safe, predictable, and easy to understand.
Core state lives in browser storage instead of depending on server-side persistence for basic use.
Writers can use their own provider key and keep control over model access inside the app settings.
The difference between noticing, teaching, dismissing, and deferring is clear in both UI and product logic.
No build step for the frontend, no app-shell bloat, and a deployment model that stays understandable.
The product architecture reinforces the product philosophy: static frontend, AI proxy worker, browser-first persistence, and streaming feedback that keeps revision moving.
# Static site
npx wrangler pages deploy public/ --project-name=krw
# Worker
cd worker
npx wrangler deploy
The result is a product that stays close to the metal: easy to host, easy to reason about, and intentionally constrained.
No. KRW is designed to give immediate, teachable revision feedback before pages go to other humans. It is a first reader, not the final authority.
That is not the core job. The product is designed to read attentively, mark passages worth attention, and preserve author agency during revision.
Broad assistants are designed to be everywhere and do everything. KRW stays narrower: it focuses on revision, reading flow, teachable feedback, and a calmer manuscript experience.
The teach loop is built specifically to reduce that problem. Explain an intentional choice once and later prompts can incorporate that context.
Yes. This marketing site is static HTML, CSS, and JavaScript, so it works well on GitHub Pages, Cloudflare Pages, Netlify, or similar static hosts.
Kaizen R/W is built for authors who care about judgment, not just capability. Enter your email below and we'll send you an access link.
No account needed. No password. We send a link and your browser remembers you.