Redline: An Editor That Reads You Back

Two of our earlier essays diagnosed a specific failure mode of AI writing tools. Both pieces are still on this site, and you should read them if you haven't. Here's the short version.

The first essay, "Your AI Tool Doesn't Remember What You Rejected", made the case that the most important part of working with AI isn't the suggestions you keep — it's the ones you throw away. Every dismissal is a judgment call. Every "no" is expertise. And almost no tool on the market records that signal.

The second, "Why I Built an AI Audit Trail Instead of Another AI Writer", was the founder's case for why the world didn't need a 47th tool that generates prose. It needed one that proved the human in the loop actually mattered.

Both of those essays end in roughly the same place: here is the gap; somebody should build something for it. This essay is about what we built.

The gap, named

If you imagine the AI-writing space as a number line, the two endpoints are obvious:

On one end: tools that write for you. You type a prompt, you get back a paragraph. Your role is to accept, reject, or regenerate. These tools are good at producing fluent output and bad at producing your voice.

On the other end: tools that stay out of the way. Plain text editors. Word processors with autocorrect disabled. Your role is to type. The tool has no opinion about what you're writing.

Every interesting question about authorship lives in the gap between those two endpoints. What does it look like to have an AI present in your editor without having it write for you? What does it look like to have an editor that reads what you're doing — diagnoses, observes, raises questions — but never produces the prose itself?

That's the space Redline lives in.

What Redline actually is

Imagine handing your manuscript to a good copy editor — the kind who reads carefully, marks the margin in soft pencil, and asks questions rather than making changes. Redline is that editor, on the page as you write.

You're mid-paragraph. A small red mark appears in the margin. You hover — it reads something like: "This sentence is straining. The reader has to hold the whole arc before the verb resolves." That's it. No rewrite. No suggested replacement. Just the observation, quietly waiting for you to decide what to do with it.

Each note falls into one of a few editorial categories the tool surfaces — things like tighten (something in the prose is working too hard for what it's carrying), voice (the register is shifting in a way that might not be intentional), structure (the shape of a passage is competing with its point), and clarity or evidence (a claim is thinning out where it should be firming up).

You have three options on every note: Adopt (you take the observation and act on it), Dismiss (you've considered it and chosen not to), or Open in Redline editor (you want to ask a follow-up). Whichever you choose, the decision becomes part of the verifiable record of how the piece was written.

The point isn't that Redline is right. The point is that a considered editorial voice is present, quietly, while you write — and that every time you agree or disagree with it, that judgment is documented as yours.

Heuristic and LLM, together

Behind the scenes, Redline uses two complementary methods to notice things worth pointing out — one that runs fast in the background and one that goes deeper into the language. You never see either. You just see the notes.

The point of the split isn't the technology. The point is that the editor is reading you continuously without ever being loud about it. When there's nothing worth saying, Redline says nothing. When there is, it drops a mark in the margin — and you decide what to do with it.

Volume, because writing isn't one thing

Sometimes you want a quiet editor. You're in a flow state. You want to be left alone until you ask for help. Sometimes you want a loud one. You're revising. You want every observation the system can produce, because revision is the act of considering observations.

Redline has four volume settings: Off, Quiet, Normal, Active. They control how often notes appear and how many can be open at once. You set this once per project. It persists. The editor honors your declared posture.

This matters more than it sounds like it does. Tools that don't give writers volume control either over-communicate (and get muted permanently) or under-communicate (and fade into invisibility). Redline lets you tune it to the work.

The audit trail, which is the whole point

Every Redline observation is written into the InkTrail — the verifiable record of how the work was written. The trail is cryptographically sealed and exportable as the Authorship Packet, which any reviewer can check independently, without needing our platform.

What that means in practice: when a publisher, a journal, a court, or a hiring manager asks "Did you really write this?", you don't argue. You hand them a packet that shows every editorial observation Redline made, every observation you adopted, every one you dismissed, every prompt you ran through Guidance, every manuscript checkpoint along the way. The packet is verifiable without our platform. The hash chain is its own proof.

This is the "memory for what you rejected" the first essay said the world needed. Not as a feature you turn on. As the natural byproduct of the editor doing its job.

What it's not

Redline is not a grammar checker. Grammarly is a grammar checker, and it's a good one for what it does. Redline operates at a different layer — the editorial-judgment layer that grammar checkers don't touch.

Redline is not a writing assistant. It will not generate paragraphs for you. It will not "improve" your prose. If you want a tool that writes the next sentence, there are dozens of those. Redline isn't competing with them.

Redline is not a chatbot. There is no conversation interface unless you explicitly open one. The default surface is the margin column. The default behavior is silence except when there's something worth pointing out.

The thesis, restated

The interesting space for AI in writing isn't generation. Generation is a solved problem with a thousand acceptable answers. The interesting space is the one where an AI sits beside you, reads what you're doing, raises questions you might not have asked, and keeps a clean record of how you responded.

That's Redline. That's why we built it.

If you want to see what it actually looks like in the editor, the demo has a teaser version with seeded sample notes — you can adopt or dismiss one to see the interaction, then sign up to get the full experience as you write.