# ONEDRIVE ORGANIZATION GUIDE
**Cold Bore Ballistics™ LLC — Confidential**
Last updated: 2026-06-13

---

## Purpose

This document is the authoritative reference for what lives where across all OneDrive folders. Every file and document created under the CBB OneDrive must conform to this guide. When in doubt about where something belongs, consult this document — do not guess and do not create new folders without updating it.

---

## Top-Level Namespace Structure

OneDrive is organized into top-level namespaces, one per entity or product. Within each namespace, folders follow the same data-classification tier scheme.

| Namespace | Folder | Contains |
|---|---|---|
| Corporate identity | `CBB_Corporate/` | Company-level operations, infrastructure, legal, finance, process, brand standards |
| ScopeDOPE product | `ScopeDOPE/` | Product strategy, design, engine documentation, marketing, the SPEC |
| cbb-sign product | `CBB_Sign/` | Internal document signing platform — SDLC, SPEC, infrastructure docs |

---

## Classification Tiers (apply within each namespace)

| Tier | Folder | Classification |
|---|---|---|
| 1 | `01_-_Public/` | Public-safe material — may be shared externally without restriction |
| 2 | `02_-_General/` | Internal but not sensitive — shared across the organization |
| 3 | `03_-_Confidential/` | Sensitive business material — restricted to principals and trusted advisors |
| 4 | `04_-_Highly_Confidential/` | Trade secrets and IP — strictest access; never quoted in public channels, commit messages, or issue trackers |

Not every namespace uses every tier. Create a tier only when content exists for it.

---

## CBB_Corporate/

### `CBB_Corporate/01_-_Public/`

| Folder | Contents |
|---|---|
| `Email_Signatures/` | Branded email signature templates (`.html`, `.docx`) and setup instructions |
| `Logos_and_Wordmarks/` | Approved logo files and wordmarks for both CBB and ScopeDOPE, cleared for external use |

### `CBB_Corporate/02_-_General/`

| Folder / File | Contents |
|---|---|
| `App_Store_Accounts/` | Google Play and Apple App Store account details, credentials references |
| `Certs/` | Internal CA root certificate (`rootCA.pem`) for LAN sites |
| `Domain_Records/` | Domain registrar records, DNS configuration references, SSL certificate inventory |
| `Vendor_Communications/` | General vendor correspondence not rising to Confidential classification |
| `OPEN_QUESTIONS.md` | Running list of unresolved decisions and open items across the business |

### `CBB_Corporate/03_-_Confidential/`

#### `Financial_Records/`

Financial planning, actuals, and investor-facing materials.

**Belongs here:**
- Budgets and financial projections
- Revenue and expense actuals
- Cap table and equity records
- Investor materials and term sheets
- Tax records and filings
- Startup-program and credit-grant application packages (`Startup_Programs/` — see below)

##### `Financial_Records/Receipts/`

Source receipts and purchase records, organized by product/entity then year.

| Subfolder | Contents |
|-----------|----------|
| `Receipts/CBB/YYYY/` | Receipts for CBB corporate expenses (hardware, domains, office supplies, infrastructure) |
| `Receipts/ScopeDOPE/YYYY/` | Receipts for ScopeDOPE-specific expenses (R&D hardware, product-specific tooling) |

**Naming convention:** `VENDOR-ORDERNUMBER-YYYYMMDD.md`
(e.g., `AMAZON-111-3017969-2849004-20260607.md`, `BESTBUY-1126158117243-20260607.md`)

**Note:** Original PDFs (when available) are saved alongside their `.md` summaries using the same base filename.

##### `Startup_Programs/`

Application packages for startup credit and accelerator programs (Anthropic Claude for Startups, Microsoft Founders Hub, Claude for Open Source, AWS/GCP fallbacks). Each program gets one self-contained package file: program summary, submittable application copy, and a submission/tracking checklist.

**Belongs here:**
- One `*_Application.md` per program (e.g., `Claude_for_Startups_Application.md`, `Microsoft_Founders_Hub_Application.md`, `Claude_for_Open_Source_Application.md`)

**Note:** Operational follow-up (submit, track, log decision) is mirrored as Jira issues under the CBB Epic "Startup & credit program applications" — the packages here are the source content; Jira is the work tracker. Approved credit amounts and expirations are logged in `Financial_Records/` per the existing convention.

