# Handoff — Create the `CENG` (CBB Engineering) Jira Project

**Cold Bore Ballistics LLC — Confidential**
Created: 2026-06-06
Status: TODO — project not yet created. This document is the executable handoff.

> **Purpose:** Stand up a new Jira project, **key `CENG` ("CBB Engineering")**, to separate engineering work (infrastructure, services, websites, deployment) from the existing `CBB` ("Cold Bore Ballistics — Operations") project, which holds corporate/legal/process/launch-readiness work. This document is written for an executor with **no prior context** — follow it top to bottom.

---

## Why this project exists (context)

The Atlassian site `coldboreballisticsllc.atlassian.net` currently has these projects:

| Key | Name | Holds | Version train |
|---|---|---|---|
| `DOPE` | ScopeDOPE | The ScopeDOPE app (the sellable product) | `1.0.0`, `2.0.0` (the app release train) |
| `CBB` | Cold Bore Ballistics — Operations | Corporate ops: legal/IP, M365, process, **website launch checklist**, **and (currently) infra/eng work** | **none** |

The problem: `CBB` mixes **business operations** with **engineering**, and has no version scheme — so engineering work (e.g. the feedback-service rework) has nowhere clean to track its own release cadence. Mixing them also hurts acquisition due diligence, which wants engineering tracked separately from corporate ops and separately from the sellable app.

**Decision (Jason, 2026-06-06):** create a dedicated **`CENG`** project for CBB engineering. Key is `CENG` (not `CBBE` or similar) specifically to **eliminate confusion and miskeys** against `CBB`.

### Acquisition framing
Three clean buckets, each cleanly separable at sale:
- `DOPE` — the sellable ScopeDOPE app (transfers to a buyer).
- `CENG` — CBB engineering/infra/services (CBB-owned infra; clean operational record for due diligence).
- `CBB` — CBB corporate operations (stays with CBB).

---

## What goes in `CENG` vs `CBB`

**`CENG` (engineering):**
- `cbb-infra` (Terraform / Azure infrastructure) work
- `feedback-service` (the Flask service) — including the rework, see migration below
- Website repos (`scope-dope.com`, `coldboreballisticsllc.com`) engineering/deployment work
- `cbb-utils` tooling work
- BLE bridge tooling (`ble-bridge-*`) if tracked
- Anything with a deploy/release cadence independent of the ScopeDOPE app

**`CBB` (operations) — stays put:**
- Trademark / legal / IP filings
- M365 / Atlassian / Slack admin
- Process / SDLC documentation
- Website **launch readiness / content** checklists (e.g. CBB-70 — ™ marks, Privacy Policy, ToS, footer, voting board). Content/launch-readiness is ops; the *engineering/deploy* of the sites is `CENG`.

---

## Step 1 — Create the project (Jira admin UI)

> Project creation cannot be done via the Atlassian MCP or the REST API with the current Claude Code token (it lacks admin scope / the token is currently failing — see "Known issue" below). Do this in the web UI as a Jira admin.

1. Go to `https://coldboreballisticsllc.atlassian.net`.
2. **Projects → Create project**.
3. Template: **Software development** → choose the **same template family as `CBB`/`DOPE`** (Team-managed vs Company-managed — match the existing projects for consistency; `CBB` and `DOPE` are `projectTypeKey: software`, `simplified: false` → **Company-managed**). Pick **Company-managed** to match.
4. Name: **`CBB Engineering`**
5. **Key: `CENG`** — Jira may default to something else; override it to exactly `CENG`.
6. Lead: Jason Schwefel (`jschwefel@coldboreballisticsllc.com`).

---

## Step 2 — Create the version train

In **CENG → Project settings → Releases**, create:

| Version | Description | Released? |
|---|---|---|
| `1.1.0` | First post-1.0 CBB-engineering feature release (feedback-service Azure rework, etc.) | No |

(Add future versions `1.2.0`, etc. as needed. The engineering version train is **independent** of the DOPE app train — `CENG 1.1.0` ≠ `DOPE 1.1.0`.)

