--- name: owner-context-beyond-robco description: "Owner context beyond RobCo, learned 2026-07-21 from a Gemini-memory screenshot the owner shared and asked to be remembered. He builds premium Med-Surg / pharmacology NCLEX (nursing licensing exam) study guides — this is the 'studying' half of his Claude use, and a SEPARATE Claude-heavy workload that shares his usage limit with RobCo. Gemini backs up organizing/QA of those guides when his Claude usage is capped." metadata: node_type: user type: user originSessionId: 1060dea9-0dc3-42b4-958d-2a6f7a6c0c58 modified: 2026-07-21T23:59:24.450Z --- **Saved with the owner's explicit consent** (2026-07-21): he shared a screenshot of his Gemini "RobCo mode" memory and said the info was worth me keeping. ## The genuinely relevant fact for MY role - He builds **premium Med-Surg and pharmacology NCLEX study guides** (NCLEX = the US nursing licensing exam), apparently for/with someone referred to as "Key"/"Kay". This is the **"studying" side** of his stated "Claude for coding + studying" split. - ⇒ **It's a second Claude-heavy workload competing for the SAME usage limit** that RobCo draws on. This is useful background for the usage-exhaustion we hit repeatedly — RobCo is not the only thing spending his cap. When usage runs out, part of what's competing is this NCLEX work. - **CADENCE (owner, 2026-07-21): once a WEEK, ~2 days to complete (a night + a morning), and VERY in-depth.** ⇒ There is a recurring ~2-day window each week where a large, deep chunk of his Claude usage goes to the study guides. During those windows expect RobCo usage to be tight/contended; don't be surprised by mid-work limit hits, and don't queue usage-heavy RobCo work assuming a full cap on those days. - **Gemini is his fallback** for organizing / QA-ing those guides when his Claude usage is capped (per the shared screenshot). ## What I deliberately did NOT put here Personal-life details also visible in the screenshot (e.g. music taste) are NOT saved to this project-orchestration store — that would be the "dump everything everywhere" anti-pattern I advised him against the same day ([[plain-text-invisible-on-mobile]] session context). Those belong in his general Claude/Gemini assistant memory, not here. Right memory, right place. Related: [[primary-users-devices]], [[time-and-work-attribution]] (usage/limits context).