# Discord Community Launch Runbook

Owner: Community + Maintainers
Status: Launch-ready

## Objective

Launch and operate the SINT Discord server as the primary real-time community channel for:

- Integrator support
- Protocol Q&A
- Security discussions
- Contributor coordination

## Server Structure

## Categories and Channels

- `START HERE`
- `#welcome`
- `#rules`
- `#announcements`

- `COMMUNITY`
- `#introductions`
- `#general`
- `#show-and-tell`

- `BUILD WITH SINT`
- `#mcp-integration`
- `#ros2-and-robotics`
- `#industrial-iot`
- `#policy-design`

- `CONTRIBUTING`
- `#good-first-issues`
- `#contributor-onboarding`
- `#maintainer-office-hours`

- `SECURITY`
- `#security-bulletins`
- `#incident-reporting` (private mod intake)

## Roles

- `Maintainer`
- `Moderator`
- `Contributor`
- `Design Partner`
- `Security Researcher`
- `Community Member`

## Moderation Policy

- Enforce a strict no-harassment, no-doxxing, no-malware-sharing policy.
- Redirect vulnerability details to private security channels.
- Require technical claims to include reproducible context when possible.

Escalation ladder:

1. Warning
2. Timeout
3. Temporary ban
4. Permanent ban

## Launch Day Checklist

1. Finalize channels and permissions.
2. Post `#welcome` and `#rules` copy.
3. Publish invite link in README + launch posts.
4. Seed `#good-first-issues` with 5 starter tasks from `docs/community/good-first-issues-board.md`.
5. Schedule first office hours session.
6. Announce first security bulletin date.

Use `docs/community/discord-launch-kit.md` for copy/paste launch messages and CTA templates.

## Week 1 Success Metrics

- 100+ joined members
- 20+ unique posters
- 5+ integration support threads resolved
- 1+ external contributor starts first PR

## Operations Cadence

- Daily: moderator review of flagged content
- Weekly: office hours + issue triage summary
- Monthly: post SINT security bulletin in `#security-bulletins`
