Atlas.
A persistent assistant for the work between the apps.
Adam’s personal AI setup brings business context, messaging access, and day-to-day development work into a persistent environment.
Personal operating system01 /The context
What needed
to work better.
Working across multiple ventures means repeatedly rebuilding context: what changed, what needs attention, and where the relevant information lives. A personal assistant is more useful when that context survives the next conversation.
02 /What was built
- A persistent Claude Code assistant running on an always-on Mac Mini.
- Phone and desktop access, with an Obsidian-based body of business context and working memory.
- An independently scheduled morning briefing and documented monitoring and recovery mechanisms.
03 /The thinking
Atlas is a personal implementation developed for Adam’s operations with technical collaboration. The useful lesson is the connection between lasting context, access to the right tools, and clearly owned routines.
04 /The decisions
Context is stored where a person can read it
Business knowledge lives in plain files rather than inside a product, so it can be read, corrected and carried elsewhere. An assistant whose memory is only legible to itself is a dependency, not an asset.
Consequential actions stop and ask
Anything customers or live systems would feel is described in plain language and waits for a decision. The rule holds even when the action is obviously right, because being correct and being reversible are different things.
The briefing is scheduled, not requested
A daily brief that has to be asked for gets asked for twice and then forgotten. Arriving on its own is most of its value.
05 /Where it fits
A smaller, focused version can help an owner find business knowledge, prepare a briefing, or assemble the context needed for a recurring task.
Explore the service06 /Questions
Is Atlas a product?
No. It is a personal implementation, described here from documentation and Adam's own account of using it. Access to this website's code does not imply access to the machine it runs on.
Does it act on its own?
It does scoped work on its own and stops for anything with consequences. The interesting engineering is in where that line sits, not in how much it can do unsupervised.
Keep exploring