# CBB Corp Readiness — v1.0.0 Launch-Blocker Gap Analysis

**Date:** 2026-06-09
**Status:** DRAFT — analysis for review. **No Jira mutations made.**
**Scope:** v1.0.0 corp launch-blockers only (per Founder direction). Post-launch
milestone epics (CBB-37–41, CBB-3, CBB-107) intentionally untouched.
**Tracker:** CBB Jira project (already richly structured — 99 issues, 14 epics).

> ⚠ **Why this is a doc, not executed changes.** I was asked to "reconcile fully
> (close duplicates)" and reopen CBB-20. While verifying each item first (per
> your instruction), I found the CBB "Done" items cannot be trusted as evidence
> of completion, and two contain a forbidden-domain violation. Closing duplicates
> against them would either bury real launch-blocking work or propagate the
> error. **All Jira changes are held pending your ticket→reality mapping below.**

---

## The core problem: "Done" ≠ done

Every "Done" CBB legal/admin item I verified is marked Done **with entirely
unchecked acceptance criteria** — the signature of a planning import where status
was set without the work being verified complete. You already confirmed this for
CBB-20 (trademarks). It is **systemic**, not isolated:

| Done item | Summary | AC state | Contradiction |
|---|---|---|---|
| CBB-16 | Register Google Play + Apple accounts | ☐ all unchecked | §2 has open dupes CBB-65/66 |
| CBB-18 | Draft LLC Operating Agreement | ☐ all unchecked | §1 has open dupe CBB-45 |
| CBB-20 | File 4 USPTO trademarks | ☐ all unchecked | **You confirmed Done is WRONG** → reopen |
| CBB-22 | Write/publish Privacy Policy | ☐ all unchecked | 🔴 **forbidden domain in text** + §2 dupe CBB-64 |
| CBB-23 | Write/publish App EULA | ☐ all unchecked | 🔴 **forbidden domain in text** + §2 dupe CBB-63 |
| CBB-32 | Stand up 1Password Teams | ☐ all unchecked | Marked Done but **"Target version: v1.5+"**; §1 dupe CBB-54 |

**Implication:** I cannot use these Done statuses to justify closing the §1–3
duplicates. Whether each is truly complete is a fact only you can supply.

---

## 🔴 Forbidden-domain violations (highest priority — fix regardless of scope)

Per CLAUDE.md, the bare `coldboreballistics.com` is NOT CBB-owned and forbidden in
**code, config, docs, URLs** — the correct domain is `coldboreballisticsllc.com`.
(Discussing *acquiring* the bare domain is allowed — that's CBB-46. Any other
usage is forbidden.) Two tickets embed it as an instruction:

| Ticket | Offending text | Should be |
|---|---|---|
| CBB-22 | "Publish at `coldboreballistics.com/privacy`" | the live policy URL on `coldboreballisticsllc.com` (or the actual scope-dope.com privacy URL — confirm) |
| CBB-23 | "Publish at `coldboreballistics.com/terms`" | same — correct domain |

**Recommended:** correct these two descriptions regardless of the dedup decision.
The real privacy policy is already live (per project memory) — these tickets just
carry a wrong URL. *(Held pending your OK to edit the descriptions.)*

> Note: CBB-46 "Acquire coldboreballistics.com domain" is **allowed** — it is the
> acquisition-offer task (talking about acquiring the forbidden domain is
> permitted). Left untouched; not a launch blocker.

---

## Apparent duplicate map (§1–3 ladder vs completed/orphan work)

Verified by reading both sides. **None closed** — pending your confirmation that
the "Done"/original side is genuinely complete.

| Open §1–3 task | Duplicate of | Match | Safe to close once you confirm original is real? |
|---|---|---|---|
| CBB-45 Draft Operating Agreement | CBB-18 (Done) | exact | needs CBB-18 verified |
| CBB-54 1Password Teams | CBB-32 (Done) **and** orphan CBB-32 | exact | CBB-32 itself is suspect (v1.5+, unchecked) |
| CBB-55 USPTO ScopeDOPE | CBB-20 | strong (CBB-20 covers all 4) | **CBB-20 Done is wrong → keep CBB-55-58 instead** |
| CBB-56 USPTO Ballistic Computer | CBB-20 | strong | per above |
| CBB-57 USPTO Cold Bore Ballistics | CBB-20 | strong | per above |
| CBB-58 USPTO DOPE-Blend | CBB-20 | strong | per above |
| CBB-63 Write/publish EULA | CBB-23 (Done) | exact | needs CBB-23 verified (+ domain fix) |
| CBB-64 Write/publish Privacy Policy | CBB-22 (Done) | exact | needs CBB-22 verified (+ domain fix) |
| CBB-65 Register Google Play Console | CBB-16 (Done) | strong | needs CBB-16 verified |
| CBB-66 Register Apple Developer | CBB-16 (Done) | strong | needs CBB-16 verified |

