# grip-docs

Strategic documentation for the **Grip Cannabis Platform** project at OCG.

This repository captures planning, architecture, rollout strategy, tooling decisions, and reference knowledge for the in-house cannabis ERP build (codename **PLATO**, with Grip-named modules). It is a markdown-only knowledge base — not a code repository.

## Who this is for

- **Rich Stopczy** (IT manager, OCG) — primary owner, uses this repo to drive enterprise dev planning.
- **Claude assistants** — Anthropic's Claude Code sessions use this repo as context when helping with documentation, planning, and meeting prep.
- The broader enterprise dev team (Grip, OCG, Axon, IT subgroups) as reference reading.

## Layout

```
.
├── README.md          You are here
├── CLAUDE.md          Standing context for Claude Code sessions
├── docs/              Strategic / planning documents
│                        ARCHITECTURE, ROLLOUT, PHASE-1-AWS-SETUP,
│                        TOOLS_MATRIX, MEETING_PREP, etc.
└── reference/         Captured knowledge from Claude conversations
    ├── ai-tooling/
    ├── github/
    ├── linear/
    └── infrastructure/
```

## How to use it

- **Working with Claude Code:** open this folder in Cursor or the Claude Code CLI. The `CLAUDE.md` file is automatically loaded as context, so the assistant already knows the project, team, and conventions.
- **Adding a new strategic doc:** drop a markdown file into `docs/` with an `ALL_CAPS_NAME.md`.
- **Capturing reference knowledge:** if Claude produces useful research in a conversation (e.g. a comparison of CI tools), save it under the matching `reference/<category>/` subfolder so it's reusable later.
- **Editing existing docs:** preserve table formatting and column alignment carefully — many docs are reviewed in rendered form.

## Conventions

- Markdown only. Source-of-truth Word/Excel exports are kept elsewhere; do not commit `.docx` or `.xlsx` here.
- Filenames: `SCREAMING_SNAKE_CASE.md` for strategic docs in `docs/`, `kebab-case.md` for reference notes.
- Commits should be reviewed before pushing — this repo is a record, not a scratchpad.