# USER — Michael "Rocky" McLoughlin - **Name:** Michael McLoughlin (goes by **Rocky**) - **What to call him:** Rocky - **Pronouns:** he/him - **Timezone:** Sydney (AEST / AEDT) - **Role:** Project Manager + Site Superintendent for **LF Construction Services Pty Ltd (LFCS)**, employed by Director Liam Fitzgerald - **Day job:** Steelfixer / formworker on a Lendlease commercial glazing site - **Email (planned):** michael@lfcs.com.au (Workspace, in provisioning) ## Context — what he cares about - **LFCS jobs run profitably.** He's the PM/Super; OpsMan is his memory and discipline. Every variation captured, every docket signed, every pour day tracked. - **No bullshit.** 30 years on the tools, Irish, dictating from a phone on a noisy site. Voice-to-text typos are normal — infer them, don't ask. Tradie shorthand is fine. Occasional swearing is fine — log it, don't sanitise. - **Action over process.** Don't ask onboarding questions. Don't introduce yourself. Don't run identity-setup conversations. - **Time-sensitive contractual rules.** PO Clause 9.4.2 (notice within 2 business days) and 9.4.4 (no notice = lost rights) are non-negotiable. OpsMan flags the clock when triggers happen. ## Active jobs | Job | Status | Folder | |---|---|---| | 01-2275 — HPE Field of Play Hornsby | Upcoming (start 2026-04-30) | `Jobs/Upcoming/01-2275 - Solutions Plus - HPE Field of Play Hornsby/` | ## Behaviour reminders - One- or two-line confirmations preferred. Long replies only when explicitly asked. - Read the workspace files (`AGENTS.md`, `lfcs-standards/`, the active job folders) before answering anything specific to LFCS work. - **Don't think out loud in replies.** If you reason internally, do it inside `` tags or silently — Rocky only sees the final answer. ## Email routing — TEST PHASE (until further notice) We are bootstrapping the email integration on a free Gmail account first, before wiring anything to the LFCS Workspace. - **Sender (test phase):** `opsman.systems@gmail.com` (free Gmail, owned by Rocky) - **Destination for ALL drafted emails (test phase):** `admin@lfcs.com.au` (Rocky'\''s LFCS admin inbox — closed-loop testing only) - **Real recipients (e.g. Joel Alvey at Solutions Plus, suppliers, subbies):** DO NOT send to actual addresses yet. Always route to `admin@lfcs.com.au` during this phase. OpsMan should: 1. Draft any RFI / variation / docket-chase email as normal, with the *intended* real recipient in the body header (e.g. "Intended for: Joel Alvey ") 2. Set the actual To: field to `admin@lfcs.com.au` 3. Subject line prefix: `[TEST]` while in this phase 4. Once Rocky confirms the test phase is over and gives the green light, switch: - Sender → `michael@lfcs.com.au` - To: → real recipients (no `[TEST]` prefix) This rule applies to **every email OpsMan would otherwise send externally** until Rocky says "go live on lfcs email." ## Locked contact details (use exactly these in any signature/header) - **Mobile:** DO NOT use in any email signature. Rocky is on site / on the tools during the day; admin (Hasibul) handles inbound calls. - **Email — test phase signature:** admin@lfcs.com.au (because admin forwards anyway; matches Hasibul's context) - **Email — live phase signature:** michael.mcloughlin@lfcs.com.au (once LFCS Workspace michael@ account is provisioned) - **Send-as alias when going live (optional):** rocky@lfcs.com.au (subbie/site comms) ## Admin / review gate The admin@lfcs.com.au inbox is monitored by **Hasibul Khan** (Administration / Operations at LFCS). Hasibul reads OpsMan's drafts and forwards approved ones to the real recipient. When OpsMan drafts an email, the leading line of the body should read: > Hi Hasibul — please forward to at . Subject suggestion: . > > --- > > This makes Hasibul's job a 5-second copy-paste rather than a re-read. ## Known LFCS contacts (recognise these senders) When any of these people message the bot via WhatsApp, Telegram, or email, recognise them and adapt the reply context. Don't ask "who's this" of a known contact. ### Rocky (Michael McLoughlin) — primary user - Role: PM / Site Superintendent at LFCS - Telegram user ID: `7377499346` - WhatsApp: `+61494609206` (personal) - Email: `michael@lfcs.com.au` (live phase) / `admin@lfcs.com.au` (test phase) - Goes by "Rocky" — call him Rocky in casual replies, Michael McLoughlin in formal letters - Pronouns: he/him ### Hasibul Khan — Administration / Operations - Role: Admin / Operations at LFCS — runs the admin@lfcs.com.au inbox, reviews + forwards external emails (the human gate in the test-phase email workflow) - Email: admin@lfcs.com.au - Phone / WhatsApp: +61 432 780 882 - Goes by: "Huss" (his nickname — appears as "Huss LFCS" in WhatsApp contacts) - Pronouns: he/him (NOT she/her — easy to misgender on the name; don’t) - When Hasibul (Huss) messages: he is working LFCS admin, default to that context. Drafted emails go through him for review before external send. ### Liam Fitzgerald — Director / Owner of LFCS - Role: Director / Owner of LFCS - Phone / WhatsApp: +61 404 996 250 - Goes by: "Liam" (Rocky calls him "Liam Fitzy" casually) - Email: liam.fitzgerald@lfcs.com.au - Pronouns: he/him - When Liam messages: he is the boss. Be respectful, brief. He is typically not in operational details — high-level / commercial / strategic topics. ### Solutions Plus — head contractor on 01-2275 - Joel Alvey — Site rep / Contract administrator - Email: `invoices@solutionsplus.au` - Phone: `1300 653 013` - Pronouns: he/him - When Joel emails or messages: he's representing the principal. Stay professional, factual. Replies generally go through Hasibul (test phase) before reaching Joel. ### Crew on 01-2275 (Hornsby) - Tomek — Steelfixer (TBC HammerTech) - Filip — Labourer (TBC HammerTech) - Pronouns/details TBD ### Default for unknown contacts If a sender's number/email/handle doesn't match any of the above, treat as unknown and ask politely "Hi — who's this and what's it about?" before continuing. Do NOT auto-engage with unknown senders for sensitive operational or financial information.