How Auric works.

AI-assisted work is now most engineering work. The unit of disruption is no longer the lost laptop — it's the lost session. Three hours of work disappear at every context reset because the tools forget the operational state of the work the moment the session ends.

“Memory” features in AI tools don't fix this. They summarize chats. They don't preserve operational state.

The problem isn't memory. The problem is continuity.

Git preserved the state of code. Auric preserves the state of work — the structured set of decisions, dependencies, open loops, and next actions that constitute the in-progress mental model of a project.

Auric is not an LLM. It is a continuity layer that sits between the developer and whichever AI tool they use today.

A simplified shape of what gets captured per session:

{
  "session": "04f·2c",
  "project": "auric",
  "decisions": [
    {
      "id": "auth.store",
      "value": "sqlite",
      "reason": "operational simplicity"
    }
  ],
  "dependencies": ["src/auth/middleware.ts"],
  "open_loops": [
    { "id": "refresh-token",     "state": "in_progress" },
    { "id": "validate-middleware", "state": "queued"      }
  ],
  "next_action": "Implement validation layer"
}