Artemis City Discord Community Structure

Published on June 10, 2024

Goal: Foster engaged, helpful community that reduces your support burden

Target: 50+ members Week 1, 200+ Month 1

Success Metric: Active daily discussions, community answering each other's questions


Discord Community Structure

Server Setup

Server Name

Artemis City

Server Description

The kernel-driven operating system for AI agents.

Official Discord for Artemis City developers—get help, share projects, and shape the roadmap.

Server Icon

Artemis City logo (single emoji or custom)

Invite Link

Custom vanity URL: discord.gg/T2Huqg4c


Channel Structure

📋 INFORMATION

#welcome

👋 Welcome to Artemis City!

We're building a kernel-driven operating system for AI agents—deterministic, governed, and production-ready.

🚀 Get Started:
• Quick-start guide: [link]
• GitHub: [link]
• Whitepaper: [link]

💬 How to Get Help:
1. Check #faq first
2. Ask in #support
3. Share your project in #showcase

🤝 Community Guidelines:
• Be respectful and helpful
• No spam or self-promotion (unless relevant to Artemis City)
• Keep discussions on-topic per channel
• Search before asking (you might not be the first)

📢 Stay Updated:
• #announcements - Product updates and releases
• #changelog - Detailed changes

Let's build something incredible together.

#announcements (read-only, Prinston only)

  • Product launches
  • Major releases
  • Important updates
  • Community milestones

#changelog (auto-feed from GitHub releases)

  • Version updates
  • Bug fixes
  • New features
  • Breaking changes

#faq (read-only, curated)

  • Common questions and answers
  • Troubleshooting guides
  • Updated based on #support themes

💬 COMMUNITY

#general

  • Casual discussion
  • Introductions
  • Off-topic (within reason)
  • Community building

#support

  • Installation issues
  • Configuration help
  • Error debugging
  • "How do I...?" questions

#showcase

  • Share your Artemis City projects
  • Demo workflows
  • Creative use cases
  • Success stories

#feedback

  • Feature requests
  • Bug reports
  • UX/DX improvements
  • Roadmap input

🛠️ DEVELOPMENT

#development

  • Architecture discussions
  • Technical deep-dives
  • Performance optimization
  • Advanced configurations

#plugins

  • Plugin development
  • Share custom plugins
  • Tool integrations
  • MCP discussions

#agents

  • Custom agent templates
  • Agent design patterns
  • Routing strategies
  • ATP (Agent Template Protocol)

#memory-bus

  • Obsidian integration
  • Supabase setup
  • Memory architecture
  • Trust-decay discussions

🎯 WORKING GROUPS (Add as needed)

#governance-wg

  • Enterprise features
  • Compliance requirements
  • Audit tooling
  • RBAC design

#cloud-wg

  • Artemis City Cloud
  • Deployment strategies
  • Scaling patterns
  • Multi-instance coordination

🤝 CONTRIBUTION

#contributors

  • For active contributors
  • Coordination on PRs
  • Code review discussions
  • Release planning

#docs

  • Documentation improvements
  • Tutorial creation
  • Example workflows
  • Content feedback

🎤 VOICE CHANNELS

General Voice

  • Casual hangout
  • Pairing sessions
  • Ad-hoc discussions

Office Hours (scheduled)

  • Weekly Q&A with Prinston
  • Deep-dive sessions
  • Community demos

Roles & Permissions

@Founder (Prinston)

  • All permissions
  • Distinguishable color (gold/blue)
  • Can post in #announcements

@Core Team

  • Active maintainers
  • Moderate channels
  • Pin helpful messages
  • Manage spam

@Contributors

  • Merged 1+ PRs
  • Special badge
  • Access to #contributors
  • Recognition role

@Early Adopter

  • Joined in first month
  • Special badge
  • Community recognition

@Member (default)

  • Access to all public channels
  • Can post everywhere except #announcements

Moderation Guidelines

What to Encourage

  • ✅ Thoughtful questions
  • ✅ Helpful answers
  • ✅ Constructive criticism
  • ✅ Project showcases
  • ✅ Learning in public

What to Discourage

  • ⚠️ Spam
  • ⚠️ Off-topic promotion
  • ⚠️ Unconstructive negativity
  • ⚠️ Repeated questions (point to docs)
  • ⚠️ DM harassment

Moderation Actions

  1. First time: Friendly redirect to appropriate channel
  2. Second time: Public reminder of guidelines
  3. Repeated: Timeout (24h)
  4. Severe/malicious: Ban

Automation & Bots

Welcome Bot

Auto-message in #general when someone joins:

👋 Welcome @username to Artemis City!

🚀 Get started: [quick-start link]
💬 Introduce yourself and tell us what you're building!
❓ Need help? Ask in #support

GitHub Bot

Auto-post to #changelog:

  • New releases
  • Merged PRs
  • New issues (optional, can be noisy)

FAQ Bot (Optional)

