The origin story: a founder's note
A few months ago my older sister called me. Her insurance broker had emailed her a settlement letter she had never agreed to. The email was signed "your AI agent on file" — an agent the broker had quietly enrolled her in to "speed up paperwork." She had no record of authorizing it. The signature was real; the authority was fictional. I spent that weekend reading IAM literature and realized the gap she had encountered was not a bug. It was the design.
The week after
I made a list. Every system my sister had touched in the prior six months that might have run an AI agent on her behalf. Forty-three. The number was inflated by the kind of things that did not really need an agent (her grocery delivery's "smart" reorder), but the spreadsheet still showed nineteen real agent-authored actions across nine vendors that she had not knowingly authorized.
Each of those nineteen actions traced to the same legal-and-architectural pattern: a service account, named for a department, holding a credential that named no human. The vendors were not malicious; they were efficient. The system did not care about my sister's signature; the system cared about throughput.
The phone call
I called Anjali, who I had worked with twice before, and described the gap. We talked for two hours. By the end of the call we had drafted what would become the seven-layer reference architecture — on a napkin, then on a Google Doc, then on a whiteboard at her kitchen table the next weekend. The draft did not have a name; we had been calling it "the human layer." Two weeks later, while reading Sankhya commentaries — Anjali's father is a Sanskrit scholar — we came across the word Manav. The hairs on the back of my neck did the thing.
The decision to build a protocol
It would have been easier to build a product. We had two near-paths to a fast launch: a Chrome extension that warned users when an agent was acting on their behalf without consent; a SaaS that wrapped existing IAM tools with audit logs naming the human in the loop. Both would have shipped in three months. Neither would have outlived their first compliance regulation.
The hard path — and the one we chose — was a protocol that survived the products on top of it. Open-source, with a hosted commercial layer for operations, governed by a foundation eventually. The opposite of fast. The only way to build a layer of trust that does not become a single point of failure.
What we got wrong already
Two early decisions we have since revisited. We started with a Solidity-first design because we assumed the chain would be central; we have since moved most of the protocol off-chain, with on-chain anchoring for audit. We also under-invested in developer experience for the first six months; we corrected, and the SDKs are now the part of the project we are most proud of.
What we got right early
Two decisions, both costly to live with at the time. We refused early acquisition interest from a major identity vendor; the offer was generous, the terms would have ended the protocol's open-source posture before it shipped. We also chose Bengaluru over San Francisco for incorporation; the cultural and labor-cost arguments were obvious, the tax-and-investor-relations cost was painful and worth it.
What my sister thinks now
She has a Manav DID and uses it weekly. She still gets emails her agent did not authorize, but the wallet now flags them and she ignores them. The settlement letter is framed in our office, with the words "the gap was the design" written on a sticky note below it.
Common objections
Two objections worth answering. Stated values do not survive growth pressure — true historically, which is why we put structural mechanisms (open-source, governance, protocol-enforced custody) behind the words rather than just the words. This sounds like marketing — the test will be the audit hashes, the protocol design, and the operating agreements, not the prose.
Frequently asked questions
What does this commitment cost us if we honor it? Real money in the years where the temptation would have been highest. We are pricing it in upfront because the commitment is structural, not aspirational.
Where do we publish this commitment? Here, on the protocol governance page, and in the operating agreements with our investors. Anyone can audit whether the commitment is being kept by reading the audit hashes we publish quarterly.
What if leadership changes? The commitment is structural enough that a new leadership cannot quietly reverse it. The protocol mechanics make the breach detectable; the legal commitments add a second layer; the cultural commitments add a third.
Where to start
For the wider posture, read manav manifesto and why manav sanskrit. The values, the protocol, and the operating model only fit together when read in that order.
Every category-defining company has an origin story. Ours is a phone call from a sister who deserved better infrastructure than the one we had built her.