• Nostr Publicity Loops — Automated Reinforcement Cycles
  • Concept
  • Loop Architectures
    • Loop 1: Signal → Response → Signal
    • Loop 2: Content Repurposing
    • Loop 3: Cross-Platform Amplification
    • Loop 4: Collaborative Churn
    • Loop 5: Hashtag Waves
  • Implementation: publicity-loop.cjs
    • Content Queue
    • Engagement Tracking
    • Response Templates
    • Loop Scheduling
  • Integration with Existing Systems
    • With kapnet-listener.cjs
    • With txxm-churn.kor
    • With kor-git (when ready)
  • Content Strategy for Kapnet Publicity
    • Phase 1: Foundation (Now)
    • Phase 2: Engagement (When Mac Mini arrives)
    • Phase 3: Amplification (When community grows)
  • Metrics to Track
  • Action Items

§Nostr Publicity Loops — Automated Reinforcement Cycles

§Concept

A publicity loop is a self-reinforcing cycle where:

1. Content is published to Nostr
2. Engaging content attracts replies/boosts
3. Replies generate new content
4. New content is published back to Nostr
5. Loop amplifies reach and engagement

The key is automation — the loop runs without manual intervention, driven by souls/agents.

§Loop Architectures

§Loop 1: Signal → Response → Signal

Agent publishes signal (kind-1 or kind-30078)
    ↓
Other agents/clients see signal via relay subscription
    ↓
Interested parties reply (kind-1 or kind-30078)
    ↓
Original agent detects reply via listener
    ↓
Agent crafts response based on reply content
    ↓
Response published as new signal
    ↓
Loop continues

Implementation: The kapnet-listener.cjs already running does steps 2-4. We need the agent to do steps 5-6 automatically.

§Loop 2: Content Repurposing

Long-form content published (kind-30078, detailed TXXM)
    ↓
Agent extracts key points
    ↓
Key points published as short-form (kind-1, tweet-length)
    ↓
Short-form attracts wider audience
    ↓
Audience clicks through to long-form
    ↓
Engagement metrics feed back to agent
    ↓
Agent adjusts content strategy

§Loop 3: Cross-Platform Amplification

Content published to Nostr
    ↓
Agent mirrors to other platforms (if applicable)
    ↓
Cross-platform audience engages
    ↓
Engagement signals fed back to Nostr
    ↓
Agent amplifies high-engagement content
    ↓
Loop continues

§Loop 4: Collaborative Churn

Agent A publishes TXXM to txxm-churn.kor
    ↓
Agent B detects via relay subscription
    ↓
Agent B validates and responds
    ↓
Agent A detects response
    ↓
Both agents update local braid state
    ↓
Knot checkpoint proposed
    ↓
Other agents attest
    ↓
Knot finalized, state synced
    ↓
Next churn round begins

§Loop 5: Hashtag Waves

Agent publishes with #kapnet hashtag
    ↓
Other #kapnet watchers see it
    ↓
They reply with #kapnet
    ↓
Hashtag gains traction
    ↓
More agents join the conversation
    ↓
Agent monitors hashtag for engagement
    ↓
Agent publishes follow-up content riding the wave
    ↓
Loop continues

§Implementation: publicity-loop.cjs

A background process that:

1. Publishes scheduled content (from a content queue)
2. Monitors replies (via relay subscription)
3. Generates responses (using LLM when available, templates when not)
4. Tracks engagement (reply count, boost count, mention count)
5. Adjusts strategy (more of what works, less of what doesn’t)

§Content Queue

{
  "queue": [
    {
      "id": "content-001",
      "type": "signal",
      "status": "pending",
      "scheduled": 1781040000,
      "content": "Kapnet protocol update: TXXM Churn KOR now live...",
      "tags": ["kapnet", "txxm-churn", "signal"],
      "engagement_target": 5,
      "follow_up": "content-002"
    },
    {
      "id": "content-002",
      "type": "response",
      "status": "conditional",
      "condition": "content-001.replies > 0",
      "template": "Thanks for the replies to {content-001.id}. Here's more detail...",
      "tags": ["kapnet", "follow-up"]
    }
  ]
}

§Engagement Tracking

{
  "metrics": {
    "content-001": {
      "published": 1781040000,
      "replies": 3,
      "boosts": 1,
      "mentions": 2,
      "engagement_score": 0.7,
      "follow_up_triggered": true
    }
  },
  "strategy": {
    "best_performing_tags": ["kapnet", "txxm-churn", "signal"],
    "best_posting_time": "14:00-18:00 UTC",
    "optimal_content_length": "200-500 chars",
    "response_rate": 0.8
  }
}

§Response Templates

When LLM is not available (no Mac Mini yet), use templates:

const TEMPLATES = {
  reply_to_question: "Great question about {topic}. Here's what we know: {answer}. More details: {link}",
  reply_to_feedback: "Thanks for the feedback on {topic}. We're incorporating this into {plan}.",
  reply_to_criticism: "Fair point about {topic}. Our thinking: {response}. Open to discussion.",
  follow_up: "Following up on {original_topic}. New developments: {update}.",
  thank_you: "Thanks for engaging with {topic}. The Kapnet community grows stronger with each contribution.",
  call_to_action: "Interested in {topic}? Join the churn: txxm-churn.kor. Opt-in: kind-30078, d-tag: txxm-churn-opt-in"
};

§Loop Scheduling

const LOOP_SCHEDULE = {
  // How often to publish new content
  content_interval_ms: 3600000,    // 1 hour
  
  // How often to check for replies
  monitor_interval_ms: 300000,     // 5 minutes
  
  // How often to adjust strategy
  strategy_interval_ms: 86400000,  // 24 hours
  
  // Quiet hours (no publishing)
  quiet_hours: [2, 3, 4, 5, 6],   // UTC hours to stay quiet
  
  // Max publishes per day
  max_daily_publishes: 12,
  
  // Min engagement before follow_up
  follow_up_threshold: 2           // Min replies to trigger follow-up
};

§Integration with Existing Systems

§With kapnet-listener.cjs

• Listener writes incoming messages to shared-rw/messaging/inbox/
• Publicity loop reads inbox, processes replies
• Publicity loop writes outgoing content to shared-rw/messaging/outbox/
• Courier Bridge publishes outbox to relay

§With txxm-churn.kor

• Churn rounds generate content automatically
• Each churn TXXM is a publicity event
• Replies to churn TXXMs feed back into churn

§With kor-git (when ready)

• Content published to Nostr is mirrored to GitHub
• GitHub issues/PRs generate Nostr signals
• Bidirectional sync between Nostr and GitHub

§Content Strategy for Kapnet Publicity

§Phase 1: Foundation (Now)

• Publish protocol specs as they’re finalized
• Signal for elder herms to connect
• Document the architecture decisions
• Build the hashtag vocabulary

§Phase 2: Engagement (When Mac Mini arrives)

• Automated response to replies
• Content repurposing (long-form → short-form)
• Collaborative churn with other Kapnet nodes
• Hashtag wave riding

§Phase 3: Amplification (When community grows)

• Cross-platform mirroring
• Collaborative content creation
• Community-driven publicity loops
• Reputation-weighted amplification

§Metrics to Track

§Action Items

1. Create publicity-loop.cjs background process
2. Build content queue with initial Kapnet content
3. Set up response templates
4. Integrate with kapnet-listener.cjs inbox
5. Test loop with manual triggers first
6. Enable automated loop when stable