# Hermes — LFCS Foreman Support Gap Analysis **Date:** 2026-06-27 **Trigger:** Rocky described the full vision for the foreman's pocket PM role. --- ## What Rocky described Hermes (me) is the foreman's pocket super: - PM + estimator + admin + engineer all in one - On the phone with the foreman every day - I make the job specs and pre-pour checklists (or foreman prints what I draft) - I hold the baseline schedule and progress schedule - I tell the foreman how to get back on track when behind - I answer scope questions instantly — in scope or not? - I draft the variation and send it immediately (48-hour clause) - When the foreman asks me something, I answer from the full job context --- ## What I currently HAVE **Available now (from vault + workspace):** - Rate card (dayworks rates, tier structure, rules) - LFCS folder spec (where everything is filed) - Job types (price / dayworks / hybrid) — per job brief - Contract terms known: PO Clause 9.4.2 (2 BD variation notice), 9.4.4 (no notice = lost rights) - All contacts (Rocky, Hasibul, Liam, Joel Alvey, crew) - Daily diary format - Variations and RFI register format - Job Tracker structure (hours, materials, costs, milestones) - Lessons learned index **Available on Rocky's laptop (not yet accessible to me):** - `gws` CLI with Gmail, Drive, Sheets, Calendar - Airtable base (LFCS-Operations) - Google OAuth credentials --- ## What's MISSING — the gaps ### Gap 1 — I have no contract documents I don't have the actual contracts, POs, or scope of works in my context. - Each job's `00-brief.md` has type + client + contract value - But the actual terms, payment schedule, retentions, deadlines, variation process, liquidated damages — I don't hold these - **Need:** `01-2275` (Hornsby HPE) PO terms at minimum. Can pull from job folder if it's filed. ### Gap 2 — I have no drawings or specs I can't answer "is X in scope?" without the drawings and specs. - 01-2275 IFC drawings are in the job folder at `03a - Issued for Construction/` - But I haven't read them and don't have a working index of what's in them - **Need:** Drawing index per job (what drawings exist, what each covers). File them. Read the key ones (structural, civil, architectural). ### Gap 3 — No programme / schedule I have no baseline programme to compare progress against. - Can't answer "are we behind?" or "how do we get back on track?" - **Need:** The programme (MS Project or whatever is filed). Even a PDF version I can reference. - When Rocky says "we're behind" — I need something to compare against. ### Gap 4 — Pre-pour checklist template doesn't exist yet Rocky said I make the pre-pour checklists. - There's no template in the vault - **Need:** Draft pre-pour checklist template for 01-2275 based on the job scope (HPE — concrete slab, possibly footings). Standard items: mix design confirmed, reinforcement inspected, formwork checked, cover spacers in place, site access confirmed, pump booked, weather OK, client rep confirmed on site, etc. ### Gap 7 — Email auth is broken Can't send variation notices, RFIs, or dockets by email. - Google OAuth token expired on opsman.systems@gmail.com - **Need:** Re-auth. Setup script at `/root/.hermes/skills/.archive/google-workspace/scripts/setup.py` ### Gap 8 — No Airtable access from Hermes The LFCS-Operations base (appE43UvTyARe5oJs) is wired for OpsMan, not Hermes. - **Need:** Either Hermes gets the PAT, or OpsMan's MCP is transferred. Rocky said "Opsman is no more — it's you now" — so this needs resolving. ### Gap 9 — No SMS / WhatsApp from laptop Rocky's WhatsApp bridge (OpenClaw) is set up but I haven't seen the status. - WhatsApp groups are read-only for me per rules. - 1:1 DMs work. - **Need:** Confirm WhatsApp bridge is live and I can receive Rocky's messages there. ### Gap 10 — Job status is unclear in my context - 01-2275 (Hornsby HPE) — status? Last seen as "Upcoming" with start date 2026-04-30. Are we on site yet? - 2626 (Mack Civil Stormwater) — status? Draft bid May 6, no outcome on record - 2629 Erskine Park — status? - **Need:** Current job status register. All jobs, their stage, what's in progress, what's at risk. --- ## What I'm ALREADY great at (no gap) - Capturing site notes, photos, hours, deliveries - Logging variations + RFIs immediately with the 48-hour clock - Tracking dockets (signed/missing) - Answering "what did I do Tuesday?" type recall questions - Routing "PM territory" work to Claude Code correctly - Maintaining the daily diary - Rate card calculations for dayworks --- ## Priority order to close the gaps 1. **Re-auth email** — so I can actually send variation notices (most commercially critical) 2. **File + index the Hornsby (01-2275) contract docs** — PO terms, scope, drawings list 3. **Get Airtable access** — job status, crew, tracker in one place 4. **Draft pre-pour checklist template** — put it in the job folder 5. **Get the programme** — even a PDF 6. **Clarify current job status across all jobs** --- ## Note on Claude Code coordination Rocky wants me and Claude Code working off the same page. The split from AGENTS.md: - **Me (Hermes):** capture, recall, remind, route, log - **Claude Code:** formal drafts, programme analysis, contract interpretation, reports For this to work: - My daily diary entries must be thorough enough for CC to draft from - Variations and RFIs I log must have enough context (date, trigger, dollar estimate) for CC to build a formal letter - CC should read `daily/{date}.md` every morning as its first context - CC should read the Variations register before drafting any commercial letter