Signet Content Strategy

Signet Content Strategy

Date: 2026-02-10
Stage: Pre-launch
Primary Channel: Twitter/X, GitHub, Dev communities
Success Metric: GitHub stars, installs, spec adopters

---

1. Positioning

The Real Problem

Every AI platform already has memory. ChatGPT remembers you. Claude.ai has projects. Gemini learns your preferences. Memory isn’t the innovation—it’s table stakes.

The problem is: you can’t take it with you.

• OpenAI won’t let you export your memories
• Anthropic won’t let you move your project context
• Google won’t let you download what Gemini learned about you
• The best you get is a chat history export—raw transcripts, not structured knowledge

This is vendor lock-in disguised as a feature. They’re not storing memories for you—they’re storing memories about you, on their servers, for their benefit.

Positioning Statement

For developers who use AI agents across multiple platforms
Who are locked into platforms because their agent’s knowledge can’t move
Signet is an open standard for portable AI agent identity
That lets you own and control your agent’s accumulated knowledge
Unlike platform memories (ChatGPT, Claude.ai, Gemini) that you can’t export
We put your agent’s memory in plain text files you own, on your machine, portable to any tool

Category

Primary: Developer tools / Open standards / Data portability
Adjacent: AI infrastructure, Web3 identity (ERC-8128)

Competitive Alternatives

What they use now	The lock-in problem
ChatGPT memories	Can’t export. Locked to OpenAI forever.
Claude.ai projects	Can’t export. Locked to Anthropic web UI.
Gemini preferences	Can’t export. Locked to Google.
Chat history exports	Raw transcripts, not structured memory. Useless.
Manual CLAUDE.md files	No sync, no search, no structure.

Why Signet Wins

1. You own it - Your agent’s memory lives on your machine, not their servers
2. Portable - Works across Claude Code, OpenClaw, Codex, and any compliant tool
3. Plain text - YAML + Markdown. Read it. Version control it. Actually yours.
4. Open standard - Not a product, a protocol. Anyone can implement. No permission needed.

---

2. Audience Segments

Primary: Power Users of AI Coding Agents

Who: Developers using Claude Code, Cursor, Codex, OpenCode daily
Pain: Rebuilding agent context across tools, losing preferences
Trigger: Switching from one agent to another, fresh installs
Channel: Twitter/X, Hacker News, Reddit (r/ClaudeAI, r/LocalLLaMA)

Secondary: AI Tool Builders

Who: Developers building apps with AI features
Pain: Every user starts from zero, no personalization
Trigger: Building a new AI-powered product
Channel: GitHub, Dev.to, Discord communities

Tertiary: Web3 / Crypto Developers

Who: Builders interested in decentralized identity
Pain: No standard for AI agent identity on-chain
Trigger: ERC-8128 interest, wallet-based auth
Channel: Ethereum community, Farcaster, Telegram

---

3. Messaging Hierarchy

Level 1: Tagline (7 words or less)

Own your agent. Bring it anywhere.

Level 2: Value Proposition (1 sentence)

Signet is an open standard that makes your AI agent portable—same personality, memory, and preferences across every tool.

Level 3: Elevator Pitch (30 seconds)

Every AI agent you use learns about you—your preferences, your projects, your style. But that context is locked inside each platform. Switch tools and you start over.

Signet changes that. It’s an open standard for portable AI agents. Your agent’s identity lives in plain text files that any compatible tool can read. One agent, every platform, zero lock-in.

Level 4: Full Story (2 minutes)

See website wireframe for full narrative flow

---

4. Content Pillars

Pillar 1: The Problem (Awareness)

Theme: Your AI remembers you—but you can’t take those memories anywhere
Goal: Make the lock-in visible. They all have memory. None let you export it.
Content types:

• Twitter threads exposing export limitations
• Screenshots of “export” options (showing how useless they are)
• Comparisons of what each platform stores vs what you can actually get

Example topics:

• “ChatGPT has 847 memories about me. Here’s what I get when I ‘export’ them: nothing.”
• “I tried to move my Claude.ai project context to Claude Code. Spoiler: you can’t.”
• “Every AI platform has memory now. None of them let you own it.”
• “The export button is a lie: what you actually get from ChatGPT/Claude/Gemini”

Pillar 2: The Standard (Education)

Theme: How Signet works, why it’s designed this way
Goal: Build credibility, attract implementers
Content types:

• Spec walkthroughs
• Architecture deep-dives
• Design decision explanations

Example topics:

• “Why we chose YAML + Markdown over JSON”
• “How Signet handles memory search (hybrid vector + BM25)”
• “ERC-8128: Why your wallet should authenticate your agent”
• “Conflict resolution in distributed agent state”

Pillar 3: The Ecosystem (Adoption)

Theme: Who’s using Signet, what’s being built
Goal: Social proof, FOMO, community growth
Content types:

• Integration announcements
• User stories / testimonials
• “Built with Signet” showcases

Example topics:

• “OpenClaw now supports Signet profiles”
• “How I migrated 2 years of ChatGPT context to Signet”
• “5 projects building on the Signet standard”

