03Restoration
Open your work exactly where it stood.
Not chat history. Not a summary. The working state of the problem — the goal, the approach in play, the constraints, what's blocking you, and the next move — restored in a breath.
Authentication Migration
Implement refresh token flow — in progress
Validate middleware — queued
Complete session persistence — queued
SQLite selected over Redis — Operational simplicity
Implement validation layer
Where the work actually was.
Not where the chat ended.
What it restores
The state of the problem, intact.
04The system
A single line, never broken.
WORK
You work in Claude, Cursor, Codex — wherever work happens.
READ
Auric reads the evidence — your conversations, code, and commits — as work happens.
PRESERVE
It reconstructs the state behind that evidence — decisions, constraints, open loops — and keeps the state, not the transcript.
RESTORE
State rehydrates in under a second when you return.
CONTINUE
Momentum, unbroken.
Built on protocols, not products.
The receipts
Built to be believed.
The entire system of record is a single local file. Copy it: that's a backup. Delete it: Auric is gone.
Restores are pure data assembly. Same file in, same context out — byte for byte.
Nothing is edited or deleted. Decisions are superseded, with the when and why on record.
Auric checks its own consistency and reports contradictions instead of hiding them.
Local-first. Offline by default. No telemetry, no account.
A system that tells you when it's wrong is the only kind you can trust when it says it's right.
Ownership
This isn't another AI memory layer.
Every AI is getting memory — and each one remembers only its own chats, locked inside that one tool.
But memory answers what was said. Work runs on state: what you're trying to prove, what you've ruled out, what's blocking you, what's next. A bigger context window just hands your AI more transcript to re-read. Auric hands it the state.
Your code already works this way. It lives in Git — owned by the project, not the editor. Auric does the same for the reasoning around the code.
Git tells you what changed. Auric tells you why it changed.
The work persists. Tools change.
Auric is the layer that outlasts the tool.
Begin
Never start over again.
Keep the thread — across sessions, tools, and models.