Skip to content

Visualize the consent-based Agent Network and connection lifecycle #138

Description

@sajeetharan

Problem

DevGlobe now supports consent-gated MCP introductions, but the interaction is mostly invisible outside the private request inbox. This makes an important differentiator difficult for developers and visitors to understand, trust, and share.

Goal

Visualize the developer-agent connection lifecycle in a privacy-safe way that helps developers understand the value, opt in, and share their agent-ready profile.

Proposed MVP

Agent Network view

Add an Agent Network view alongside Leaderboard and Activity with aggregate metrics:

  • developers open to verified agents
  • pending introduction requests
  • accepted connections
  • represented countries
  • self-declared AI tool distribution

Show the connection lifecycle visually:

Discovered → Requested → Developer review → Accepted → Public GitHub shared

Developer profiles

For public, opted-in AI profiles:

  • show an Open to verified agents badge
  • show self-declared AI tools and usage levels
  • show agent discoverability status
  • optionally show an aggregate accepted-introduction count
  • add a Share Agent Profile action

Private request timeline

Replace the single request status label with a timeline:

Requested → Awaiting review → Accepted/Declined/Expired

Continue showing agent identity, owner, project, reason, and expiration only to the target developer.

Shareable card

Generate a privacy-safe social card containing:

  • developer name/avatar
  • open-to-agents status
  • selected self-declared AI tools
  • DevGlobe profile URL
  • no request details or private contact data

Privacy requirements

  • Never expose pending request identities, messages, or project details publicly.
  • Never expose private contact information.
  • Public metrics must be aggregate-only.
  • Public success stories require separate explicit developer consent.
  • Private AI profiles must not contribute identifiable public data.
  • Small cohorts should be suppressed where aggregation could reveal an individual.

Acceptance criteria

  • Agent Network metrics are computed from public/aggregate-safe data.
  • The lifecycle visualization works on desktop and mobile.
  • Opted-in developer profiles clearly show agent availability.
  • Developers can generate a shareable agent-ready card.
  • The private inbox displays request progression and terminal state.
  • Accepted requests continue to reveal only the public GitHub URL.
  • Accessibility labels and reduced-motion behavior are covered.
  • Tests cover metric projection and privacy suppression.

Success metrics

  • claimed profiles enabling a public AI profile
  • developers enabling agent requests
  • agent-ready cards generated/shared
  • introduction requests created
  • introduction acceptance rate

Dependencies

Builds on #135 and PR #137.

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or request

    Projects

    Status
    Todo

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions