I'm an operator, founder, consultant, and builder. I started automating operational work in the early 1990s, long before I thought of what I was doing as a particular kind of career. Since then I've built companies and products, established operating and financial systems, led enterprise change, managed a team of process improvement professionals at Level 3, worked as a solution architect and a developer, and spent eight years as CEO of a globally distributed infrastructure company.

All my education is social science. All my work is technology. The thing I'm after in both is the same: systems that transfer capacity to the people using them instead of making those people dependent.

Today I run Cirdia, where I work hands-on across software, AI systems, privacy architecture, and company operations. Much of that work is about human + AI operating models: what machines should do, where human judgment changes the outcome, and how the availability of increasingly capable AI changes the way we design companies and work.

Other companies hire me to do the same for them, start to finish: advising, implementing, and deploying. I set up a company's infrastructure, then listen and build secure, private automations around the specific needs inside the organization. I have set up US and international companies, reconstructed a company's entire financial system from every transaction, written and reviewed employee handbooks, modeled compensation plans and pro formas, and built the products and systems that run a firm's practice management. The work covers operations, compliance, law, finance, and business automation, and I do the development myself. I take on a small number of these engagements each year.

I host Terms of Service and write about technology, privacy, and the systems we build around people.

The other constant is privacy. I co-created the Cryptographic Autonomy License, build privacy-preserving infrastructure, and write and speak about the relationship between technology, personal data, and human agency.

Who is writing the prompts?

Software encodes the values of the people who write it. That has always been true. What is new is that AI now sits between us and almost every interaction we have. The systems doing the inferring are trained on a corpus that systematically underrepresents women. The prompts shaping how those systems answer are written, overwhelmingly, by people who don't know what they don't know.

So I keep asking: who is writing the prompts? Whose lived experience is the design centering? What assumptions are quietly encoded in the infrastructure we treat as neutral?

They show up in whether a wellness app stores your cycle data on a server you cannot reach. They show up in whether a wearable returns your data to you or sells it to an advertiser. They show up in whether AI talks down to women about their own bodies because the corpus it learned from did.

What I do about it is build new application layers around this technology that has flaws, and write my own prompts differently than what I believe most people do. One question under all of it is: *who shall we be as people in this new age of AI*. That is what someting I explore in my essays, and it is one I would take into think tanks, companies, and policy rooms if asked.