Skip to main content
📚
Keeping long work consistent

Month eleven stops contradicting month one

Consistency stops depending on anyone's memory, human or otherwise

The Problem

A long manuscript, a large codebase and a formal report have one thing in common: hundreds of small decisions that must not contradict each other.

Nobody holds them all in their head, and a model certainly does not hold them between sessions. So month eleven contradicts month one, and neither the model nor you notices until someone else does.

How Stompy Helps

Lock the canon: the characters and the rules of the world, the naming constraints, the architecture choices. Record each editorial decision together with its reason.

Before drafting anything, the model checks the work against the canon that applies. A continuity error is caught before the page exists, and a later session does not quietly undo an earlier decision, because the reason is on file.

The same method carries from fiction to code to formal documents, because each is a curated body of decisions. It carries to repeating work as well. A near-daily publishing routine can run entirely on locked rules: a check every piece passes before it ships, a start-up checklist that loads the voice and strategy before drafting begins, and a rule for bringing older material back round. Ours has run that way for months.

The limit, plainly: only what you lock is kept. Continuity is only as good as the canon you locked, and on a small, fresh project the overhead is not worth it.

Integration Walkthrough

1

Lock the canon, one fact per entry

Keep entries small and named so they can be found. Add tags to group them.

lock_context(
project="my-novel",
topic="canon_the_harbour_town",
content="""The harbour town has no railway. Everything arrives by sea or the coast road.
Why it matters: chapters 3, 9 and 14 depend on the delay.""",
tags="canon,setting"
)
2

Record the decision with its reason

An editorial or architectural choice, and why it was made.

lock_context(
project="my-novel",
topic="decision_narrator_voice",
content="""Decision: first person, past tense throughout.
Why: the late reveal only works if the narrator is looking back."""
)
3

Check new work against what applies

Before drafting, search for what bears on the scene, or read several named entries at once.

context_search(project="my-novel", query="how people travel to the harbour town")
recall_batch(project="my-novel", topics=["canon_the_harbour_town", "decision_narrator_voice"])
4

For repeating work, lock the routine

A check every piece passes, and a start-up checklist read before drafting.

lock_context(
project="my-newsletter",
topic="pre_publish_check",
content="""1. Every number has a source and a date.
2. Voice matches the style entry.
3. No claim contradicts a locked decision.""",
priority="important"
)

What You Get

  • A later session knows what an earlier one decided, and why
  • Continuity errors are caught before the page exists
  • The same method works for fiction, code and formal documents
  • Repeating work can run from locked rules and checklists

Start your own record

Join the waitlist and we will tell you when your place is ready.