#### `Infrastructure/`

"Run the business" — IT systems, hosted services, cloud infrastructure, and operational vendor tooling. A buyer's technical due diligence will scrutinize this folder first.

Each infrastructure domain has its own subdirectory. Within each subdirectory, the following document types are maintained (see `CLAUDE.md` — Operational Domain Documentation Structure for full rules):

| Doc type | Filename pattern |
|---|---|
| As-built state | `*_Architecture_Reference.md` |
| Step-by-step procedures | `*_Operating_Runbook.md` |
| Disaster recovery / rebuild | `*_Rebuild_Guide.md` |
| Acquisition view | `*_Acquisition_Brief.md` |
| Recommendations *(optional)* | `*_Recommendations.md` |

**Current subdirectories:**

| Subdirectory | Domain |
|---|---|
| `Android_Dev/` | Android development phone — setup, adb, sideloading, BLE capture |
| `Atlassian/` | Jira Software (DOPE, CBB) and Confluence — project and knowledge management. JSM project ESUP is being decommissioned per CLAUDE.md. |
| `Azure/` | Cloud infrastructure — VMs, storage, networking, Terraform state |
| `Azure_Key_Vault/` | Azure Key Vault — secret inventory, access policies, rotation procedures |
| `CBB_Sign/` | cbb-sign signing platform — architecture, runbook, rebuild, acquisition brief, cost-impact analysis (the **operational infra** doc set; the project SDLC/SPEC/LOE live in the `CBB_Sign/` namespace) |
| `DocuSeal/` | DocuSeal self-hosted e-signature — evaluation, architecture, runbook, rebuild |
| `M365/` | Microsoft 365 — Exchange, SharePoint, Teams, admin |
| `Namecheap/` | Namecheap — domain registrar, DNS management, API key |
| `SendGrid/` | SendGrid — transactional email delivery, domain authentication, API keys |
| `Sentry/` | Sentry — error and crash reporting, session tracking, alerting |
| `Slack/` | Slack workspace — channels, integrations, administration |
| `Twilio/` | Twilio — telephony, SMS, IVR, voicemail |
| `Websites/` | Web hosting, nginx, deployment, domain routing |

#### `Legal_and_Trademarks/`

All legal documents, filings, and IP records.

**Belongs here:**
- USPTO trademark filings and correspondence
- Patent research and filing materials
- NDAs, MSAs, contractor agreements, partnership agreements
- Entity formation documents
- Legal counsel correspondence

#### `Process/`

Operational processes and startup playbooks.

**Belongs here:**
- `CBB_SDLC.md` — CBB-wide master SDLC
- `App_Store_Release_Runbook.md` — Google Play & Apple App Store pre-release and production release procedures
- Startup and onboarding guides
- Operational process definitions

**Note:** Project-specific SDLCs live in the project namespace. `ScopeDOPE_SDLC.md` is at `ScopeDOPE/03_-_Confidential/ScopeDOPE_SDLC.md`.

#### `Security/`

Corporate information security policy suite, incident records, and the vendor security review template.

**Belongs here:**
- The master `CBB_Information_Security_Policy.md` and all subordinate security policies
- `Incidents/` — post-incident review documents (`YYYY-MM-DD_<brief-description>.md`)

**Note:** The vendor Security Review template lives at `Infrastructure/Security_Review_Template.md`. Completed vendor reviews live within each vendor's `Infrastructure/<domain>/` subdirectory.

#### `Style_Guides/`

Internal CBB style and standards guides governing how all work is produced. These are corporate standards — they apply to all products.

| Guide | Covers |
|---|---|
| `CODING_STYLE_GUIDE.md` | Kotlin/KMP naming, null safety, Compose conventions, architecture, testing, trade-secret guard |
| `TECHNICAL_DOCUMENTATION_GUIDE.md` | READMEs, runbooks, architecture references, API specs |
| `INTERNAL_WRITING_GUIDE.md` | Commit messages, Jira tickets, Confluence pages, Slack, session handoff docs, units |
| `BRAND_LEGAL_LANGUAGE_GUIDE.md` | Product names, trademark symbols, domain rules, phone numbers, CBOSL attribution, NDA requirements |
| `UI_DESIGN_STYLE_GUIDE.md` | Color tokens, typography, component specs, spacing |

