Step 01
You finish the draft
Eighty thousand words. Eighteen months. A middle-grade adventure novel for your nephew, who kept asking when it would be done. Parts of it came fast. Parts came only because you asked an AI for structural feedback on Chapter 14 and the climax finally clicked. You did not hide that. You just did not have a way to explain it cleanly — until now.
Step 02
The agent asks
Your query letter lands a request for the full manuscript. Two days later an email arrives with one line that makes you pause: "Before we read it, can you tell us how AI was used in drafting?" A year ago this question would have been insulting. In 2026 it is standard. You are grateful somebody is asking.
"Before we read it, can you tell us how AI was used in drafting?"
Step 03
You open the project
The manuscript has lived inside RedInkAI from Chapter 1. The InkTrail is eighteen months deep. 312 events. Every AI consultation. Every adoption decision. Every scene rewritten after AI with the AI turned off. The Cognitive Audit Report fills in automatically with your adoption breakdown: 68% of AI suggestions rejected, 19% partially adopted, 13% adopted. The prose percentages are higher for your own words than you expected, and that feels true.
Step 04
Your reply
You write back: "Thank you for asking directly — this is the right question in 2026. AI was used for structural feedback and craft reasoning checks on four scenes; each consultation is logged and the adoption breakdown is attached as a Cognitive Audit Report. The voice, characters, and story decisions are mine. If you want to spot-check any scene, the verify URL will show you exactly what I adopted and what I rewrote."
Step 05
The agent reads the trail
They open the verify URL. They see you rewriting the climax three times after AI gave you a structurally tidy but emotionally wrong solution. They see the adoption-rate graph flatten to near-zero in the dialogue-heavy chapters. They see your notes in the margin of your own InkTrail: "too clever, not my kid." They read two paragraphs and then request the full MS with the pitch added.
Step 06
The story goes forward
The offer comes three weeks later. The audit report goes into the author-publisher file. The book carries a small disclosure line in the acknowledgments — it fits in one sentence because you have a record to point at. Your nephew reads the first chapter on the phone with you, and none of the sentences that matter to him were written by anything other than you.
"This is the clearest AI disclosure we have seen from an unagented submission. Thank you for making it easy to say yes."
The full timeline
The voice was always yours. The proof is now automatic.
- You open RedInkAI and start Chapter 1Month 0
- InkTrail logs 312 events across 18 monthsMonth 0–18
- Agent asks about AI useDay +2 from query
- You generate the Cognitive Audit Report90 sec
- You compose your reply3 min
- Full MS requestedSame day
For the next manuscript
Your next book won't need a forensic defense.
The hardest part of an AI-disclosure question is reconstructing eighteen months of decisions you barely remember. With RedInkAI open from the first sentence, the disclosure writes itself while you write the novel.
- ✓Start the project the day you outline. The InkTrail records every chapter, every revision, every AI consultation from word one.
- ✓Write the way you already do — AI-on for craft reasoning, AI-off for voice. Both states are tagged automatically.
- ✓When the next agent or editor asks, the Cognitive Audit Report is two clicks. Adoption breakdown, verify URL, disclosure language — all already correct.
Write your novel with AI in the room, not AI on the page.
RedInkAI was built by an author for authors. Free tier includes ten guidance credits and the same verifiable audit trail every agent and editor is starting to ask for. No card required. Your voice stays unmistakably yours.
Or reach the founder directly at redinkaistudio@redinkai.com
Other scenarios