Asten for fan-fiction writers

Asten uses canon the way fandom does. Settle what is true in your version, keep source canon you have changed on file as contested, and get a mark when chapter 40 contradicts chapter 4.

Try the pre-alpha How it works

In short

Asten lets fan-fiction writers record canon as settled facts, keep source canon they’ve changed on file as contested, and get notified when the story contradicts what they settled. Everything stays in a file on your own computer; Asten never generates prose and never trains on your writing.

Common problems

Long fics, longer memories

A 300,000-word work-in-progress and readers who notice everything.

AU rules you invented

You changed one thing about canon. Now you have to remember its consequences.

AI scraping worries

You want your writing to stay yours, not become someone’s training data.

How Asten helps

Canon, literally

Settle facts from the source and from your own story.

Learn more

Contested, not deleted

Keep source canon on file as contested. Your AU facts are the ones Asten checks.

Learn more

Local-first

Your fic lives in a file on your computer. No account, no upload, no training.

Learn more

Export anywhere

Compile to HTML or Markdown for posting.

Learn more

The AU where he lived

In source canon, Captain Oren dies. In your AU, he doesn’t.
You keep the source fact “Oren · status · dead” on file as contested, so it never raises a mark, and settle “alive” for your story.
Months later an old outline note settles him as dead again. Asten marks the clash (CANON-E013) before you post the chapter.
Throughout, the fic stays in a file on your laptop.

Write a name

𓅱o𓂋r𓇋e𓈖n

A playful alphabet using uniliteral signs. Real Middle Egyptian spelled names differently and mostly left out vowels.

Limits

Asten doesn’t import a franchise’s canon for you. You settle the facts that matter.
There’s no posting integration; compile to HTML or Markdown and post as usual.
It is a pre-alpha (release 0.0.1b); expect rough edges.