### `CBB_Corporate/04_-_Highly_Confidential/`

Reserved for corporate-level trade secrets and IP when they arise. Currently empty.

---

## ScopeDOPE/

### `ScopeDOPE/01_-_Public/`

| Folder | Contents |
|---|---|
| `DOPE_Format_Spec/` | Public-facing `.dope` file format specification |
| `Logos_and_Wordmarks/` | Approved ScopeDOPE logo files and wordmarks cleared for external use |

### `ScopeDOPE/02_-_General/`

| Folder | Contents |
|---|---|
| `Marketing_Assets/` | Finalized marketing collateral cleared for public distribution |

### `ScopeDOPE/03_-_Confidential/`

#### Lifecycle Rule — MANDATORY

Documents follow a lifecycle based on specificity:

1. **Exploratory / general strategic planning** → `Product_Strategy/`
2. **Decision made, targeted analysis or implementation underway** → move to the appropriate domain folder
3. **Superseded or replaced** → move to `Obsolete/` subdirectory within the originating folder — never delete outright

#### `Product_Strategy/`

General strategic planning, opportunity sizing, market analysis, and project briefs.

**Belongs here:**
- Project briefs and opportunity assessments (`CBB_BRIEF_*.md`, `CBB_PROJECT_BRIEFS_TOC.md`)
- Market analysis documents
- Business model explorations
- Roadmap planning documents

**Destination-on-graduation tag — MANDATORY for `CBB_BRIEF_*`.** Every project brief stages here while it is concept-stage, regardless of whether the venture is ScopeDOPE-specific or company-level. To make the *eventual* home explicit from the start, each brief's header must declare a **Destination** field — where the brief moves when it graduates from concept (lifecycle stage 2):

- **`Destination: ScopeDOPE feature`** — the concept is a feature, module, or extension of the ScopeDOPE product itself. It will remain in the `ScopeDOPE/` namespace when implementation begins (moving to the appropriate `ScopeDOPE/03_-_Confidential/` domain folder, or into the engine/app repos). Examples: a ScopeDOPE module, a ScopeDOPE web companion, the `.dope` format/SDK.
- **`Destination: CBB_Corporate venture`** — the concept is a distinct company venture, product line, or service that is not part of the ScopeDOPE product. While the brief is concept-stage it stays here in `ScopeDOPE/03_-_Confidential/Product_Strategy/` alongside ScopeDOPE-destination briefs; at lifecycle stage 2 (decision made, implementation underway) it moves directly to the appropriate `CBB_Corporate/03_-_Confidential/` domain folder for the work (e.g., `Infrastructure/<domain>/`, `Legal_and_Trademarks/`) or to a new top-level namespace if the venture warrants one. There is no `CBB_Corporate/03_-_Confidential/Product_Strategy/` parking folder — concept-stage briefs of every destination live in the single `ScopeDOPE/03_-_Confidential/Product_Strategy/` until they graduate. Examples: a separate app/SaaS, a B2B data/licensing business, consulting services.

The tag records intent only — it does **not** move the file. Files move only at lifecycle stage 2 (decision made / implementation underway), per the Lifecycle Rule above. The TOC (`CBB_PROJECT_BRIEFS_TOC.md`) carries the same Destination in its summary matrix so the whole portfolio's intended split is visible at a glance.

#### `Design/`

In-progress design assets and UI work not yet cleared for public release.

**Belongs here:**
- UI mockups and wireframes (unreleased) — `Design/UI_Mockups/`
- UX research and design exploration

**Does not belong here:**
- Finalized ScopeDOPE brand assets → `ScopeDOPE/01_-_Public/Logos_and_Wordmarks/`
- Finalized CBB Corporate brand assets → `CBB_Corporate/01_-_Public/Logos_and_Wordmarks/`

### `ScopeDOPE/04_-_Highly_Confidential/`

Trade secrets and proprietary ScopeDOPE IP. Strictest access controls.

