Decide once; every session starts from it
Your standards stop depending on whether the model happened to remember them
The Problem
A decision made in a chat lasts as long as the chat. The next session has never heard of it, so you explain it again. Or you do not, and the model quietly does something different.
Instruction files help until there are several of them, in several tools, each slightly out of date.
How Stompy Helps
Lock the decision as a rule. Every later session, in any tool, can start from it.
The most important rules go in a single standing-rules context that every session checks. It points to the detail rather than repeating it, and you are the one who updates it. That is deliberate: a short list that is read every time beats a long one that is skimmed.
Rules are versioned. When you change your mind, the new version replaces the old one and the old one stays in the history, so you can see what you believed at the time as well as what you believe now. Every item also has a state (active, parked, delivered or archived), so the record can say what is live and what has been put to bed.
Mistakes go in the rulebook too. When something goes wrong once, on something that mattered, you lock what went wrong and why, and every later session starts with that lesson in hand. Our own rules each earned their place by costing us something.
The limit, plainly: only what you lock is kept. Retrieval is the strong part; whether a model follows a rule is still the model's job. And a short list asks for pruning.
Integration Walkthrough
Lock the rule where every session will check it
Mark the few rules that must always be read as always_check. Keep the list short and let it point to the detail.
lock_context(project="my-project",topic="working_rules",content="""1. Check the decision log before changing a settled choice.2. Every claim names its evidence.Detail: recall_context("house_style"), recall_context("review_checklist")""",priority="always_check")
Change your mind without losing the history
Locking the same topic again saves a new version. Read an earlier one by naming its version.
lock_context(project="my-project", topic="working_rules", content="...updated rules...", priority="always_check")recall_context(project="my-project", topic="working_rules", version="1.0")
Put things to bed with a lifecycle state
Mark what is live, what is parked, what is delivered and what is archived. Nothing is deleted.
set_lifecycle(project="my-project", topic="old_approach", state="archived", note="Replaced by the new approach")project_history(project="my-project", kind="rule_changed")
Lock the lesson, not just the fact
When something goes wrong once, lock what and why so a later session starts with it.
lock_context(project="my-project",topic="lesson_unchecked_import",content="What went wrong: ... Why it mattered: ... What to do instead: ...")
What You Get
- One short standing-rules context that every session checks, pointing to the detail
- Versioned history: what you believed at the time and what you believe now
- Lifecycle states: active, parked, delivered, archived
- Mistakes become rules, so a failure is not made twice
Start your own record
Join the waitlist and we will tell you when your place is ready.