Your AI remembers your rules.
Then breaks them anyway.
Memory is table stakes now. outer.bot makes your rules binding: violations get blocked, drift gets caught, and you get the receipts. On any model, any tool, in a memory you hold.
Start remembering> explain the auth flow
Which auth flow? I don't have any context on this project — can you share the relevant files?
> explain the auth flow
Session tokens are issued in auth.php and validated in middleware.ts — this is the flow you refactored in March to fix the expiry bug.
Delivered isn't the same as obeyed. Scroll to see the difference.
Two problems wear the name "memory"
Delivery
Delivery is getting your context in front of the model. Hooks, proxies, retrieval, half a dozen tools now do this well. It's solved.
Adherence
Adherence is the model actually following that context instead of drifting from it fifty turns later. Nobody else is solving this.
outer.bot does both. It delivers your project's memory reliably, and then it makes the important parts binding, so a rule you've written can't be silently ignored.
How it works
point
Base URL or personal proxy URL.
remember
Briefing auto-builds from traffic + GitHub.
recall
Every session starts informed.
The memory layer
Compression is halftone for conversations — fewer dots, same picture.
Fusion + Tandem
Fusion
Two models answer. A third keeps the best of both.
Tandem
A frontier model writes the plan. A fast model builds it. You approve every step.