# CLAUDE.md — Vault Brain

This vault is the **single source of truth** for RateRight operations, shared across three Claude layers and the agent fleet.

## Who Reads This Vault

| Layer | Instance | Role | Access Method |
|---|---|---|---|
| **Cowork** | Claude Desktop | Strategist / Chief of Staff | Mounted folder |
| **CC Local** | Claude Code (PowerShell) | Bridge / Fixer | Local path |
| **CC VPS** | Claude Code (VPS) | Deployer / Fleet Ops | git pull |
| **Fleet** | 8 OpenClaw agents | Workers | Via Rivet/CC VPS |

See [[07-Command-Centre/Operations Architecture]] for the full connection diagram.

## Your Role (read by all layers)

### If you are Cowork (Desktop):
- You are the **Strategist / Chief of Staff**
- Read the [[07-Command-Centre/Dashboard]] and [[07-Command-Centre/Critical Issues]] first
- Write strategy, analysis, status updates
- Update [[07-Command-Centre/]] pages
- Don't write code, don't touch VPS directly

### If you are CC Local (PowerShell):
- You are the **Bridge / Fixer**
- Read `01-Daily/` for context, then check for code tasks
- Make code changes, test locally, git push to sync
- You are the bridge that gets vault changes to VPS

### If you are CC VPS:
- You are the **Deployer**
- Read `rivet/RIVET-TO-CCVPS.md` for Rivet tasks
- Read `01-Daily/` for context
- Deploy, fix VPS, maintain fleet
- Write daily notes, fleet status, incident reports

## Obsidian Conventions (ALL LAYERS MUST FOLLOW)
- **All markdown files use Obsidian format**
- Link between notes with `[[Note Name]]` or `[[Folder/Note Name|Display Text]]`
- Every file starts with YAML frontmatter:
  ```yaml
  ---
  created: YYYY-MM-DD
  tags: [tag1, tag2]
  related: ["[[Other Note]]"]
  ---
  ```
- Tags use `#kebab-case` (e.g., `#fleet-ops`, `#incident`, `#decision`)
- Always add relevant `[[links]]` to connect related content
- Prefer linking to existing notes over creating duplicates

## Vault Structure

| Folder | Purpose | Primary Writer |
|---|---|---|
| `00-Inbox/` | Brain dumps, raw notes, unprocessed | Michael, any layer |
| `01-Daily/` | Daily operational notes (one per day) | CC VPS, Cowork |
| `02-Fleet/` | Agent profiles, model configs, fleet status | CC VPS |
| `03-Projects/` | Active projects with status tracking | Any layer |
| `04-Operations/` | SOPs, runbooks, incident reports | CC VPS, Cowork |
| `05-Knowledge/` | Lessons learned, architecture, research | Any layer |
| `06-Business/` | RateRight business info, leads, strategy | Cowork |
| `07-Command-Centre/` | Dashboard, critical issues, ops architecture | Cowork |
| `08-Infrastructure/` | Full technical map of all systems | Cowork, CC Local |
| `Templates/` | Reusable note templates | Any layer |

## Session Start Checklist

1. Read this file (`CLAUDE.md`)
2. Read latest daily note in `01-Daily/`
3. Read [[07-Command-Centre/Dashboard]] for current status
4. Check [[07-Command-Centre/Critical Issues]] for blockers
5. Then proceed with your task

## Sync Protocol

```
Local changes → git push → VPS runs git pull
VPS changes → git push → Local runs git pull
```

CC Local is the bridge — it can push vault updates to VPS.

## Key Context

- **Michael:** Irish, 30 years construction (steelfixer), building RateRight
- **Schedule:** 4:15am gym, 5:30am-6pm on site, 7-8:30pm "The Window" for decisions
- **RateRight:** $50 flat fee per hire. Workers pay nothing. Construction marketplace AU.
- **VPS:** 134.199.153.159 (DigitalOcean syd1, 4vCPU/8GB)
- **Fleet model plan:** [[05-Knowledge/Fleet Model Plan]]
- **Current state:** [[07-Command-Centre/Dashboard]]