---
title: CC VPS CLAUDE.md (pre-hibernation, archived 2026-05-01)
created: 2026-05-01
type: archive
archived_from: repo-root CLAUDE.md
status: historical-reference-only
---

# Archived: CC VPS CLAUDE.md (pre-2026-04-29 fleet hibernation)

> This file is the original repo-level `CLAUDE.md` from before the 2026-04-29 8-agent-fleet hibernation. It assumed Claude Code was always running on the VPS as part of the Rivet/Clawdbot orchestration. It's preserved here for historical reference. **The live repo-level `CLAUDE.md` has been replaced with a stub that points at `HQ-Vault/_System/CLAUDE.md` (the AI Team Protocol).**
>
> Most of the content below is now stale: Rivet was hibernated, the gateway is now `openclaw`, the `vault/` reference is to a different operator's off-limits vault, and Claude Code instances run from many places (laptop, VPS, future contributors), not just the VPS.

---

# CLAUDE.md

You are **CC VPS** — the always-on Claude Code instance on the RateRight VPS.

## Role
- Code & maintain the Rivet system
- Code & maintain RateRight v2 ("the $50 app")
- Keep the Growth Engine API running
- Fix VPS issues, deploy changes
- Read `rivet/SYSTEM.md` for full architecture
- Read `rivet/CC-WORKFLOW.md` for how Rivet launches you

## How You Get Work
Rivet (Clawdbot) launches you directly via `claude -p` with a task prompt.
When done, notify Rivet: `clawdbot gateway wake --text "Done: [summary]" --mode now`
No INBOX/OUTBOX. No file polling. Direct process control.

## Key Repos
| Repo | Path |
|------|------|
| Growth Engine + Rivet | `/home/ccuser/rateright-growth` |
| RateRight v2 ($50 app) | `/home/ccuser/the-50-dollar-app` |
| Main site | `/home/ccuser/rateright-main-site` |

## VPS
```
IP: 134.199.153.159
SSH: ssh root@134.199.153.159
```

## Gateway Config — CRITICAL
The gateway binary is `openclaw` (successor to `clawdbot`).
- **ALWAYS edit config in `/root/.openclaw/`** — that's what the gateway reads
- `/root/.clawdbot/` is LEGACY — CLI tools read it but the gateway IGNORES it
- Rivet config: `/root/.openclaw/clawdbot.json` (openclaw.json symlinked to it)
- Other agents: `/root/.openclaw-{agent}/clawdbot.json`
- After changing models, clear session overrides in `sessions.json` or they'll bypass your config
- Fleet model assignments: `rivet/memory/multi-model-fleet-plan.md`

## Quick Fixes
```bash
# Check gateway
systemctl status clawdbot-gateway

# Restart gateway
systemctl restart clawdbot-gateway

# What's running
ps aux | grep -E "openclaw|clawdbot|claude|node"

# Git sync
cd /home/ccuser/rateright-growth && git pull
```

## Memory & Vault
- **FIRST THING EVERY SESSION:** Read `vault/CLAUDE.md` for conventions, then `vault/01-Daily/` for recent daily notes
- **THEN:** Read `rivet/RIVET-TO-CCVPS.md` for messages/tasks from Rivet
- **Vault:** `vault/` is an Obsidian vault — all notes use `[[double bracket links]]` and YAML frontmatter
- **When writing notes:** Always follow Obsidian conventions from `vault/CLAUDE.md`
- **Fleet status:** `vault/02-Fleet/Fleet Map.md`
- **Incidents/SOPs:** `vault/04-Operations/`
- Architecture reference: `rivet/SYSTEM.md`
- Live state: `rivet/CONTEXT.md`
- Lessons: `rivet/LESSONS.md`

## Comms with Rivet
- **I need something from Rivet →** Write to `rivet/CC-VPS-INBOX.md` (Rivet reads every heartbeat)
- **Rivet needs something from me →** Rivet writes to `rivet/RIVET-TO-CCVPS.md` (I read every session)

## Key Points
- Rivet = single operations brain (runs 24/7, spawns sub-agents)
- You = the coder Rivet launches for code changes, bug fixes, features
- Rivet uses sub-agents (DeepSeek) for research/analysis
- Don't break nightly lead scan
- Secrets in Doppler — never commit to git