| Folder | Contents |
|---|---|
| `Engine_Documentation/` | Ballistics engine white papers, validation reports, internal engineering docs |
| `Marketing_Guide/` | Proprietary go-to-market strategy and messaging guidance |
| `SPEC/ScopeDOPE/` | The four ScopeDOPE SPEC files — sole authoritative product specification (`SPEC.md`, `SPEC_data_engine.md`, `SPEC_features.md`, `SPEC_nonfunc_appendices.md`) |

**Rule:** Never quote contents of any `03_-_Confidential/` or `04_-_Highly_Confidential/` folder in public channels, commit messages, issue tracker comments, or any externally visible context.

---

## CBB_Sign/

### `CBB_Sign/01_-_Public/`

| Folder | Contents |
|---|---|
| `Logos_and_Wordmarks/` | Approved cbb-sign logo and brand assets cleared for external use (placeholder — populated when branding is defined) |

### `CBB_Sign/02_-_General/`

General internal documentation not rising to Confidential classification. Currently empty.

### `CBB_Sign/03_-_Confidential/`

#### `CBB_Sign_SDLC.md`

The cbb-sign project SDLC — extends `CBB_SDLC.md`. Registered in the master SDLC §1 table.

#### `Infrastructure/`

**Project-level** infrastructure planning for cbb-sign — currently the LOE only.

| File | Contents |
|---|---|
| `CBB_Sign_LOE.md` | Level of effort estimate — component breakdown, hour estimates, open items |

> **The operational infrastructure doc set lives elsewhere.** The as-built/operational cbb-sign infrastructure documents — Architecture Reference, Operating Runbook, Rebuild Guide, Acquisition Brief, and the Cost-Impact Analysis — live under `CBB_Corporate/03_-_Confidential/Infrastructure/CBB_Sign/`, alongside every other operational infrastructure domain (Azure, DocuSeal, M365, …), per the CLAUDE.md Operational Domain Documentation Structure. This keeps all "run the business" infrastructure in one place for due diligence. The `CBB_Sign/` namespace holds the **product** artifacts (SDLC, SPEC) and the project **LOE**; the corporate `Infrastructure/CBB_Sign/` directory holds the **operational** infra docs.

### `CBB_Sign/04_-_Highly_Confidential/`

#### `SPEC/`

The cbb-sign product specification — four files: `SPEC.md` (master — overview, scope, RBAC, functional requirements, architecture, target infrastructure), `SPEC_workflow.md` (signing workflows), `SPEC_api.md` (API contract), `SPEC_audit.md` (audit trail, identity, WORM immutability).

---

## Namespace Separation — MANDATORY

**The three top-level namespaces (`CBB_Corporate/`, `ScopeDOPE/`, `CBB_Sign/`) must never be commingled.** This rule applies at every level of the folder hierarchy.

- A file belonging to one namespace must never be placed under another.
- A folder must never contain a mix of assets from different namespaces — not even as subdirectories. The top-level namespace split is the sole namespace boundary; do not recreate it internally.
- When an asset type exists in multiple namespaces (e.g., logos, marketing), each namespace has its own parallel folder. Never consolidate them into a single shared folder under any namespace.
- If an asset serves multiple namespaces, it must be placed under `CBB_Corporate/` (corporate-level assets govern all products) and cross-referenced from the relevant product-namespace doc — never duplicated.

**Folders must be flat within their scope.** Do not create subdirectories that re-partition content by brand or product when the namespace already handles that separation. For example, `Logos_and_Wordmarks/` inside `CBB_Corporate/` holds CBB logos flat — no `CBB/`, `ScopeDOPE/`, or `CBB_Sign/` subdirectory inside it.

---

## Adding New Folders

Before creating any new folder under any namespace or tier:
1. Determine which namespace it belongs to (`CBB_Corporate/`, `ScopeDOPE/`, or `CBB_Sign/`)
2. Determine the correct tier based on data classification
3. Confirm it does not belong in an existing folder
4. Confirm it does not violate the namespace separation rule above
5. Update this document — add the folder to the appropriate section
6. Update `CLAUDE.md` — update the OneDrive table in the Working Directory Boundary section

---

## Document Control

| Field | Value |
|---|---|
| **Document owner** | `jschwefel@coldboreballisticsllc.com` |
| **Classification** | Confidential (03_-_Confidential/) |
| **Location** | `OneDrive/CBB_Corporate/03_-_Confidential/ONEDRIVE_ORGANIZATION_GUIDE.md` |
| **Cross-references** | — |
| **Created** | 2026-06-07 |
| **Last updated** | 2026-06-13 |
| **Next full review due** | 2027-06-07 |

