# Slack Acquisition Brief — Cold Bore Ballistics, LLC

**Classification:** Confidential
**Last updated:** 2026-06-06
**Audience:** Acquirer technical due diligence team, investors, and CBB leadership

---

## Summary

Cold Bore Ballistics uses Slack as its internal communications platform. The workspace is on the Business Standard plan, covers all active engineering repositories via a per-repo GitHub notification model, and enforces a written data-classification policy. The workspace is production-ready and transferable.

---

## Platform and Ownership

| Property | Value |
|---|---|
| **Platform** | Slack (Salesforce, Inc.) |
| **Workspace URL** | `coldboreballisticsllc.slack.com` |
| **Plan** | Business Standard (~$8.75/user/month billed annually) |
| **Admin account** | `jschwefel@coldboreballisticsllc.com` |
| **Workspace created** | 2026-06-04 |
| **Message retention** | Unlimited (Business Standard) |

The workspace is owned and billed under the CBB admin account. There is no personal account dependency — ownership can be transferred to any `@coldboreballisticsllc.com` account.

---

## What Lives in Slack

Slack is classified as a **General (02)** tier surface. It is used for:

- Team coordination and internal discussion
- Real-time GitHub activity notifications (PRs, commits, releases, CI runs) per repository
- Company-wide announcements (`#all-cold-bore-ballistics-llc`)
- Product discussion (`#scopedope-general`)

Slack does **not** contain:

- Source code or binaries
- Confidential documents (SPEC, engine internals, financial records, legal)
- Customer or user data
- Credentials or secrets

A data-classification policy is posted and pinned in `#all-cold-bore-ballistics-llc`.

---

## Channel Structure

16 channels covering all active repositories, product discussion, and company-wide announcements. Every channel has a description. The GitHub integration uses a per-repo model (one channel per repo) rather than a catch-all, keeping signal-to-noise high.

Full channel listing: see `Slack_Architecture_Reference.md`.

---

## GitHub Integration

The official GitHub app for Slack is installed and authenticated against the `ColdBoreBallistics` GitHub organization. All 11 active repositories post notifications to their dedicated channels. There is no catch-all channel — each repo routes to exactly one channel.

This integration is stateless and transferable — if the GitHub organization is transferred to an acquirer, the GitHub app connection is re-authenticated; Slack subscriptions survive the reconnect with `/github subscribe` commands.

---

## Users

| User | Role |
|---|---|
| `jschwefel@coldboreballisticsllc.com` | Owner / Admin |

Single-person operation. No contractors or external guests. The workspace is ready to scale — new members are invited via the admin console and automatically join all public channels.

---

## Plan Comparison and Upgrade Path

| Feature | Business Standard | Business+ | Enterprise Grid |
|---|---|---|---|
| Message retention | Unlimited | Unlimited | Unlimited |
| Guest accounts | Yes | Yes | Yes |
| SAML SSO | No | **Yes** | Yes |
| Message export | Admin export only | Admin export only | Full DLP + export |
| DLP controls | No | No | **Yes** |
| Compliance exports | No | No | Yes |
| Price (est.) | ~$8.75/user/mo | ~$15/user/mo | Custom |

**Current gap:** No SAML SSO (Business Standard). At current headcount (1 person), this is not material. At 5+ people, SSO becomes a security hygiene requirement. Budget for Business+ upgrade at first external hire.

**DLP gap:** No automated data-loss prevention at Business Standard or Business+. Mitigated by written policy and manual enforcement. Enterprise Grid adds automated DLP scanning if required by compliance or by an acquirer's security posture.

---

## Acquisition Considerations

**Positive signals:**
- Workspace URL matches company domain (`coldboreballisticsllc.slack.com`) — no rebranding needed
- Per-repo GitHub notification model is clean and scalable
- Data-classification policy is documented and pinned
- All channels have descriptions — workspace is self-documenting
- No personal account dependency — fully transferable
- No customer or user data stored in Slack

**Items for acquirer to evaluate:**
- SAML SSO not yet enabled — standard ask at Business+ or higher; straightforward to enable
- No automated DLP — policy-only controls at current plan tier
- Single administrator — transfer of workspace ownership is a 5-minute admin operation

**Transfer procedure:** Workspace ownership is transferred via Admin console → Members → select user → Change role to Owner. The outgoing owner is demoted to Admin or deactivated. No data loss occurs.

---

## Document Control

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

---

## Revision Control Block

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