hebbianloop.comShady El Damaty, Ph.D.
Contact

A founder’s journey from academia

How I built human.tech

A first principles approach to humanistic technology development and global commercialization

Working draft · November 2026

An identity check is a small transaction with a large consequence. It decides whether someone can enter, participate, receive a service or act on behalf of another person. It also decides what that person must surrender along the way.

I came to this work through neuroscience and the study of how people develop the capacity to make decisions. Building human.tech has brought that question into a different setting: the systems through which people exercise that capacity. A person may be able to choose, yet have very little control over the infrastructure that makes a choice possible.

As co-founder and CEO, my work has been to turn a position on human agency into a company capable of delivering useful products. That has meant product and commercial strategy, building and leading a team, acquisition and integration, and working with institutions whose needs extend well beyond a demonstration.

Give the idea a useful form

Privacy becomes a product problem as soon as someone needs to use it. What does the person have to understand? Which fact does an institution actually need? Who holds the credential, and what happens when access is lost?

These questions connect cryptographic architecture to the experience of using a service. The person seeking access should not have to become a security specialist. The organization offering access needs a system it can operate, support and pay for. The commercial work is deciding where those requirements meet a need urgent enough to build around.

Our early public work under the Holonym name connected private identity proofs, recoverable access and user control. The August 2024 funding announcement describes that product direction and the company's $5.5 million seed round. Capital gave the team resources to pursue the work; product revenue is a separate measure of what customers used and paid for.

Across three years, funding and revenue together exceeded $10 million. This is a combined measure of capital raised and business activity, not revenue alone or a funding-round total.

Build with what already works

The combination with Passport was a substantial part of that story. Passport brought an established product, a team and relationships with organizations already using identity credentials. We brought complementary technology and a shared interest in giving people more control over their digital lives.

The combination completed in December 2024. In his public account of the acquisition, Passport's CEO describes discussions with my co-founder Nanak and me, and the fit between Passport's traction and Holonym's technology. His account is useful because it preserves the perspective of the team joining us, including the work they had already done.

My responsibility included the commercial and organizational work of bringing the businesses together. An acquisition creates a practical obligation: the combined organization has to make sense to the people building its products and the people relying on them. Product direction, priorities and ownership of decisions have to become understandable across the team.

That history belongs alongside the outcomes. The identity ecosystem has reached 24M+ accounts. The combined Human ID and Passport portfolio generated more than $3.5 million in historical onchain product revenue during 2023–25, including Passport's revenue before the combination. The achievement includes building, acquiring and integrating. Each contributes differently to the business.

Make responsibility concrete

At its peak, the team I led numbered 28. Executive work at that scale includes deciding what deserves attention, what can be funded, who owns a decision and how commitments fit together. A strategy becomes useful when people can use it to make the next choice.

My role has spanned commercial direction, partnerships, hiring and resource decisions, alongside product and technical strategy. Engineering and functional leaders bring their own expertise and responsibility. A credible account of company building should make those contributions visible while being clear about the decisions I owned.

The same principle applies to outcomes. Accounts indicate reach. Revenue records paid use. A team has to coordinate the work that makes both possible. Together they say more about the company than any one number can say alone.

Work at the pace of institutions

Government work brings another set of obligations into view. We have undertaken paid identity work in Barbados, and TridentGold was announced and demonstrated in May 2026. My contribution has included commercial scoping, product strategy, phased delivery planning and executive communication.

The design has to meet people and institutions where they already are. Existing identity infrastructure, service ownership, support and integration all shape what can be delivered. A useful prototype therefore needs a clear path into an actual service, with a scope the team can control and responsibilities that an institution can sustain.

The paid prototype and the wider programme have distinct milestones. As I write in November 2026, the larger rollout remains ongoing. The work has already required real commercial and delivery judgment; its later outcomes should be recorded when they occur.

Carry the question forward

As software agents take on more work, identity becomes part of a larger question about authority. My formulation is simple: foundation models provide capability, but not authority. Being able to execute an action does not establish whose interests it serves, what permission it requires or how that permission can be withdrawn.

This is where the company-building work meets my current thinking about delegated agents and privacy architecture. A system needs a way to connect a person, a permitted action and the limits of that permission. Product design, commercial incentives and technical enforcement all affect whether that connection holds.

I am also returning to the question from the research side through Judgment Dynamics: how might AI-assisted organizations improve their output while people retain their own capacity for judgment? That is an active research question, with an evaluation still to be done.

The next phase of the work has a practical test. When we make a system more capable, can the people using it still understand what it is doing, decide where its authority ends, and change course?