**Trademark decision (your call, recorded):** reopen CBB-20 (Done is wrong); keep
CBB-55–58 as the authoritative open trademark tasks; tag them release-blocking.
→ So for trademarks, the *§2 items win* and CBB-20 is the stale one — the inverse
of the other rows, where the Done item may be the real one. This asymmetry is
exactly why each row needs your confirmation.

---

## Genuinely open launch-blockers (no duplicate — real v1.0 corp work)

These have no completed twin and are real launch gates. Candidates to tag
`release-blocking-1.0` once you confirm scope:

**§1 Business Formation (CBB-33)** — the foundation; nothing ships legally without these:
- CBB-42 File Articles of Organization (WI DFI) · CBB-43 Obtain EIN · CBB-44 Business bank account
- CBB-45 Operating Agreement *(= CBB-18 dupe)*
- CBB-51 catch-all email forwarding · CBB-52 Cold Bore Gmail *(= part of CBB-16)* · CBB-53 Zoho Books · CBB-54 1Password *(= CBB-32 dupe)*
- CBB-47 Acquire scopedope.com · CBB-48 ballisticcomputer.net · CBB-49 .app domains · CBB-46 acquire bare domain *(acquisition play, not a blocker)*

**§2 Legal & IP (CBB-34)** — IP protection + store prerequisites:
- CBB-55–58 trademarks *(authoritative per your call)* · CBB-21 provisional patent
- CBB-62 publish .dope spec · CBB-63 EULA *(dupe)* · CBB-64 privacy *(dupe)* · CBB-65/66 store accounts *(dupe)* · CBB-67 NDAs with third parties

**§3 Launch Readiness (CBB-35)** — 17 open; mostly real:
- CBB-69 verify store listings · CBB-70 website launch checklist · CBB-17 App Store listing copy · CBB-68 apply ™ to marketing · CBB-24 external-purchase channel *(now post-launch per our External Purchase work — reconcile)*
- Social handle claims (CBB-71–76), barrel-maker calls (CBB-77/78), Arken (CBB-79) — partnership/marketing, arguably not hard launch *gates*

**§2/§4 (CBB-19 copyright, CBB-36 partnerships)** — CBB-59/60/61 copyright filings; CBB-80/81/82 Niimbot/ELEY outreach (partnership, not a gate).

> **Scope question for you:** "launch-blocker" could be tight (only what legally/
> technically blocks shipping: CBB-42/43/44 formation, trademarks, patent,
> copyright, store accounts, store-listing verification, privacy/EULA) or broad
> (include social-handle claims and partnership outreach). The social/partnership
> items read as *desirable-by-launch*, not *blocking*. Recommend the tight set.

---

## Recommended next actions (all held for your approval)

1. **You map ticket→reality** for the 6 suspect "Done" items (CBB-16/18/20/22/23/32):
   which are genuinely complete vs. planning-import false-Done?
2. **Fix forbidden domain** in CBB-22 + CBB-23 descriptions (recommend yes regardless).
3. **Reopen CBB-20** (confirmed) → Backlog (transition id 11); keep CBB-55–58.
4. **Close confirmed-true duplicates** only after step 1.
5. **Tag the tight launch-blocker set** `release-blocking-1.0`; reconcile under
   CBB-1 (or a launch epic) — note CBB-1 is currently "Done" with no children, so
   it may need reopening or the §1–3 epics become the launch home.
6. **CBB-24 (external purchase)** → mark post-launch per our External Purchase
   Strategy decision (not a v1.0 gate).
7. Write the REQUIREMENTS-style tracker referencing final CBB keys (like the DOPE one).

## Open structural question

CBB-1 "v1.0.0 Launch — Legal & Admin" is **Done with zero children**, while the
§1–3 epics hold all the actual open launch work. Either CBB-1 is the real launch
epic (and should be reopened + made parent) or the §1–3 ladder is. **Which is the
launch home?** This determines where release-blocking work gets parented.