---

## Step 3 — Components (optional but recommended)

In **CENG → Project settings → Components**, add:
- `Infrastructure` (cbb-infra / Azure)
- `feedback-service`
- `Website`
- `Tooling` (cbb-utils)

These let one project cleanly categorize the different engineering streams without further project proliferation.

---

## Step 4 — Migrate `CBB-108` into `CENG`

There is already an engineering issue mis-filed in `CBB` that must move:

- **`CBB-108` — "Rework feedback-service for Azure deployment"** (labels: `v1.1.0`, `feedback-service`, `move-to-CENG`).

To migrate:
1. Open `CBB-108`.
2. **Move** (⋯ menu → Move) → target project **`CENG`**, issue type **Task**.
3. Map fields; set **Fix Version = `1.1.0`** (now that the CENG version exists).
4. Set **Component = `feedback-service`**.
5. Remove the now-redundant `move-to-CENG` label (keep `feedback-service`; `v1.1.0` label can be dropped once the real Fix Version is set).

The full scope/context is already in the CBB-108 description (Azure Container App `ca-feedback-prod`, port 5001, KV `kv-scope-dope-prod` secrets, Postgres on `vm-postgres-prod`, ACR `crcbbprod`, blob `stcbbprod/dope-uploads`, plus the carried follow-ups: github-token placeholder, OIDC SP recreation, postgres CIDR). It will carry over with the Move.

---

## Step 5 — Sweep `CBB` for other engineering issues

Review the `CBB` backlog for other issues that are really engineering and should move to `CENG`. Candidates to check (the doc-coverage gaps named in the repo CLAUDE.md):
- `CBB-29` (M365 Rebuild Guide), `CBB-30` (Atlassian Acquisition Brief), `CBB-31` (Azure Acquisition Brief) — these are **documentation/ops**, likely stay in `CBB`. Judge each: infra *engineering* → `CENG`; corporate doc/process → stays `CBB`.

Leave `CBB-70` (website launch **content** checklist) in `CBB` — it's launch-readiness/content, not engineering.

---

## Step 6 — Update issue-tracking policy doc

The repo `CLAUDE.md` (private, at the working-directory root) currently lists Jira projects as **DOPE, CBB, ESUP**. After `CENG` exists, the Jira-project list should mention `CENG` for engineering work. Flag this to Jason — `CLAUDE.md` is hand-maintained and not committed; do not edit it without his confirmation.

---

## Known issue — REST/MCP cannot create projects or versions

During the 2026-06-06 session:
- The **Atlassian MCP** (`mcp__plugin_atlassian_atlassian__*`) can read/edit/comment issues and run JQL, but has **no project-create or version-create tool**.
- The **REST API** via the Vault secret `kv-cbb-shared-prod/atlassian-admin-api-key` **failed to authenticate** (returned empty/unauthorized — `GET /project/CBB` came back with null fields). That token appears **stale and should be rotated** (generate a new API token at id.atlassian.com → Security → API tokens, store it back in `kv-cbb-shared-prod/atlassian-admin-api-key`). Rotating it would also unblock future script-based Jira automation.

So **Steps 1–2 must be done in the admin UI** (or via a working admin-scoped API token). Steps 4–5 (issue Move, Fix Version, labels) **can** be done via the MCP once the version exists, except the Move operation which is easiest in the UI.

---

## Acceptance checklist

- [ ] `CENG` project created (Company-managed, key exactly `CENG`, lead Jason)
- [ ] Version `1.1.0` created in `CENG`
- [ ] Components added (Infrastructure / feedback-service / Website / Tooling)
- [ ] `CBB-108` moved to `CENG`, Fix Version `1.1.0`, Component `feedback-service`
- [ ] `CBB` swept for other engineering issues; moved as appropriate
- [ ] `atlassian-admin-api-key` rotated in Vault (unblocks future automation)
- [ ] `CLAUDE.md` Jira-project list updated to include `CENG` (with Jason's confirmation)

---

## Document Control

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