# TCE Liverpool — Artefact Recovery Log

**Date:** 2026-05-11
**Session:** 08:51–09:56 AEST
**Trigger:** Rocky asked "TCE Liverpool" for P&L check — job not in VPS vault, laptop closed

---

## What we know

- **Client:** TCE Contracting (Kirolos Barsom — kbarsom@tcecontracting.com.au)
- **Location:** Liverpool NSW
- **Type:** dayworks (per context: crew held up 3hrs waiting on another contractor)
- **Status:** active on site, crew waiting
- **Issue:** 3hr delay at cost — ground worker wasn't ready when crew arrived

---

## Why it's not in the vault

Rocky says job is on shared Drive or his laptop. Laptop is currently closed (lid shut / sleep). VPS vault has no TCE Liverpool entry. Airtable Jobs table (LFCS-Operations base) has no Liverpool entry either.

---

## Protocol used

1. Search VPS vault for "TCE", "Liverpool", "TCA" → nothing
2. Check Airtable Jobs table → 6 records, none match Liverpool or TCE Liverpool
3. SSH to laptop → interrupted / timed out — laptop confirmed closed by Rocky
4. Fallback: acknowledge gap, capture what we know, flag for reconciliation when laptop reopens

---

## Next steps (when laptop is back online)

1. SSH to `mclou@laptop-cd8df7fs`
2. Check `C:\Users\mclou\lfcs-inbound-artefacts\` for TCE/Liverpool folder
3. Also check Google Drive local sync: `C:\Users\mclou\Google Drive\` or `C:\Users\mclou\My Drive\`
4. If found: create vault entry at `Jobs/Ongoing Jobs/26XX - TCE - Liverpool [project name]/`
5. Pull 00-brief.md → type, contract_price, start_date
6. Log delay event in 07d - Daily Diary

---

## Questions to ask Rocky when he's on the laptop

- What is the exact job name / project title in the folder?
- What's the LFCS job number (26xx format)?
- Is there a 00-brief.md or any pricing doc in the folder?
- Are there signed dockets for today (need to capture the 3hr delay at cost)?

---

## Lessons learned

- "TCE Liverpool" = location+client identifier, not formal job name
- Laptop-closed SSH timeout is a distinct failure mode from network unreachable
- Protocol: acknowledge closed → log what we have → surface questions → move on, don't retry

---

## Update — 2026-05-11 09:00–11:30 AEST

### Crew on site
- **Steel crew:** Steve + apprentice — tied steel mat, raked square for lifting
- **Shutter crew:** Donald "Boss" Murphy + apprentice — shutters
- **Rocky** on tools supervising

### Day's events
- 07:00 — LFCS crew on site, ground workers not ready (promised ready in 2hrs)
- 07:00–09:30 — **3hr idle hold** (at LFCS dayworks cost — billable if docket signed)
- 08:30 — Steel mat ready (laid out, tied, raked square — 2 lads, ~1.5hrs)
- 09:30 — Heavy rain, crew knocked off for breakfast
- ~10:15–11:00 — Returned, finished rebar prep (45min, 2 lads)
- 11:01 — Ground workers still not ready; foreman confirmed **"on dayworks for the day"**

### Photos captured
| File | Description |
|---|---|
| `img_d08dec5f80cf.jpg` | Steel mat — tied, raked square, ready at 08:30 |
| `img_c623276cb01d.jpg` | Rebar prep — completed after rain, ~10:15–11:00 |
| `img_d977d96e260f.jpg` | Pour in progress — workers placing concrete |

### Open items
- [ ] Job number — ask Liam / check laptop when reopened
- [ ] Signed docket for today's dayworks (3hr delay + rain stoppage)
- [ ] Google Workspace connection — tonight after hours (~17:00–18:00)
- [ ] EOD report compiled as Google Doc with photos inline

### Key protocol notes
- Dayworks confirmation from site foreman ("on dayworks for the day") locks in billing basis — log as the event, docket is the proof
- When Rocky says "compile the daily report" at EOD: use `eod-google-doc-report.md` — Google Doc with photos, not markdown fallback
- Photos sent via Telegram are sufficient input for EOD report; no camera app needed on Hermes side