User: Windows laptop 'Connie' (i5-1235U, 12GB). Hermes Desktop locally; heavy work → VPS 2.25.172.164 via Nous. PowerShell `PS C:\Users\Rob>`; admin to VPS via Hostinger web terminal. Build-mode work often stranded on Connie — ask which machine first. Cost-conscious on inference + tools; wants LIVE spend visibility — built a tray $ counter on Connie (runbook: windows-spend-tray-counter skill); leading spend signal = cache_read_tokens. Prefers SSOT designs and do-it-right over hacks.
§
'Flash' is ambiguous — clarify render flicker vs focus theft first.
§
Businesses: RRR (local-service SMB growth, Brighton CO, primary; "plug the leaks → add gas" model; social = Facebook), Pipeline Layer (B2B SaaS RevOps, separate — no cross-promo; social = LinkedIn), Job Seeker (inactive), OriginatorOS (mortgage vertical, parked; Rob's 1994–2008 brokerage = its credibility hook).
§
Social posts: Rob approves final text before anything saves to planner — show full post, wait for his go. PL LinkedIn: CTA line directly above any link.
§
Rob can spiral to worst-case interpretations when contacts go silent (e.g. two unanswered Lumen network pings). Calm, probability-weighted reframing — mundane explanations first, no false comfort — lands well (he acknowledged the pattern).
§
Rob counts carefully; double-check tallies. "Both" = both options, no clarifying. Reports done actions inline mid-message ('sent that over, 8:30') — scan for done-ness before re-instructing. Batch artifacts (tailored flyers/pages): build ONE test pour first, his approval, THEN batch the rest — never the full set blind.
§
Walk-throughs: ONE numbered step at a time, wait for confirmation. Name the EXACT UI object per step; when he reports what he sees, reply with just the values to enter. Mid-crisis, name the window/app to type into. Late-night Denver + destructive ops = fat-finger risk — flag the hour. Park his tangents by name, steer back.
§
(cell preferred; Google Voice OK)
§
('do we just ask the AI'); he'll often let an AI builder finish + save to see the output even when a rebuild is planned — don't push cancel. Verify claims after — GHL's workflow AI overclaims.
§
Claim discipline: every collateral claim gets 'do we really KNOW that?' — unverifiable claims RETIRED not softened ('can't answer phone at bond window'). He field-verifies himself (called 6 bail shops at 5 a.m.). Witnessed evidence > adjectives.
§
Copy rules: no internal SKU names on client assets; name products in buyer vocabulary (Premium Line = their 15% fee); never say anything twice on a page; don't teach buyers their own numbers. Same plain-vocabulary rule applies WITH Rob in sessions — no journalism jargon ("lede" flopped 2026-08-10; say "opening paragraph").