# Week 9 — Anchor: "I launched a writing tool this week — the one I built because I kept forgetting my own fantasy world."
Type: Newsletter issue section + the seed for all Week 9 posts
—
I launched a writing tool this week — the one I built because I kept forgetting my own fantasy world.
This was the week my side projects started talking to each other. The writing tool I teased last week is live at continuumscribe.com, and I spent the week doing the launch I actually believe in: not a Product Hunt blast, but conversations where fantasy authors already are. The tool solves a humiliating personal problem. Fourteen chapters into my series, I could not remember which character knew about the shadow organization, or when the magic system's rules were established. My world had outgrown my memory.
What I built is a knowledge-graph writing workspace. Characters, locations, magic systems, and organizations are entities, not notes. Scenes @mention them, an AI consistency check flags contradictions before readers do, and a character-chat mode lets me explore who a person is. Two-way Obsidian sync means my words are never locked inside a tool. Stack: Next.js, Postgres with pgvector, LiteLLM over models I already run. Same box in my house, same boring pattern, one real problem solved.
The API also crossed two weeks, and I owe you the honest numbers: a trickle of signups, a quiet day two, and a handful of people who actually made a successful first call. No spike, no revenue worth mentioning — and I am not dressing that up. What changed is which number I watch. Signups are wishes. The first successful call is data. Free accounts that never call the API are decoration; the people who hit the free tier's ceiling are customers waiting for a reason.
One old failure surfaced in review this week and showed the same lesson from the other side: the scraper that feeds my health-content pipeline broke in three places in a single week — silent, empty returns, no alert. The fix was per-source retry rules and an alert when a feed returns nothing. A system that can't tell you it's broken is untested, not finished. Full teardown is on X this week.
Tools I leaned on: Next.js + pgvector + LiteLLM (continuumscribe), Umami (the honest numbers), and my events log — still the best dashboard I own.
Next week: the community launch week for the writing tool — what authors actually tell me — and the first real revenue numbers from the API, whatever they are.