vol. iii · no. 31 · sunday, the 2nd of augustink on paper · also, software · a fresh kind of morning
feature deep-dive · memory

it read chapter 3.
it still remembers chapter 3.

Quarkle turns the manuscript into a living set of story notes, then keeps those notes current as the draft changes. chat and review passes can work from the book without asking you to rebuild the context every time.

chat · the hollow house.md
chapter 03 · 1,900 words in

Eldra pulled her hood back. Her eyes were the grey of a winter storm, the same grey her mother's had been.

· · · 37 chapters and 40 chat messages later · · ·
chapter 40 · you, in chat

quick continuity check: what color are Eldra's eyes again? don't want to contradict ch.3.

grey: the grey of a winter storm, same as her mother's. you set that in chapter 3, so anything else here would contradict it.

✓ ch. 03 · ln 42

try the toggle above: same question, memory on vs. off.

what quarkle keeps track of

four parts of the draft it keeps within reach.

01

characters

names, ages, relationships, physical details, the line where you first described them.

02

chapter events

chapter summaries and the story events Quarkle can reference when you ask about an earlier scene.

03

pinned canon

freeze the facts and rules that should stay fixed, even while the rest of the draft keeps moving.

04

revision history

see who changed an Atlas note, inspect the word-level diff, and return to a saved version.

how this compares

story-memory tools make different tradeoffs.

some prioritize a deeply configurable story bible; others rely mainly on a model's context window. Quarkle prioritizes manuscript-derived notes that feed directly into editorial review and chat.

bring the book. we'll remember it.