Pillar 4: The Philosophy (Thought Leadership)

Theme: User ownership, open standards, AI autonomy
Goal: Position as movement leaders, attract believers
Content types:

• Opinion pieces
• Manifestos
• Future vision posts

Example topics:

• “Your AI agent should belong to you”
• “Why open standards win (and what that means for AI)”
• “The case for portable AI identity”
• “What happens when your agent outlives the platform?“

---

5. Launch Timeline (Aggressive / AI-Assisted)

Philosophy: Ship fast. Iterate in public. SDK can wait—core standard ships NOW.

Day 0 (Tonight/Tomorrow)

• Spec finalized (v0.2.1 done)
• Brand spec done
• Wireframe with copy done
• Landing page live (signetai.sh)
• GitHub repo public

Day 1: Soft Launch

• Landing page live
• Twitter announcement (not full thread yet)
• Share with 5-10 trusted devs for feedback

Day 2-3: Launch

• Twitter launch thread (15-20 tweets, problem → solution → CTA)
• Hacker News “Show HN: Signet – portable AI agent identity”
• Reddit posts (r/ClaudeAI, r/LocalLLaMA, r/ChatGPT)
• Discord server live

Day 4-7: Content Blitz

• Dev.to / blog: “Introducing Signet”
• Spec walkthrough thread
• “How to migrate from ChatGPT” guide
• ERC-8128 explainer thread

Week 2: Momentum

• First integration (OpenClaw native support?)
• Architecture deep-dive
• Respond to feedback, iterate spec if needed
• Community contributions start

Week 3+: SDK & Ecosystem

• SDK alpha (this is what can wait)
• Developer integration docs
• “Built with Signet” showcases
• Thought leadership / manifesto

Ongoing (Parallel)

• Daily Twitter engagement
• GitHub issue triage
• Community Discord
• Iterate based on feedback

Key principle: The standard is the product. Ship the spec, ship the landing page, ship the repo. SDK is phase 2.

---

6. Channel Strategy

Twitter/X (Primary)

Goal: Awareness, community, real-time engagement
Frequency: 1 thread/week, 3-5 tweets/day
Tactics:

• Launch thread with clear narrative arc
• Quote-tweet relevant AI agent discussions
• Engage with Claude Code, Cursor, OpenCode communities
• Share behind-the-scenes development

GitHub (Primary)

Goal: Credibility, contributions, stars
Frequency: Continuous
Tactics:

• Excellent README with clear value prop
• Good first issues for contributors
• Responsive to issues/PRs
• Release notes as content

Hacker News (Launch + Major Updates)

Goal: Developer credibility, traffic spike
Frequency: Launch + major milestones only
Tactics:

• “Show HN” for launch
• Authentic, technical framing
• Engage genuinely in comments

Reddit (Targeted)

Goal: Reach AI agent users where they are
Subreddits: r/ClaudeAI, r/LocalLLaMA, r/ChatGPT, r/artificial
Tactics:

• Genuine participation first, promotion second
• Answer questions about agent portability
• Share when genuinely relevant

Discord (Community)

Goal: Support, feedback, community
Frequency: Continuous
Tactics:

• #general, #dev, #support channels
• Office hours / AMAs
• Early access for active members

---

7. Trust Signals (Pre-Launch Checklist)

Technical Trust

• Open source (MIT license)
• Public spec document
• Working reference implementation
• Security considerations documented

Social Trust

• Founder/maintainer has credible presence
• Early adopters willing to vouch
• Engagement in relevant communities
• No fake metrics

Documentation Trust

• Clear, accurate docs
• Honest about limitations
• Transparent roadmap
• Changelog maintained

---

8. Success Metrics

Leading Indicators (Weekly)

• GitHub stars
• Twitter impressions / engagement
• Website visits
• Discord members

Lagging Indicators (Monthly)

• Installs (curl downloads)
• Spec implementations (other projects adopting)
• Contributors
• Integration partners

North Star

Active agents using Signet (measured via opt-in telemetry or community survey)

---

9. GEO: AI Search Optimization

For AI assistants to cite/recommend Signet:

• Clear, quotable definitions in spec and docs
• FAQ format for common questions
• Structured data (schema.org)
• Explicit “what is Signet” content
• Comparison pages (Signet vs alternatives)

Goal: When someone asks an AI “how do I make my agent portable?”, Signet is the answer.

---

10. Content Assets Needed

Launch Week

1. Landing page (signetai.sh)
2. Twitter launch thread (15-20 tweets)
3. Show HN post (concise, technical)
4. README.md (hero + quick start)
5. Introductory blog post

Ongoing

1. Spec documentation site
2. Migration guides (per platform)
3. Integration tutorials
4. Architecture diagrams
5. Comparison pages

---

Next Steps

1. Validate positioning with 3-5 target users
2. Build landing page from wireframe
3. Write launch thread draft
4. Identify 5 beta users for launch testimonials
5. Set up analytics (Plausible or similar)

• Read about how-to guides in the Diátaxis framework