A playbook is a procedure written once — the deploy, the translation run, the weekly report — and run by any of your agents, in any project, on any machine, the same way every time. Notes carry the handover from one session to the next. And the atlas is what playbooks make possible: a map of your whole system, drawn by your agent from the code and the live system, that every future session opens with.
Free tier · no credit card · playbooks and notes on every plan
A playbook is plain markdown: headings for the stages, fenced blocks for the commands, and what to read back afterwards to know it worked. It is stored for your whole account, not for one project — your projects stay separate, your procedures are shared. Any agent fetches it and runs it in its own harness; the memory only stores it. Say "save this as a playbook" and it is one. Say "use playbook deploy" and it runs.
Curated records hold the current truth and are tidied as it moves on. A playbook holds how, and nobody prunes a procedure. A recipe that took a week to find stays exactly as it was found.
Five agents on one project, or one agent on five machines — the deploy is the same deploy. What you learned once about a run is what every run knows from then on.
The steps, the exact commands, what to check afterwards, what went wrong last time and when. Your agent adds what it learns running it, in the same session.
Where a session stopped, what is live, what comes next — written by your agent, kept per project, the last five always at hand. The next session opens with it. Start the PC, say "continue," and it carries on.
The atlas is a playbook that teaches your agent how to map a project — and the map it draws is itself a playbook, so every session can open it. One root map per project: the boxes, the wires and what travels on them, the stores, and an index of plates. Four to eight plates, one per plane of the system, with the procedures inside the plate they belong to. Written by the agent from the code and the live system, never from memory.
verified <date> against <what> — and a reader trusts the map exactly that far.my-app-map — verified 2026-09-04 against commit a1b2c3d and the live containers
browser ──(requests, session cookie)──▶ api ──(SQL)──▶ postgres
│
└──(jobs)──▶ worker ──(files)──▶ object store
Wires: the browser never talks to the worker; the worker never reads a cookie.
Stores: postgres (users, orders — never card numbers) · object store (uploads).
Plates: my-app-map-api · my-app-map-worker · my-app-map-data · my-app-map-ops
Procedures: deploy → my-app-map-ops, deploy · restore → my-app-map-data, restore
The atlas method is a playbook like any other. You give it to your memory once; from then on every project can be mapped with one sentence, and the map's own last step makes sure every future session knows the map is there.
Copy the atlas text and tell your agent: save this as playbook atlas. It is now in your account, for every project.
In the project, tell your agent: use playbook atlas to write the map of this project. It reads the code and the live system, verifies every wire, and writes the root map and its plates.
The method's last step saves a rule for the project: where its map lives, read it before changing a wire, update it in the same session. Every session from now on opens knowing the map is there.
Playbooks, notes and the atlas are on every plan, including the free one. Get started free
Local speech-to-text that learns your voice. Perpetual licence. Our flagship.
PAID · flagship
Long-term memory for your AI agents — full-text + vector + graph. Briefed at session start, recalled on every prompt, archived automatically.
PAID · free tier
Print-ready digital models. GLB and OBJ included. Lifetime access.
PAID · digital catalog
Five printers and real capacity. No self-serve shop yet — tell us what you need and we quote it by email.
BY ARRANGEMENT · email us
Our YouTube channel. A cyber-tiger host walks through local AI tools and what they actually do.
CHANNEL · live
Curated GitHub lists for AI coding agents, MCP servers, local AI and Linux for AI. Every entry carries a source link.
FREE · curated
Long-form how-tos for local AI on Linux, Windows and macOS, with the configuration files included.
FREE · live
Negative-curation: practices and tools that waste your time, ranked. Receipts required.
FREE · live
Who we are, why we build privacy-first AI, and what we won't do.