# Atlassian Acquisition Brief
**Cold Bore Ballistics LLC — Confidential**
Last updated: 2026-06-06

> This document summarizes the CBB Atlassian instance for acquisition due diligence. Written for a buyer's technical or business team. For full operational detail, see `Atlassian_Architecture_Reference.md`, `Atlassian_Operating_Runbook.md`, and `Atlassian_Rebuild_Guide.md`.

---

## What It Is

Atlassian is the project management and knowledge-management platform for Cold Bore Ballistics LLC. The CBB instance (`coldboreballisticsllc.atlassian.net`) provides:

- **Jira Software** — issue tracking for all product development (ScopeDOPE) and company operations (legal, IP, infrastructure, business development)
- **Jira Service Management (JSM)** — structured customer support intake for ScopeDOPE; triage gate before work enters the product backlog
- **Confluence** — internal engineering and operations knowledge base

---

## Assets Included in Acquisition

| Asset | Description | Value to Acquirer |
|---|---|---|
| Atlassian site | `coldboreballisticsllc.atlassian.net` — permanent, cannot be renamed | Stable URL; company-canonical name already in the domain |
| Cloud ID | `f09947a5-08f9-4bb5-9f6c-4ae74d368f66` | Stable API identifier for all automation |
| DOPE project | ScopeDOPE product backlog — all bugs, features, improvements, engine and hardware work | Complete product work history and active backlog |
| CBB project | Operations backlog — legal, IP, infrastructure, business development | Full operational history; acquisition due diligence items tracked here |
| ESUP project | ScopeDOPE Engineering Support — customer-facing support intake, 13 request types | Ready-to-use support system; no configuration required |
| Confluence SCOPE space | ScopeDOPE engineering knowledge base — KB articles, hardware docs, release status | Customer-facing support knowledge base already linked to JSM |
| Confluence CBBOPS space | Internal operations wiki — brand, legal, infrastructure, vendor contacts | Operational knowledge transfer artifact |
| GitHub for Jira integration | Connected to `ColdBoreBallistics` GitHub org; auto-links commits, branches, and PRs to issues | Full development traceability between code and issues |
| Repository custom field | Multi-select issue field mapping issues to one or more of 11 repos | Query issues by repo (`JQL: Repository = "scopedope-android"`) |
| Hardware label convention | `hw:<driver_id>` labels on DOPE issues — queryable by hardware target | `JQL: project = DOPE AND labels = "hw:niimbot_b21_pro"` |

---

## Plan and Cost

| Product | Plan | Monthly cost | Limits |
|---|---|---|---|
| Jira Software | Free | $0 | 10 users |
| Jira Service Management | Free | $3/agent/month at Standard | 3 agents on Free |
| Confluence | Free | $0 | 10 users, 2 GB storage |
| **Total** | **Free** | **$0/month** | — |

The instance is on the Free plan. At launch scale (single-founder team) this is sufficient. On upgrade to Standard (~$7.75/user/month for Jira Software), the permission scheme, project role actors, and Confluence space permissions that are already staged activate automatically by re-running the setup script — no manual re-configuration.

---

## Issue Tracking Policy — Acquisition Relevance

| Repo | Tracker | Rationale |
|---|---|---|
| `dope-format` (public) | GitHub Issues | Community-facing; public artifact |
| All private repos | Jira (DOPE / CBB / ESUP) | Internal operational artifact |

This boundary is deliberate. The public issue tracker on `dope-format` is a community-facing signal of openness and ecosystem engagement. The Jira backlog is the internal operational record. A buyer gets both: the community engagement signal on GitHub and the full internal history in Jira.

---

## Traceability

Every Jira issue that touches code is linked to its commits, branches, and pull requests via the GitHub for Jira integration. The Repository custom field on each issue records which repo(s) it touches — making it possible to answer "what was changed in `scopedope-android` between v0.9.5 and v1.0.0?" directly from Jira without reading git history.

This level of traceability is directly relevant to an acquirer's technical due diligence.

---

## Support Infrastructure

The ESUP project is a production-ready customer support system. Its 13 request types cover the full range of ScopeDOPE support scenarios (7 bug categories, 4 feature request categories, hardware validation, admin). The JSM portal is linked to the Confluence SCOPE knowledge base — articles are suggested to customers automatically when they submit a ticket, reducing agent load.

---

## Free-Plan Constraints Active at Acquisition

| Constraint | Impact | Resolution at Standard |
|---|---|---|
| Custom permission scheme not assigned to projects | Default Jira permissions apply — all authenticated users have broad access | Re-run setup script after upgrade; scheme is already staged |
| Confluence space permissions not enforced | All authenticated users can view/edit all spaces | Re-run setup script after upgrade |
| JSM portal groups manually managed | Portal group changes require UI, not API | No change — JSM portal groups are always a manual task regardless of plan |
| 10-user Jira limit | Adequate at current team size | Standard plan removes this cap |

None of these constraints affect data integrity or traceability. They affect access control granularity, which activates cleanly on plan upgrade.

---

## Credentials and Access

Access is controlled via `admin@coldboreballisticsllc.com`. There are no API credentials stored in Azure Key Vault for Atlassian — access is via the Atlassian MCP (API token) and the admin account. The admin account password and API token are stored in the CBB credential store (see `OneDrive/CBB_Corporate/03_-_Confidential/`).

Transfer of the Atlassian organization to a buyer is done via **`admin.atlassian.com` → Organization → Settings → Transfer ownership** — requires the current admin to initiate.

---

## Acquisition Recommendation

The Atlassian instance is clean, company-canonical, and well-structured for a handoff. The naming (`coldboreballisticsllc.atlassian.net`), the project structure (DOPE / CBB / ESUP), and the GitHub integration are all acquisition-readiness choices made from day one. The full product backlog, support history, and operational record are in one place, with code traceability built in.

The only action required before acquisition handoff is upgrading from Free to Standard to activate the permission model — a one-click upgrade, after which the setup script applies all staged permissions automatically.

---

## Document Control

| Field | Value |
|---|---|
| **Document owner** | `jschwefel@coldboreballisticsllc.com` |
| **Classification** | Confidential (03_-_Confidential/) |
| **Location** | `OneDrive/CBB_Corporate/03_-_Confidential/Infrastructure/Atlassian/Atlassian_Acquisition_Brief.md` |
| **Cross-references** | `Atlassian_Architecture_Reference.md`; `Atlassian_Operating_Runbook.md`; `Atlassian_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 |