---

## Revision Control Block

| Rev | Date | Changed By | Reviewed By | Approved By | Summary |
|-----|------|------------|-------------|-------------|---------|
| 0.9 | 2026-06-07 | jschwefel | — | — | Initial release |
| DRAFT | 2026-06-09 | Claude (Opus 4.8) | — | — | Added "Destination-on-graduation" tag convention for `CBB_BRIEF_*` to the `Product_Strategy/` section: each brief declares whether it graduates to a ScopeDOPE feature or a CBB_Corporate venture, recording eventual namespace intent without moving the file (move still occurs only at lifecycle stage 2). Applied ™ to first use of Cold Bore Ballistics. |
| DRAFT | 2026-06-12 | Claude Code | — | — | Added `cbb-sign/` top-level namespace (new product); updated SPEC path to `SPEC/ScopeDOPE/` (subdir added 2026-06-12); added full `cbb-sign/` section with tier structure and doc inventory. |
| DRAFT | 2026-06-12 | Claude Code | — | — | Added `Financial_Records/Receipts/` subsection documenting CBB/YYYY and ScopeDOPE/YYYY subfolder structure, naming convention, and PDF co-storage note. |
| DRAFT | 2026-06-12 | Claude Code (Opus 4.8) | — | — | Resolved an SDLC↔guide inconsistency on cbb-sign infra-doc location: added `cbb-sign/` to the corporate `Infrastructure/` subdirectory table (operational infra doc set lives there, matching DocuSeal and the Operational Domain Documentation Structure); clarified the `cbb-sign/` namespace `Infrastructure/` holds only the project LOE; listed the four written SPEC files. |
| DRAFT | 2026-06-12 | Claude Code (Opus 4.8) | — | — | Added `Financial_Records/Startup_Programs/` subsection: holds one `*_Application.md` package per startup credit/accelerator program (Claude for Startups, Microsoft Founders Hub, Claude for Open Source); noted Jira mirroring under the CBB Epic and award-logging convention. |
| DRAFT | 2026-06-13 | Claude Code (Opus 4.7) | — | — | Renamed cbb-sign OneDrive namespace root `cbb-sign/` → `CBB_Sign/` (PascalCase-underscore for filesystem-stable namespace; project name "cbb-sign" remains lowercase in prose and as the GitHub-repo grouping dir). Updated Namespace Separation rule to enumerate all three namespaces. Updated Adding New Folders step 1. Cleaned residual `cbb-sign/` prose references that meant the OneDrive root. |
| DRAFT | 2026-06-13 | Claude Code (Opus 4.7) | — | — | Consistency audit: standardized cbb-sign OneDrive namespace casing to `CBB_Sign/` throughout (top-level table line 21, Infrastructure subdir table, namespace section header and tier headings) — matches actual filesystem casing and CLAUDE.md line 150 clarification (repo grouping dir is lowercase `cbb-sign/`; OneDrive docs namespace is PascalCase `CBB_Sign/`). Added `Sentry/` to the Infrastructure subdirectories table (was present on filesystem but undocumented). Updated `Atlassian/` description to reflect Jira Software primary use (DOPE, CBB) and ESUP/JSM decommissioning. Added `App_Store_Release_Runbook.md` to the `Process/` "Belongs here" list (added to filesystem 2026-06-12). |
| DRAFT | 2026-06-13 | Claude Code (Opus 4.7) | — | — | Resolved Lifecycle-Rule contradiction: the `Destination: CBB_Corporate venture` rule previously pointed graduating briefs to `CBB_Corporate/03_-_Confidential/Product_Strategy/`, a folder that does not exist. Rewrote the rule so all concept-stage briefs (both ScopeDOPE-destination and CBB_Corporate-destination) live in the single `ScopeDOPE/03_-_Confidential/Product_Strategy/`, then move directly to the appropriate CBB_Corporate domain folder (or a new top-level namespace) at lifecycle stage 2 — no `Product_Strategy/` parking folder is created in `CBB_Corporate/`. |
