# Slack Workspace Guide — Cold Bore Ballistics, LLC

**Workspace:** coldboreballisticsllc.slack.com
**Classification:** Confidential

---

## Overview

Slack is the internal communications platform for Cold Bore Ballistics, LLC. It is used for team coordination, GitHub activity notifications, and per-repo development discussion. Each active GitHub repository has a dedicated channel. A catch-all channel aggregates notifications across all repos.

---

## Joining the Workspace

1. Open a browser and navigate to `https://coldboreballisticsllc.slack.com`.
2. Click **Sign in** and use your `@coldboreballisticsllc.com` email address.
3. If you have not yet been invited, contact the workspace administrator to receive an invitation link.
4. Slack is available as a desktop app (recommended), web app, and mobile app. Download the desktop app from `https://slack.com/downloads`.

---

## Channel Directory

### General Channels

| Channel | Purpose |
|---|---|
| `#all-cold-bore-ballistics-llc` | Company-wide announcements and updates |
| `#scopedope_general` | General ScopeDOPE product discussion |
| `#social` | Non-work conversation |
| `#github-activity` | Catch-all GitHub notifications for all repositories |

### Repository Channels

Each repository has a dedicated channel. GitHub activity (pull requests, reviews, commits, releases, deployments, workflow runs) is posted here automatically via the GitHub app.

| Channel | Repository | Notes |
|---|---|---|
| `#scopedope-android` | `ColdBoreBallistics/scopedope-android` | ScopeDOPE Android app |
| `#scopedope-shared` | `ColdBoreBallistics/scopedope-shared` | Shared KMP ballistics engine and assets |
| `#scopedope-ios` | `ColdBoreBallistics/scopedope-ios` | ScopeDOPE iOS app |
| `#dope-format` | `ColdBoreBallistics/dope-format` | `.dope` file format spec; also receives issue notifications (public repo) |
| `#www-scope-dope-com` | `ColdBoreBallistics/www.scope-dope.com` | ScopeDOPE marketing website |
| `#www-coldboreballisticsllc-com` | `ColdBoreBallistics/www.coldboreballisticsllc.com` | CBB company website |
| `#cbb-utils` | `ColdBoreBallistics/cbb-utils` | Internal scripts and utilities |
| `#cbb-infra` | `ColdBoreBallistics/cbb-infra` | Azure Terraform infrastructure |
| `#ble-bridge-server` | `ColdBoreBallistics/ble-bridge-server` | BLE Bridge desktop TCP server |
| `#ble-bridge-android` | `ColdBoreBallistics/ble-bridge-android` | BLE Bridge Android app |
| `#ble-bridge-ios` | `ColdBoreBallistics/ble-bridge-ios` | BLE Bridge iOS app |

---

## GitHub Integration

The official **GitHub app for Slack** is installed in this workspace. It posts real-time notifications from GitHub into the appropriate repo channel and into `#github-activity`.

### Events Subscribed

| Event | All repos | `#dope-format` only |
|---|---|---|
| Pull requests | Yes | Yes |
| Pull request reviews | Yes | Yes |
| Commits | Yes | Yes |
| Releases | Yes | Yes |
| Deployments | Yes | Yes |
| GitHub Actions workflow runs | Yes | Yes |
| Issues | **No** | **Yes** |

`dope-format` is the only public-facing repository with a community issue tracker, so issue notifications are enabled there only.

### Interacting with GitHub Notifications

- Click any notification in Slack to open the linked PR, commit, or workflow run in GitHub.
- You can approve pull requests, leave reviews, and manage issues directly from within Slack using the action buttons attached to notifications.
- To mute notifications from a specific repo in a given channel, use `/github unsubscribe ColdBoreBallistics/<repo-name> <event>`.

---

## Channel Naming Conventions

When a new repository is added, its Slack channel must follow these rules:

- All lowercase, hyphens only (no underscores, no dots, no spaces)
- Repository name with dots converted to hyphens: `www.scope-dope.com` → `#www-scope-dope-com`
- Must match the repository name as closely as possible
- Prefix `www-` for website repositories

---

## Adding a New Repository Channel

See `Slack_Admin_Setup_Guide.md` for the full procedure.

---

## Workspace Etiquette

- Repository channels are primarily for GitHub notifications. Substantive discussion about a PR or issue should be threaded under the notification, not posted as a new top-level message.
- `#github-activity` is read-only by convention — do not use it for discussion.
- `#all-cold-bore-ballistics-llc` is for announcements only — keep it low-volume.

---

## Document Control

| Field | Value |
|---|---|
| **Document owner** | `jschwefel@coldboreballisticsllc.com` |
| **Classification** | Confidential (03_-_Confidential/) |
| **Location** | `OneDrive/CBB_Corporate/03_-_Confidential/Infrastructure/Slack/Obsolete/Slack_Workspace_Guide.md` |
| **Cross-references** | `Slack_Architecture_Reference.md`; `Slack_Operating_Runbook.md` |
| **Created** | 2026-06-04 |
| **Last updated** | 2026-06-04 |
| **Next full review due** | 2027-06-04 |

---

## Revision Control Block

| Rev | Date | Changed By | Reviewed By | Approved By | Summary |
|-----|------|------------|-------------|-------------|---------|
| 0.9 | 2026-06-04 | jschwefel | — | — | Initial release |
