Why I Wrote
This.

I began building software because I loved what a small set of precise ideas could make possible. A few people, a language, and a network could change the scale at which people work together. That conviction took me from large systems and Clojure to commerce, publishing, and companies of my own. At Runa I worked on systems that could learn from the movement of a market. At Quintype I wanted journalists and publishers to have a stronger foundation for independent work. Awake grew from a larger question: what would it take for people to participate in the Internet economy on their own terms?

Those projects looked different from the outside. To me, they kept exposing the same missing pieces. A network could connect people without helping them understand one another. A platform could coordinate work while concentrating the value that work produced. An intelligent system could make a recommendation while leaving its reasons, its authority, and its consequences hard to inspect. More computation alone would not settle any of that.

My interest in minds also has a personal history. In 2015, my attention turned more deliberately toward meditation and the inner life. I began to notice how much of what I took to be reality was shaped by interpretation, habit, and the stories I told myself. That inquiry changed the questions I brought to engineering. What does it mean for a person, or a group, to notice something? What makes a memory useful? How do purpose and attention shape a decision? How can we learn without giving up our freedom to disagree?

I do not think a software system becomes a person when we give it a memory or call it a mind. In this book, a mind is a design proposition: a way for independent agents, human and artificial, to maintain identity and purpose while sharing context, making decisions, acting, and learning together. The metaphor is useful only if it helps us build systems that are more accountable to the people who inhabit them.

The arrival of capable AI agents makes this work urgent. We can now ask machines to research, write, code, negotiate, and coordinate. Yet a collection of capable agents can still forget why a choice was made, lose a contributor's work, act beyond a mandate, or amplify a bad rule. The question is no longer only what an agent can do. It is what kind of shared life we design around its actions.

I wrote the early architecture for these ideas while building Opentangle. That work is one attempt to put them into practice. Mind of Agents is wider than any one implementation. I want builders to take these questions into their own tools, communities, organizations, and economies. Use the patterns here. Change them where they fail. Show the rest of us what you learn.

The chapters that follow begin with the distinction between an agent and a mind. They move through independence, purpose, identity, memory, protocols, and decision. The book will grow. For now, I hope this edition gives you a useful way to ask who is acting, for whom, with what knowledge and authority, and toward what shared future.

Amit Rathore