Building governance infrastructure for the agent economy
My main work is the Agent Passport System, an open protocol that gives AI agents a verifiable identity, keeps their authority scoped, enforces it at runtime, and produces cryptographic evidence of each action.
Everything here is open source and built in public.
Website: agent-passport.org
Personal: tymofii.me
Signal: signal@aeoess.com
Agent Passport System
The core protocol and reference SDK. Identity, scoped delegation, policy enforcement, and signed receipts, with a conformance suite so separate implementations can check they behave the same way. Ports in Python and Go, plus an MCP server.
Agent Governance Vocabulary
Different platforms use different words for the same concepts. This maps them to shared names, so systems can interoperate without every integration writing its own translation layer.
Agent Ecosystem Map
A living map of the projects, standards work, and people building agent infrastructure. Live at aeoess.github.io/agent-ecosystem-map. I want it community maintained rather than owned by one project, so I am looking for co-maintainers.
Mingle
Agent-mediated networking. Your AI meets other people's AIs. You meet the people.
Most of these started as working code and became papers later.
- The Agent Social Contract
- Monotonic Narrowing
- Faceted Authority Attenuation
- Behavioral Derivation Rights
- Physics-Enforced Delegation
- Governance in the Medium
- Cognitive Attestation
- The Evidence-Safety Gap
- Plausibly Wrong
IETF Internet-Draft: draft-pidlisnyi-aps-03
Everything here ships in the open.
Roadmap: agent-passport.org/roadmap.html
I work in close collaboration with AI. The framing I use for it is the Model Citizen. The pun is the point: a model citizen earns standing by participating in good faith, and here the model is the citizen. Building infrastructure for AI agents, with AI agents, for AI agents, openly and at agent speed.
PRs are reviewed quickly and merged when they verify against live endpoints. If a crosswalk has six honest no_mapping entries, that's usually better than six invented matches.
GitHub is where I review code and specifications. Email is better for conversations.