Rockachopa/Timmy-time-dashboard
1
0
Fork 2
Code Issues 7 Pull Requests Actions Packages Projects Releases Wiki Activity

[EPIC] Meet & Partnership Protocol — NIP-89/NIP-90 Agent Discovery & Benchmarking #794

New Issue
Closed
opened 2026-03-21 21:51:52 +00:00 by perplexity · 0 comments
perplexity commented 2026-03-21 21:51:52 +00:00
Collaborator
Copy Link

Overview

Implement the "Meet and Partnership" protocol enabling Timmy to discover, evaluate, and establish partnerships with other AI agents/platforms on the Nostr network using NIP-89 (Capability Cards) and NIP-90 (Data Vending Machine) protocols.

Source Document

Meet-and-Partnership-Protocol-Implementation-Report.pdf (28 pages, generated by Kimi.ai)

Key Concepts

  • NIP-89: Decentralized service discovery via Kind 31990 "Capability Card" events
  • NIP-90: Job delegation via Kind 5000-5999 requests and Kind 6000-6999 results
  • Kind 7000: Feedback/status events for job progress tracking
  • Trust scoring: Dynamic trust model based on benchmark outcomes
  • Lightning payments: Sats-based bidding for benchmark and production jobs

Architecture

  1. Discovery — Subscribe to relays, monitor Kind 31990 events, maintain platform registry
  2. Meet — Send NIP-90 benchmark job requests (Kind 5000) to discovered platforms
  3. Evaluate — Parse benchmark results, score platforms on trust metrics
  4. Partner — Establish ongoing partnerships with high-trust platforms

Sub-Issues

See linked issues below for implementation scope.

Linked Sub-Issues

  • #795 — [Meet Protocol] NIP-89 Relay Subscription Manager
  • #796 — [Meet Protocol] Capability Card Parser & Validator
  • #797 — [Meet Protocol] Platform Discovery Registry
  • #798 — [Meet Protocol] NIP-90 Benchmark Job Request Builder
  • #799 — [Meet Protocol] Benchmark Result Processor & Trust Scoring
  • #800 — [Meet Protocol] Lightning Payment Integration for Job Bidding
## Overview Implement the "Meet and Partnership" protocol enabling Timmy to discover, evaluate, and establish partnerships with other AI agents/platforms on the Nostr network using NIP-89 (Capability Cards) and NIP-90 (Data Vending Machine) protocols. ## Source Document `Meet-and-Partnership-Protocol-Implementation-Report.pdf` (28 pages, generated by Kimi.ai) ## Key Concepts - **NIP-89**: Decentralized service discovery via Kind 31990 "Capability Card" events - **NIP-90**: Job delegation via Kind 5000-5999 requests and Kind 6000-6999 results - **Kind 7000**: Feedback/status events for job progress tracking - **Trust scoring**: Dynamic trust model based on benchmark outcomes - **Lightning payments**: Sats-based bidding for benchmark and production jobs ## Architecture 1. **Discovery** — Subscribe to relays, monitor Kind 31990 events, maintain platform registry 2. **Meet** — Send NIP-90 benchmark job requests (Kind 5000) to discovered platforms 3. **Evaluate** — Parse benchmark results, score platforms on trust metrics 4. **Partner** — Establish ongoing partnerships with high-trust platforms ## Sub-Issues See linked issues below for implementation scope. ## Linked Sub-Issues - #795 — [Meet Protocol] NIP-89 Relay Subscription Manager - #796 — [Meet Protocol] Capability Card Parser & Validator - #797 — [Meet Protocol] Platform Discovery Registry - #798 — [Meet Protocol] NIP-90 Benchmark Job Request Builder - #799 — [Meet Protocol] Benchmark Result Processor & Trust Scoring - #800 — [Meet Protocol] Lightning Payment Integration for Job Bidding
claude was assigned by Rockachopa 2026-03-22 23:35:10 +00:00
claude added the harnessp1-importantsovereignty labels 2026-03-23 13:54:16 +00:00
claude was unassigned by Timmy 2026-03-24 19:34:01 +00:00
Timmy closed this issue 2026-03-24 21:54:56 +00:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
222-epic
Workshop: Timmy as Presence (Epic #222)
 actionable
Has a concrete code/config task extracted
 assigned-claude
Issue currently assigned to Claude agent — do not assign to another agent
 assigned-gemini
Issue currently assigned to Gemini agent — do not assign to another agent
 assigned-groq
assigned-kimi
Issue currently assigned to Kimi agent — do not assign to another agent
 assigned-manus
Issue currently assigned to Manus agent — do not assign to another agent
 claude-ready
consolidation
Part of a consolidation epic
 deprioritized
Keep open but not blocking P0 work
 deprioritized
Keep open but not blocking P0 work
 duplicate
Duplicate of another issue
 gemini-review
Auto-generated by Gemini, needs relevance review
 groq-ready
harness
Core product: agent framework, heartbeat, inference, memory
 heartbeat
Harness: Agent heartbeat loop
 inference
Harness: Inference and model routing
 infrastructure
Supporting stage: dashboard, CI/CD, deployment, DNS
 kimi-ready
Scoped and ready for Kimi to pick up
 memory-session
Harness: Memory and session crystallization
 morrowind
Harness: Morrowind embodiment
 needs-design
Needs architectural design before implementation
 needs-extraction
Philosophy with unextracted engineering work
 p0-critical
Priority 0: Must fix now
 p1-important
Priority 1: Important, next sprint
 p2-backlog
Priority 2: Backlog, do when time permits
 philosophy
Philosophical foundation — informs architecture decisions
 rejected-direction
Closed: rejected or superseded direction
 seed:know-purpose
Three Seeds: KNOW YOUR PURPOSE
 seed:serve-real
Three Seeds: SERVE THE REAL
 seed:tell-truth
Three Seeds: TELL THE TRUTH
 sovereignty
Harness: Sovereignty stack
No Label harness p1-important sovereignty
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
Timmy claude grok groq kimi manus perplexity Rockachopa
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: Rockachopa/Timmy-time-dashboard#794
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?