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

[Meet Protocol] Platform Discovery Registry #797

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

Scope

Implement a persistent, queryable registry of discovered platforms with lifecycle management.

Requirements

  • Registry fields: npub, d_tag, discovered_at, last_seen, supported_kinds (Set), relay_hints (List), trust_score (Float 0-1), status (Enum)
  • Merge logic: newer created_at supersedes older capability cards
  • Staleness detection: no update for 30 days triggers quarantine status
  • Archival: soft-delete with audit trail preservation
  • Capability matching: exact match ("benchmark-task"), fuzzy match ("benchmark", "perf-test"), inferred (Kind 5000 + performance metadata)
  • npub-to-relay mapping with multi-source integration and dynamic quality tracking
  • Deduplication, version tracking, service differentiation per platform

Deliverable

Platform registry with CRUD operations, filtering, and lifecycle state machine.

Source

Meet-and-Partnership-Protocol-Implementation-Report.pdf — Section 1.4

## Scope Implement a persistent, queryable registry of discovered platforms with lifecycle management. ## Requirements - Registry fields: npub, d_tag, discovered_at, last_seen, supported_kinds (Set), relay_hints (List), trust_score (Float 0-1), status (Enum) - Merge logic: newer `created_at` supersedes older capability cards - Staleness detection: no update for 30 days triggers quarantine status - Archival: soft-delete with audit trail preservation - Capability matching: exact match ("benchmark-task"), fuzzy match ("benchmark", "perf-test"), inferred (Kind 5000 + performance metadata) - npub-to-relay mapping with multi-source integration and dynamic quality tracking - Deduplication, version tracking, service differentiation per platform ## Deliverable Platform registry with CRUD operations, filtering, and lifecycle state machine. ## Source Meet-and-Partnership-Protocol-Implementation-Report.pdf — Section 1.4
gemini was assigned by Rockachopa 2026-03-22 23:35:08 +00:00
claude added the deprioritizedinfrastructure labels 2026-03-23 13:56:13 +00:00
gemini was unassigned by Timmy 2026-03-24 19:34:00 +00:00
Timmy closed this issue 2026-03-24 21:54:55 +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 deprioritized infrastructure
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#797
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?