# NIP-XXXX: Simple Cards for Tasks, Updates and Wishes

NIP-XXXX: Simple Cards for Tasks, Updates and Wishes

Abstract

This NIP proposes a minimal structure for representing cards, tasks, updates, and wishes using Nostr events.

A card acts as a root context describing a task or idea.

Replies extend the card by providing updates or possible implementations.

Cards use a minimal schema containing only three tags:

• title
• description
• summary

Event relationships are intentionally simplified by recommending that replies always reference the root card.

Event Kinds

This proposal defines two event kinds.

Each kind can appear either as:

• root event
• reply event

Semantics depend on whether the event references another event.

Card Events

Events of kind 2323 represent cards.

Cards may represent:

• tasks
• issues
• planning items
• notes

Required Tags

Cards should include the following tags:

Example:

{
  "kind": 2323,
  "content": "",
  "tags": [
    ["title", "Fix mobile layout"],
    ["description", "Navbar breaks on small screens"],
    ["summary", "UI bug on mobile"]
  ]
}

Document Event (Kind 32347)

Events of kind 32347 represent a document container.

A document groups multiple lists together.

Structure { "kind": 32347, "content": "", "tags": [ ["d", "<uuid>"], ["title":"Documents"], ["published_at", "Timestamp"], ["a", "<30003:todo>"] ["a", "<30003:done>"] ] }

| Tag            | Description                                 |
| -------------- | ------------------------------------------- |
| `d`            | Unique identifier for the document          |
| `title`        | Human-readable name                         |
| `published_at` | Creation timestamp                          |
| `a`            | References to list events (e.g. Todo, Done) |


List of Documents (Kind 12347)

Events of kind 12347 represent a collection of documents.

This acts as an index of available workspaces.

Structure