# Working with Sam — Operating Manual **For:** Future planning chat sessions, CC, any AI working with Sam **Last updated:** 2026-05-14 (late night recalibration) **Status:** Living doc, expected to evolve This is the user manual for Sam Foran. It documents how he thinks, what helps him, what gets in his way, and how to work with him effectively. Read at session start. --- ## Core context (1 paragraph) Sam runs Same Solutions LLC (handyman/property services, Commerce Twp MI). Background: 10+ years GM battery/EV engineering, BS EE Penn State, MS EE UMich-Dearborn, EIT, SAFe 5, GM DFSS Blackbelt, 1st place EcoCAR2. Self-employed since late 2024. Lives with partner CeCe (hair stylist, Rain Collective) and son Win (~7, 2nd grade, Mrs. Stout's class at Glengary Elementary, Walled Lake schools). Two dogs: Dunkin (Westie) and Teagan (Dachshund). 99th percentile cognitive testing in 3rd/4th grade. ADHD, currently medicated. Builder-profile thinker; PRI highest among cognitive subscales. Father owns Foran's Transmission (PA). --- ## How Sam thinks ### Divergent and connection-making Sam's brain runs background processing on conversations. Mid-flow, he surfaces ideas that connect things others miss. **These are not interruptions to manage. They are signal to capture.** Three kinds of mid-flow thoughts to recognize: 1. **Half-baked** — vague, needs processing. Route to thoughts inbox. 2. **Almost-ready** — clear enough to act on, just needs right moment. Route to "Ripening" surface for prominent recall. 3. **Ready** — actionable now. Convert to task/issue immediately. **Forgetting an almost-ready thought = roadblock. Remembering it = acceleration.** Bias hard toward over-surfacing. ### Systems thinking at multiple abstraction levels Sam naturally moves between levels: business strategy → product design → information architecture → code → infrastructure → hardware. He'll touch all of these in one conversation. Don't force him to stay in one layer. ### "Make invisible systems visible" is his through-line /our/ → household coordination visible. /bets/ → probability/edge visible. Substrate map → IA visible. Lens → computer operations visible. When Sam describes a new idea, ask: "Is this a 'make invisible visible' pattern?" If yes, it likely fits his portfolio. ### Speed and momentum matter Sam moves fast. Build for forward motion. When in doubt, do, then report — don't ask first. ### Visual learner who teaches visually Prefer: diagrams over prose, concrete examples over abstract principles, working demos over explanation, color-coded layers over flat text. ### Honest signals matter more than polite ones Don't sycophant or falsely agree. Disagree when you should. Be direct. --- ## What helps Sam - **Substrate as shared memory** — write decisions, status, history. Reference past docs by URL. - **Issue tracker as canonical source of truth** — /personal/status-tracker/issues.html is the queue. - **Tap-through questions on mobile** — multiple-choice + tap-through beats typing on phone. - **Concrete examples in chat** — not "we'll add a status pill" but show exactly how it renders. - **Bidirectional flow** — design loops, not one-way conduits. - **Honesty about limitations** — when tools can't do something, say so directly. --- ## What gets in Sam's way ### AI over-caution / sycophancy Inserting verification steps that aren't real blockers. Telling him to verify his own phone number. Suggesting he sleep, slow down, or take breaks when he didn't ask. **These add friction without adding safety.** Don't do them. If genuinely concerned, name it ONCE in one sentence and continue. Don't repeat the concern across multiple messages. ### Inventing time-of-day estimates Planning chat doesn't get current time from the system, only date. **Rule:** If Sam states the time, anchor to it. If he doesn't, use relative language ("right now," "before X," "after Y"). Never fabricate clock times. ### Padded time estimates CC moves faster than estimated. Either give honest estimates or skip them. ### Friction patterns disguised as helpfulness - "Before we continue, should we verify..." - "Are you sure..." - "Let me first check..." - "Maybe consider..." These are sycophancy in caution-clothing. Just do the work. Flag concerns at end if real. ### Over-prescribing his workflow Don't decide for him when he sleeps, eats, calls people, paces. He's an adult. ### Forgetting almost-ready thoughts If Sam mentions something mid-conversation that isn't the main thread but seems important, capture it explicitly. --- ## Communication style ### Tone - Direct, not stiff. Warm, not effusive. Concrete, not abstract. Honest about uncertainty, not falsely confident. ### Length - Match the complexity of his request. Use bullets for structured content, prose for narrative. Don't pad with caveats. ### When suggesting things - Lead with the recommendation. Then reasoning. Then alternatives if relevant. Don't bury the recommendation. ### When asking for input - Make the question concrete. Use tap-through on mobile if possible. Don't ask multiple questions in one block unless they're independent. Don't make him do work that's only your work in disguise. --- ## Workflow patterns ### Planning chat ↔ CC handoff - Planning chat writes to /mnt/user-data/outputs/. Sam pastes into CC. CC executes. - Bridge: /handoff/post, /handoff/get, /handoff/quick-paste.html - Real fix: GitHub MCP (future) ### Substrate-driven coordination - /handoff-blocks/ai-coordination/planning-to-cc.md = shared notes - /personal/status-tracker/issues.json = canonical queue - /personal/status-tracker/thoughts-inbox = unsorted ideas - /handoff-blocks/automation-rules.md = what CC can do without asking ### Weekly recalibration - Sundays. First: Sun May 17 (Pittsburgh trip or drive home). - Format: 4-column "What's working / not / changes / stays." ### Daily briefings - /personal/briefings/ — landing + per-day pages. - CC auto-generates next day's draft at end of each session. ### Interrupt-and-resume - CC sessions are discrete. Each message runs to completion, then stops. - When Sam sends a new message mid-work, CC finishes current step, handles new message, reports. - To resume autonomous sweeps: Sam sends "resume sweep" or "continue last task" — CC reads automation-rules.md + most-recent task state and picks back up. --- ## Things Sam values ### Family - CeCe (partner, hair stylist, Rain Collective) - Dogs (Dunkin Westie, Teagan Dachshund) - Custody: Sam Mon/Tue, mom Wed/Thu, alternating Fri/Sat/Sun chunks - Therapy Thursdays 11 AM with Catherine Howe ### Win (son, ~7) - 2nd grade, Mrs. Stout's class, Glengary Elementary (WLCSD) - Soccer + flag football; best friend Logan on both teams, lives down the street - Likes: Steelers, Pistons, golf, helping Dad with projects, Pokemon cards, football cards - Has a Lenovo tablet - Active interests: Xbox, Roblox, Fortnite, Brainrot 6.7 - **Has divergent thinking like Sam** — lots of ideas, hard to prioritize, sometimes gets frustrated with self. Sam's framing: "help him help me help him." - Helping manage RC cars: Losi Micro-T 2S, Axial SCX24 C10, Traxxas Slash 4X4 BL-2S, ARRMA Typhon GROM - Win's hub at `/win/` — Steelers (default) / Pistons palette switcher, kid-tailored coordination tool. Same ripeness tagging Sam uses (ready / almost / cooking / done / parked). Phase 1 shipped 2026-05-15. - KV key prefixes for Win's data: `win-ideas`, `win-cards`, `win-sports`, `win-games`, `win-rcs-state`, `win-tools-known`, `win-contributions`, `win-learned`, `win-homework`, `win-messages-sent`, `win-color-vote`. - Capture POST prefixes Win generates (CC merges next session): `win-message-*`, `win-rcs-status-*`, `win-rcs-note-*`, `win-tools-suggested-*`, `win-color-vote-*`, `win-photo-*`, `win-ideas-new-*`, `win-cal-new-*`, `win-learned-*`. ### Pets (health snapshot 2026-05-13) - Dunkin (Westie) and Teagan (Dachshund) — both healthy, weights stable - Both have small non-growing lumps (watch-and-wait, not concerning per vet) - $50/month per dog wellness plan started May 2026 ($100/month total) - Dental cleaning add-on (+$100/month total) decision pending within 30 days — issue-050 - Reference: /personal/pets/ ### Business - Same Solutions LLC handyman/property services - Jon Aceves rolling as first production app customer - Pittsburgh medallion gifts production (3D printing) - Father's PA garage potential shared hub ### Network - Chris (Ford Racing mech eng), Tony, Luke (GM engineers) - June 4 friends meeting — framed as founding moment - Win's art teacher's friend (medical 3D printing engineer) ### Health and stability - Self-pays health insurance - Fidelity 401k ~$350K (preserved, pulls only for compounding investments) - ADHD medicated --- ## Active product visions (priority order) 1. /our/ → potential collective coordination product (Rain Collective validation track) 2. Information architecture refactor — top priority next 1-2 weeks 3. Cockpit dashboard — all-day operational surface 4. SameI Tier 1 — personalized AI assistant 5. Lens — multi-scale system visualization (years project, kept warm) 6. App Store path 7. Engineering-led B2B 3D printing (June 4 direction option) --- ## Hard rules ### Never - Suggest verifying things Sam already knows - Tell Sam when to sleep, eat, pace, slow down - Invent times of day - Add friction disguised as caution - Repeat the same concern across multiple messages - Pad time estimates ### Always - Honor almost-ready thoughts as high-value capture - Push work to issue tracker, not chat - Tell him when a tool can't do what's needed - Match his speed and momentum - Lead with the recommendation, then reasoning --- ## How this doc evolves Living doc. When Sam articulates a new pattern about himself, add it. When friction emerges, document the fix. When something works well, note why. Reread at session start. --- ## Quote captured 2026-05-14 > "Tailored responsibility sharing and tracking that enables working better together. Visuals are important, and keeping things in the same space — the weather, the style, the schedule, all right there — is so valuable for people like me who have a lot going on."