Discord Server Guide

Discord Server Guide

The FOUNDUPS Discord server is the community coordination layer for the Foundups ecosystem. It is where stakeholders (012s) gather, discuss, and coordinate — but it is NOT the canonical work surface. GitHub is canonical for code, issues, and PRs. Discord is social.

Server: FOUNDUPS Owner: UnDaoDu (foundups) Operator: 012

---

Entry Flow

The path from discovery to participation:

foundups.com (pfMALL — Play Foundups Mall)
    → browse FoundUps catalog
    → read the litepaper (foundups.com/litepaper)
    → web portal provides Discord entry
    → join FOUNDUPS Discord server
    → read #rules
    → react in #start-here → gain @Stakeholder
    → enter community (COMMONS, FoundUp categories)
    → earn @swarm-contributor via GitHub activity
    → participate in threads, submit work via GitHub
    → agents activate: 01(02) → 0102

The funnel: discover → enter → participate → activate → build.

Discord is the entry point for community. foundups.com is the entry point for discovery. GitHub is the entry point for work.

---

Server Structure

FOUNDUPS (server)
├── FOUNDUPS (category — server root)
│   ├── #rules           — server rules and code of conduct
│   ├── #start-here      — onboarding, reaction roles
│   ├── #announcements   — project announcements
│   └── #introductions   — new member introductions
│
├── COMMONS (category — general community)
│   ├── #general         — open discussion
│   ├── #off-topic       — non-project conversation
│   └── commons-voice    — voice chat
│
├── OPERATOR (category — admin only)
│   ├── #operator-log    — operator actions and decisions
│   ├── #bot-feeds       — bot status and logs
│   └── #mod-room        — moderation discussion
│
└── SCIENCE SWARM HUB (category — first FoundUp community)
    ├── #swarm-general   — Science Swarm discussion
    ├── #swarm-github    — GitHub activity feed (webhook, read-only)
    ├── #swarm-work      — work threads, active contributions
    └── swarm-voice      — Science Swarm voice chat

Each FoundUp gets its own category following this pattern. Science Swarm Hub is the template.

---

Roles

Server-Wide Roles

Role	Access	How to Get
@Operator	Full access, manage everything	Server owner / designated operators
@Core	Post everywhere, create threads	Earned through sustained contribution
@Contributor	Post in community channels	Earned through GitHub activity
@Stakeholder	Read all public channels	React in #start-here
@Unverified	Limited — cannot see FoundUp categories	Default on join

FoundUp-Specific Roles (Science Swarm example)

Role	Purpose
@swarm-contributor	Active Science Swarm contributor — can post in #swarm-work threads
@swarm-notify	Opt-in pings for Science Swarm updates

Bot Roles

Role	Bot	Permissions
@Beneficial AI	0102	ADMINISTRATOR — operator bot
@OBAI	OBAI	Helper only — NO admin, NO moderation

---

Bots

Two bots operate with strictly separated roles:

0102 (Admin/Operator Bot)

• Role: Server infrastructure, moderation, privileged actions
• Permissions: ADMINISTRATOR
• Identity: The operator's hands in Discord
• Runtime: moltbot_bridge / OpenClawDAE

OBAI (Community Helper Bot)

• Role: Helper, explainer, observer, thread participant
• Permissions: View, send, threads, embeds, reactions, slash commands — NO admin, NO moderation, NO role management
• Identity: Community-facing assistant
• Trigger: Mention-based (@OBAI) or slash commands (/obai)
• Does NOT: Verify contributions, assign roles, moderate, claim CABR authority, create GitHub issues

They are separate applications, separate tokens, separate runtimes. See Agent System for the full dual-bot architecture.

---

GitHub Integration

Science Swarm Hub has a live GitHub webhook:

• Repo: FOUNDUPS/science-swarm-hub → Channel: #swarm-github
• Events: Pushes, Pull Requests, Issues, Issue Comments
• Direction: One-way. GitHub → Discord only. Discord never writes to GitHub.
• Channel: #swarm-github is read-only for all users. Only the webhook posts there.

This pattern (GitHub webhook → dedicated #[prefix]-github channel) is the template for all FoundUp categories.

---

What Discord Is and Is NOT

Discord IS	Discord is NOT
Community coordination	The canonical work record
Discussion and questions	The verification surface
Onboarding surface	The economic gate
Thread-based collaboration	The stake verification system
Bot interaction surface	A bidirectional sync with GitHub

GitHub is always canonical for code, issues, PRs, and work records. Discord mirrors status and enables coordination. It does not determine truth.

---

Thread Model

Threads are the primary collaboration surface within FoundUp categories:

• Channels are stable surfaces. They don't change often.
• Threads are active problem rooms. One thread per work unit / math problem / subproject.
• Agents (including OBAI) participate in threads when invoked.
• Humans create or approve thread scope.
• Stale threads get archived, never deleted.

---

Onboarding Path

1. Join the server — via link from foundups.com or direct invite
2. Auto-assigned @Unverified — limited access
3. Read #rules — understand the community guidelines
4. React in #start-here — gain @Stakeholder, unlock community channels
5. Explore — browse COMMONS, read FoundUp categories
6. Contribute — start on GitHub, earn @swarm-contributor
7. Activate — your 01(02) becomes 0102 when you engage with a real problem

---

Related Pages

• Home — Project overview and ROC thesis
• Agent System — Multi-agent architecture, 01(02) → 0102 activation, dual-bot model
• FoundUps Portfolio — Active FoundUp instances
• Getting Started — Development setup
• Contributing Guidelines — How to participate

Back to Wiki Home