Trigger responses for common questions:

  • !quickstart → Links to quick-start guide
  • !whitepaper → Links to whitepaper
  • !vs-autogpt → Links to comparison

Community Programs

Weekly Office Hours

Time: Every Wednesday, 12 PM ET / 9 AM PT

Format:

  • 30 min Q&A with Prinston
  • 15 min demo/deep-dive on a topic
  • 15 min community showcases

Topics rotation:

  • Week 1: Architecture overview
  • Week 2: Plugin development
  • Week 3: Memory bus deep-dive
  • Week 4: Production deployments

Contributor Spotlights

Monthly recognition:

  • Feature top contributor in #announcements
  • Highlight their work
  • Special badge
  • Optional interview/feature

Showcase Fridays

Every Friday, encourage community to share:

  • What they built this week
  • Interesting workflows
  • Lessons learned
  • Cool agent interactions

First Week Engagement Strategy

Day 1 (Launch Day)

Your actions:

  • Post in #announcements: "Artemis City v1.0 is live!"
  • Be active in #general for introductions
  • Respond to every question in #support
  • Share launch blog in #general

Expected:

  • 10-20 members
  • Lots of setup questions
  • Excitement + curiosity

Day 2-3

Your actions:

  • Continue active support
  • Start pinning best answers
  • Encourage first showcases
  • Share interesting discussions on Twitter

Expected:

  • 20-40 members
  • First projects starting
  • Architecture questions

Day 4-5

Your actions:

  • First office hours (if ready)
  • Update #faq based on common questions
  • Highlight community contributions
  • Start seeing community-to-community help

Expected:

  • 40-60 members
  • Self-sustaining discussions
  • First plugin contributions

Conversation Starters

In #general:

What's the first agent workflow you want to build with Artemis City?

I'm curious what problems you're trying to solve.

In #showcase:

Would love to see what you're building!

Even if it's early/broken, sharing works-in-progress helps everyone learn.

In #feedback:

What's the #1 thing that would make Artemis City more useful for you?

Be specific—helps us prioritize the roadmap.

Response Templates

Installation Issues

Let's debug this together.

Can you share:
1. Your OS and Python version (python --version)
2. The full error message
3. Your Artemis City version (codex --version)

Also, have you checked the troubleshooting guide? [link]

Feature Requests

Great idea! This aligns with [use case].

Can you describe:
- Your specific use case
- How you'd use this feature
- What the workflow would look like

Helps us design it right. Also consider adding to GitHub discussions: [link]

Showcase Appreciation

🔥 This is awesome! Love seeing [specific thing].

[Thoughtful question about their implementation]

Mind if we feature this in a blog post / Twitter?

Metrics to Track

Growth:

  • Members per day
  • Active members (posted in last 7 days)
  • Retention (% still active after 30 days)

Engagement:

  • Messages per day
  • Questions asked in #support
  • Questions answered by community (not just you)
  • Projects shared in #showcase

Quality:

  • Average response time to questions
  • % questions answered within 24h
  • Community helpfulness (community answers / total answers)

Conversion:

  • Discord → GitHub stars
  • Discord → Contributors
  • Showcase projects → Case studies

Warning Signs (and Fixes)

"Only Prinston answers questions"

Fix:

  • Explicitly thank community members who help
  • Give @Contributor role for helpful answers
  • Sometimes wait 30 min before answering (let community try)

"Same questions over and over"

Fix:

  • Update #faq
  • Improve docs
  • Create FAQ bot triggers
  • Pin answers in #support

"Ghost town (no activity)"

Fix:

  • Post conversation starters
  • Share interesting external content
  • Highlight wins (GitHub stars, showcases)
  • Schedule office hours

"Toxic/negative vibes"

Fix:

  • Address immediately (DM or public, depending)
  • Reinforce guidelines
  • Timeout if needed
  • Create positive examples (gratitude, celebration)

Month 1 Goals

Quantitative:

  • 200+ members
  • 50+ daily active users
  • 5+ community-answered questions per day
  • 10+ showcase projects
  • 80%+ questions answered within 24h

Qualitative:

  • Community members helping each other
  • Positive, collaborative vibe
  • Active #showcase with real projects
  • Constructive #feedback discussions
  • Contributors coordinating in #contributors

Ready to Launch?

Pre-launch checklist:

  • [ ] All channels created
  • [ ] Roles configured
  • [ ] Welcome message written
  • [ ] #faq populated (even if basic)
  • [ ] Moderation team identified (even if just you at first)
  • [ ] Vanity URL claimed
  • [ ] Welcome bot configured
  • [ ] You're ready to be active for first 48h

After launch:

  1. Post invite link in GitHub README
  2. Share in HN comments
  3. Share on Twitter/LinkedIn
  4. Be hyper-responsive first week
  5. Set tone: helpful, technical, collaborative

Remember: The community reflects your energy. Be the community member you want to attract.

Let's build something incredible together. 💬