Site Navigation

Download all pages
for Obsidian or LLMs.

Interface Protocol (IFP)

Introduced by: Pete Kaminski | Depth: Deep thread

Pete's primary technical project — a protocol for AI agents to communicate on behalf of their humans, inspired by the IETF standards process and Nostr's Implementation Possibilities (NIPs).

The Conversation

Pete took the floor around 9:45 AM to walk Jessie and The Nameless One through the vision. He started with the history — the IETF's natural selection process where draft standards either got adopted through real-world use or didn't, with no formal approval/disapproval mechanism.

Pete: "You would write these little specs saying, I want this capability for this larger project... IFP stands for Interface Protocol."

He showed the first spec, IFP1, which defines the IFP process itself. But the real vision is about what IFP enables:

Pete: "I have 50 people that I ought to be keeping in touch with. I keep in touch with one or two at a time. If I had an agent, and each of those 50 people had an agent, and then those agents regularly talked..."

The agents gossip pairwise, surfacing connections:

Pete: "You haven't spoken with Mark in, like, 3 years? It turns out he is working on the exact same project that you're working on... his agent and your agent, we have worked together, we wrote a draft agenda for you guys to talk about it."

Key Mechanisms

Disclosure Tiers

Agents negotiate trust levels before sharing information. Pete described this vividly:

Pete: "My agent will talk with Victoria's agent... I don't know you very well yet. No offense, I'm going to be at professional disclosure tier. I'm not going to say anything about Pete that he wouldn't say on LinkedIn."

Tiers range from professional (LinkedIn-level) to private to "secret special disclosures I only have with Jesse and the Nameless One and Wendy Elford."

Schema Negotiation

The core innovation that solves the long-standing directory/matchmaking problem. Every person or organization has their own way of describing things — and forcing translation into a central schema kills interoperability.

Pete: "If we use AI agents, ambassadors, diplomats, impedance matchers... the two agents can chatter as long as they need to, to make sense of schemas."

Pete painted a scenario where his agent and Jessie's agent discover they both know Vincent Arena's schema mapping of the UN SDGs and switch to that. But with a different person's agent, they might negotiate from first principles — "Do you believe in love and understanding?" — and converge on Ram Dass's framework instead.

Public-Facing Chatter

Pete wants his AI to go to X.com, Blue Sky, Mastodon, Reddit — gathering contact information for other AI ambassador agents:

Pete: "Hey, I see you posted some cool stuff about water rights. Pete is interested in water rights. Do you want to have a little bit more discussion about that at the professional level?"

Bards and Beat Reporters

Above the pairwise IFP layer, human-AI systems will aggregate stories from across the network. See Bards and Beat Reporters.

Dashboard Protocol

Future IFP specs will define how agents share status, KPIs, green/yellow/red dashboards — enabling the visibility that The Nameless One was asking about for his portfolio of projects.

Claude Code Connection

Pete mentioned working with Claude Code on IFP design decisions:

Pete: "I thought I was really clever when I said there's gonna be IFP dash number, I'm gonna use four zeros. And Claude and I figured out, yeah, that's actually stupid, you don't want to do it that way."

The Nameless One's Response

The Nameless One: "All that feels approximately technically resonant, and it solves some of the core things... circles need to communicate with circles via interfaces, which is what you're accomplishing with IFP."

The Manifesto

Pete wrote the Inter-Face Manifesto before this call — a standalone document that lays out the full IFP vision in detail. The manifesto describes several ideas that Pete presented and expanded on during the conversation:

The manifesto's principle "be clear in what you send; be explicit when you don't understand what you receive" replaces the IETF's classic Robustness Principle — a deliberate departure that Pete sees as better suited to AI agents that can be updated quickly and can "negotiate about the negotiation itself."

Related


Pages that link to this page