A blueprint describes a system you build with an agent. Give it the document, then work through questions together to adapt the design to your goals, tools and context.
Your wiki, built and kept current by an agent: notes link themselves, and knowledge doesn't get lost in chats.
Several agents argue and converge on a decision — a council instead of a single assistant. The roles, the rules, and how to launch it.
Write in Obsidian — it lands on your site. The vault as the source, git as the pipe, no manual layout or copy-paste.
HQ on a strong model, workers priced to the task, every role written once and run on any engine: how one person runs an AI team through files instead of chats.
Your own Telegram as the agent's memory and hands: a local index of your correspondence, search over MCP, sending only after your ✅, and a pocket entrance to the agent from your phone. The data stays on your machine.
How to talk to an LLM: context, the four levels, your own context file, and ten prompt patterns. 39 pages — from zero to a working system in one evening.