# CBB Project Brief: Rifle & Scope System Registry
**Status:** Concept
**Destination:** ScopeDOPE feature (equipment-registry module within the ScopeDOPE product; stays in the `ScopeDOPE/` namespace)
**Tier:** 3 — Longer Horizon
**Classification:** Internal — Confidential
**Version and date:** see Revision Control Block at the end of this document

---

## Summary

A comprehensive equipment registry for the serious precision rifle shooter — a system of record for every rifle, barrel, scope, suppressor, stock, and optic in their collection. Combined with ScopeDOPE™ DOPE history and the barrel lifecycle tracker (Brief #05), the Registry creates a complete, permanent record of a shooter's equipment portfolio. When a scope is swapped between rifles, the registry tracks the move. When a rifle is sold, the full history exports for the buyer. When something breaks, the documentation exists. This is a high-retention feature that dramatically increases switching cost — a shooter with 5 rifles, 10 scopes, and 3 years of history in the CBB Registry is not going to migrate to a competitor app.

---

## Problem Statement

Serious precision rifle competitors own multiple rifles, often many more scopes, and a rotating inventory of suppressors, bipods, stocks, and accessories. Managing this equipment portfolio is difficult:

- **Zero/DOPE tracking:** A scope that lives on three different rifles over two years has a separate zero history for each. Tracking which zero data belongs to which rifle+scope combination requires meticulous notation that most shooters don't maintain.
- **Maintenance history:** "When did I last replace the recoil lug on this rifle?" — most shooters have no reliable answer.
- **Serial number records:** Required for insurance, theft reports, and ATF compliance (constructive possession documentation). Most shooters have these in a notes app or, worse, nothing.
- **Scope move history:** When a scope is moved from Rifle A to Rifle B, the zero data from Rifle A doesn't apply to Rifle B, but the DOPE for common distances may still be useful as a starting point. A registry that tracks scope moves knows this.
- **Sale documentation:** When a rifle is sold, a complete build history (action, barrel, stock, optics, service records) significantly increases the resale value and makes the transaction professional.

---

## Product Concept

### Core Features (v1.0)

**Equipment Registry**
- Add equipment items: rifles (by action, caliber, current configuration), barrels (make, chambering, twist, install date), scopes (make, model, magnification, serial number), suppressors, stocks/chassis, triggers
- Each item has: make, model, serial number, purchase date, purchase price, current location (on which rifle)
- Rifles have a "current configuration" that shows all attached items

**Configuration Tracking**
- When a scope is moved from Rifle A to Rifle B: log the move with date
- Full movement history: every rifle this scope has been on, with dates
- When scope is installed on Rifle B: ScopeDOPE flags all Rifle A DOPE sessions as "pre-move history" and prompts for a new zero confirmation

**DOPE Integration**
- Each rifle+scope combination has its own DOPE history (from ScopeDOPE sessions)
- When viewing a scope's history: see all rifles it's been on, with DOPE data for each combination
- "Best starting point for this rifle+scope combination": ScopeDOPE suggests the most relevant historical data when a familiar scope is remounted on a familiar rifle

**Insurance & Documentation**
- Export full equipment registry as PDF: make/model/serial/purchase price for insurance
- Individual item export: full service history for a rifle being sold
- Serial number search: quickly find which rifle has serial number X (useful when packing for a match)

**Barrel Integration (from Brief #05)**
- Each rifle shows its barrel's round count and service life status
- Barrel change events logged here and synced to ScopeDOPE

### v2.0 Features
- Photo documentation: attach photos to each equipment item
- Insurance value tracking: current market value estimates (optional user input)
- Theft report export: formatted list of all serial numbers and descriptions for law enforcement
- Shared registry (for dealers/gunsmiths): a customer grants their gunsmith read access to their registry — the gunsmith sees the rifle's full history before starting work

---

## Target User

**Primary:** Multi-rifle precision rifle competitors with 2+ rifles and 3+ scopes. This is the demographic that would derive the most value from configuration tracking. Common NRL22/PRS competitor profile: 2–3 rifles, 4–8 scopes across different price tiers, multiple suppressors.

**Secondary:** Collectors who track a large equipment portfolio. Gun owners who want serial number records for insurance.

**Non-target:** Single-rifle casual shooters who have no configuration management complexity.

---

## Revenue Model

**Included in ScopeDOPE** for basic registry (up to 5 items). Full registry (unlimited items) is a premium feature — either tied to a future ScopeDOPE Premium subscription or a small one-time IAP ($4.99 "unlock unlimited equipment").

**The retention value is the revenue argument.** A user with their full equipment portfolio documented in CBB's system is a deeply retained user whose lifetime value is higher than average. The cost of building the registry is justified by churn reduction, not direct revenue.

---

## Strategic Fit with CBB / ScopeDOPE

The Registry is the outer envelope of the ScopeDOPE ecosystem:

```
Equipment Registry (what you own)
    ↓
Barrel Lifecycle Tracker (how worn it is)
    ↓
ScopeDOPE (what your DOPE is)
    ↓
Web Session Manager (reviewing and planning)
    ↓
Match Stage Planner (competition workflow)
```

A user who has all five layers active is essentially impossible to displace. The competitive analysis section of SCOPEDOPE_COMPETITIVE_ANALYSIS.md identifies switching cost as a key retention driver. The Registry maximizes switching cost by documenting the user's entire equipment portfolio — data that exists nowhere else and cannot be recreated without significant effort.

---

## Competitive Landscape

Generic equipment tracking apps exist (GunVault, Gun Manager apps) but none integrate with a ballistic workflow, none have DOPE history, and none have configuration tracking for scope swaps. They are static inventory lists, not dynamic equipment management systems.

---

## Technical Overview

**Platform:** ScopeDOPE module (iOS + Android) + web companion view

**Data model:**
- `EquipmentItem` (base): type, make, model, serial, purchase date, notes
- `Rifle` extends EquipmentItem: caliber, action, weight, LOP
- `Barrel` extends EquipmentItem: chambering, twist, contour, length — links to lifecycle tracker
- `Scope` extends EquipmentItem: magnification range, tube diameter, zero data, current rifle assignment
- `ConfigurationEvent`: scope_id, from_rifle_id, to_rifle_id, date, notes

**Complexity estimate:** Medium-Low. The data model is the interesting part; the UI is straightforward. 3–4 weeks as a ScopeDOPE module addition.

---

## Go-to-Market

**Announce as a ScopeDOPE update:** "Now track your entire equipment portfolio in ScopeDOPE — rifles, scopes, barrels, and complete configuration history." Post in NRL22 community.

**Insurance angle:** "Your serial numbers, in one place, exportable as PDF." This resonates beyond competitive shooters — any gun owner wants this.

**Gunsmith integration (v2.0 hook):** "Share your rifle's history with your gunsmith before they start the build." This creates a link between the Registry and the Gunsmith SaaS (Brief #13).

---

## Success Metrics

| Metric | 6-month | 12-month |
|---|---|---|
| ScopeDOPE users with ≥1 equipment item registered | 30% | 55% |
| Users with ≥3 rifles registered | 15% | 25% |
| Scope move events tracked | Measurable | Trending up |
| PDF exports (insurance documentation) | 100 | 500 |

---

## Risks & Mitigations

| Risk | Likelihood | Mitigation |
|---|---|---|
| Users don't bother populating the registry (high entry burden) | High | One-time onboarding wizard at first launch: "Tell us about your main rifle and scope — takes 2 minutes" |
| Serial number data privacy concerns | Medium | Explicit policy: serial numbers stored encrypted, never shared, never included in anonymized dataset |
| Complex configuration history creates confusing UX | Medium | Default view: current configuration only. History is one tap away, not front and center. |

---

## Resource Requirements

- 1 developer (Jason) — 3–4 weeks as a ScopeDOPE module
- No new infrastructure
- Legal/privacy review: short confirmation that serial number storage complies with existing privacy policy

---

## Recommended Timing

**ScopeDOPE v2.0 or later.** Build the barrel lifecycle tracker (Brief #05) first — it establishes the equipment data model. The Registry extends that model to all equipment types. Sequencing matters: Brief #05 → Brief #15.

---

## Open Questions

- Should suppressors be tracked separately (they have their own serial numbers and are NFA items with specific compliance requirements)? Recommendation: yes — suppressor as a distinct item type with optional NFA Form 4 number field. No compliance guidance beyond record-keeping assistance.
- Should the Registry allow sharing equipment items between users (e.g., a club's shared equipment pool)? Recommendation: not in v1.0 — too complex. Personal registry only.
- Should purchase price and insurance value be tracked? Recommendation: purchase price yes (user-entered, not retrieved externally); market value estimate no — real-time valuation data is complex and liability-prone.

---

## Document Control

| Field | Value |
|---|---|
| **Document owner** | `jschwefel@coldboreballisticsllc.com` |
| **Classification** | Confidential (03_-_Confidential/) |
| **Location** | `OneDrive/ScopeDOPE/03_-_Confidential/Product_Strategy/CBB_BRIEF_15_RIFLE_REGISTRY.md` |
| **Cross-references** | `CBB_PROJECT_BRIEFS_TOC.md` |
| **Created** | 2026-06-02 |
| **Last updated** | 2026-06-09 |
| **Next full review due** | 2027-06-02 |

---

## Revision Control Block

| Rev | Date | Changed By | Reviewed By | Approved By | Summary |
|-----|------|------------|-------------|-------------|-------|
| 0.9 | 2026-06-02 | jschwefel | — | — | Initial release |
| DRAFT | 2026-06-09 | Claude (Opus 4.8) | — | — | Removed header version number (→ Status/Destination + revision-block pointer); added Destination tag (ScopeDOPE feature); applied ™ to first use of ScopeDOPE. |
