# Local Artefact Recovery — SSH Retrieval from Rocky's Laptop

## When to use this

Rocky mentions a job that returns no search results in the VPS vault or Airtable. The job exists in his mental model and on his local machine, but has not been synced to the VPS. This is a common pattern — Rocky works from his laptop and only pushes to the vault periodically.

## Step 1 — Ask the right unlock question first

**Never say:** "That job doesn't exist."
**Say:** "I don't have that in the vault yet — what's the client name?"

The client's name is the fastest path to the correct folder on his machine.

## Step 2 — SSH to laptop

```bash
ssh -i /root/.ssh/id_hermes_ed25519 mclou@laptop-cd8df7fs
```

**Credentials:**
- User: `mclou` (Windows Administrator account — NOT root)
- Key: `/root/.ssh/id_hermes_ed25519`
- Tailscale hostname: `laptop-cd8df7fs` (100.108.207.15)
- Note: Tailscale SSH (`tailscale ssh`) does NOT work on Windows hosts — use plain SSH via Tailscale hostname

**Typical artefact locations on laptop:**
```
C:\Users\mclou\lfcs-inbound-artefacts\   ← incoming RFIs, drawings, emails
C:\Users\mclou\Downloads\                ← recently downloaded drawings
C:\Users\mclou\Google Drive\             ← mapped SharePoint/Google Drive sync
```

## Step 3 — Find and pull artefacts

```bash
# List inbound artefacts (new job packages land here first)
ls "C:\Users\mclou\lfcs-inbound-artefacts\"

# Search by client name or job number
find "C:\Users\mclou\lfcs-inbound-artefacts" -iname "*liverpool*"
find "C:\Users\mclou\lfcs-inbound-artefacts" -iname "*tca*"
```

## Step 4 — Create vault entry

Once artefacts are located, create the job folder in the VPS vault:

```bash
# New job folder structure (per lfcs standards)
mkdir -p "/home/ccuser/opsman-work/Jobs/Ongoing Jobs/<job>/"
# Create 00-brief.md at job root with type, client, contract details
# File artefacts to the appropriate numbered subfolder per folder-spec.md
```

## Step 5 — Log the gap

Append to daily diary:
```
## HH:MM — hermes — [Job] vault gap found + recovered
- Job not in VPS vault — artefacts retrieved from laptop via SSH
- Client: [name]
- Job type: [price/dayworks/hybrid]
- Action: folder created, artefacts filed
```

## Why this matters

Rocky works from his laptop. The VPS vault is a mirror that lags reality by up to several days. A job that "doesn't exist" in the vault may be actively running on site right now. The gap is a data sync problem, not a job existence problem. Never treat it as the latter.