# Claude Code Context — grip-docs

Standing context for Claude Code sessions working in this repository.

## What this repo is

`grip-docs` is the **strategic documentation repo** for the Grip Cannabis Platform project at OCG. It is owned by Rich Stopczy (IT manager) and used as Claude's working surface for planning, drafting, and refining project documentation.

It is **not** the code repository for the platform itself. There are no application sources here — only markdown.

## Project context — Grip Cannabis Platform

- **Product:** a custom in-house cannabis ERP being built to replace and consolidate prior tooling.
- **Codename:** **PLATO** (the platform itself).
- **Modules:** named with the **Grip** prefix (e.g. Grip-* modules sit on top of PLATO).
- **Goal:** end-to-end ERP coverage for OCG's cannabis operations — cultivation through distribution and finance — under one custom-built system instead of stitched-together third-party tools.

When writing or editing docs, treat **PLATO** as the platform and **Grip-\<X\>** as a module name. Don't conflate the two.

## Grip modules

The Grip-* modules sit on top of PLATO. Each is owned by one or more
Grip team members:

| Module | Function | Primary owner(s) |
|---|---|---|
| **GripGrow** | Cultivation | Corey |
| **GripReach** | Marketing | Christine, Joe G, Corey |
| **GripLedger** | Cost collector | Miko, Dennis |
| **GripTime** | Labor / uAttend | Miko, Laura, Logan |
| **GripPlan** | Budget + forecast | Miko, Dennis |
| **GripAdmin** | Compliance / audit / licenses / IT-SOP / LARA | Dennis |
| **GripPartner** | Processing | Joe G |
| **OpsHelpers** | Production | Dennis |
| **GripCommand** | Leadership dashboard (output destination) | — |
| **PLATO** | Data integration server | Rich |

When a doc references a module, the owner above is the relevant
contact unless otherwise stated.

## Team structure

The enterprise dev team is **17 people** total, organized into four
subgroups:

| Subgroup | Count | Role in the project |
|---|---|---|
| **IT** | 3 | Rich's group — infrastructure, tooling, AI enablement, cross-cutting concerns. Includes Rich (IT manager) and 2 others. |
| **OCG** | 6 | Operations side — internal business owner, defines requirements |
| **Grip** | 6 | Product / platform engineering — builds PLATO and the Grip modules. Members: Dennis, Corey, Joe G, Christine, Logan, Miko |
| **Axon** | 2 | Partner / contractor engineering capacity |

**Cross-company contributors:** 3 of the 17 work across multiple
companies; the remaining 14 work within their respective company only.

When a doc references "the team," confirm which subgroup is meant
before assuming. Decisions often live with a specific subgroup, not
the whole 17-person org. For Grip module questions specifically, see
the "Grip modules" section above for ownership.

## How documents are organized

```
docs/        Strategic / planning documents — ARCHITECTURE, ROLLOUT,
             PHASE-1-AWS-SETUP, TOOLS_MATRIX, MEETING_PREP, etc.
             Filename convention: SCREAMING_SNAKE_CASE.md

reference/   Captured knowledge from Claude conversations. Reusable
             research, not living planning docs.
   ai-tooling/      Anything Claude/Cursor/Copilot/MCP-related
   github/          GitHub setup, Actions, org policy
   linear/          Linear configuration, workflows
   infrastructure/  AWS, networking, identity, anything platform-ops
             Filename convention: kebab-case.md
```

If a piece of writing is a **decision or plan**, it belongs in `docs/`. If it's **research or captured how-to**, it belongs in `reference/<category>/`. If unsure, ask before placing.

## Where docs live across repos

This repo (`grip-docs`) is one of three strategic doc repos in the
enterprise:

| Repo | Content |
|---|---|
| `ocg-ai-grip/grip-docs` | Grip Cannabis Platform — project status, architecture, rollout, Grip-specific decisions, Grip team context |
| `ocg-ai-it/it-docs` | IT department — IT runbooks, IT-managed infrastructure decisions, IT project documentation, IT strategy |
| `ocg-ai-shared/shared-docs` | Enterprise-wide standards — DevOps setup guides, GitHub/Linear conventions, coding standards, anything any dev at any OCG company needs |

**Test for placement when writing a new doc:** if it changes, who
needs to know?
- Only Grip team → here in `grip-docs`
- Only IT folks → `it-docs`
- Anyone in the enterprise → `shared-docs`

Workstation setup, GitHub onboarding, and similar developer-facing
infrastructure docs live in `shared-docs` because they apply to all
17 enterprise developers, not just Grip.

## How to approach edits

These rules apply to every Claude Code session in this repo.

### Repo location on disk

This repo is cloned at `C:\Users\<username>\Code\grip-docs` on Rich's
machine. **Git repos at OCG should NOT be cloned into OneDrive-synced
folders** (Documents, Desktop, etc.) — Git and OneDrive create
sync conflicts and corrupt repo state. If Claude Code suggests a
file path, default to relative paths within the repo rather than
absolute paths.

### Preserve formatting carefully
- **Tables especially.** Many of these docs are read in rendered form (Cursor preview, GitHub, sometimes pasted into meeting decks). If a markdown table has aligned columns with padding spaces, keep the alignment when editing a cell — don't collapse it. If you add a row, match the column widths.
- Don't reflow paragraphs that are already wrapped at a specific width unless the user asks. Keep line breaks where they are.
- Heading levels, bullet styles (`-` vs `*`), and ordered-list numbering should match the surrounding document.

### Show diffs before committing
- **Never commit unprompted.** Even for tiny doc tweaks, the user reviews changes in Cursor before they hit git.
- When you finish an edit, surface what changed (which file, which section). The user will commit when ready.
- If asked to commit, write a descriptive message and confirm before pushing.

### Be conservative with structural changes
- Don't rename files, reorganize folders, or rewrite headings without asking. The structure here is deliberate.
- New documents are welcome — propose the filename and location first.

### Tone of the docs
- These are internal strategic docs for a senior IT/eng audience. Crisp, declarative, decision-oriented. No marketing voice, no filler.
- Acronyms (PLATO, OCG, Grip, Axon) can be used without expansion within docs — the audience knows them.

## What to do if you're unsure
Ask. The cost of a clarifying question is much lower than a doc edit that has to be reverted because it broke a table or changed a decision the user already made.