Life OS

Builds the training week and the eating plan together: proposed calendar blocks for /life-planner, every meal priced at low/medium/high with sourced prices, and recipes written two weeks ahead with a consolidated shopping list.

Derives a defended sleep window from the first fixed commitment of each day, proposes it to /life-planner above meals and workouts in the priority ladder, phases any wake-time change at 30 minutes a night, and reviews weekly what the week did to it.

Derives protected alone-time blocks from the gaps that actually exist, proposes them to /life-planner, fills each with three sourced options plus a free zero-travel fallback, and reports honestly when the block keeps getting cut.

Plans a night out that the next day survives: a legal-age check against person.md and the local drinking age, a named ride home from the last venue, and an enforced hard recovery block the following day, with every venue fact fetched and cited.

Turns a good intention into a cadence: an agreed rule with dates, a recurring family-and-relationship block proposed to /life-planner, a specific plan from /date-ideas before each occurrence, a reminder at the stated lead time, and an honest kept-versus-planned record. Never contacts the partner.

Supplies three real, cited options plus a free zero-travel fallback for shared time with a partner or small group, at the chosen budget tier. Owns no calendar block; called inline by /date-night-scheduler for each occurrence and directly by the user.

Learns birthdays, anniversaries and other important dates once (third-party-minimal: name, relationship, date), proposes a short soft yearly reminder to /life-planner at the user's lead time, and supplies real, priced gift/card suggestions on request. Never plans the celebration itself and never contacts the person being celebrated.

Supportive, non-clinical listening for the user's own personal life, using reflective listening, cognitive reframing and grounding. Runs a risk screen before every request; on any signal of imminent risk it stops coaching, delivers sourced crisis resources, and logs the escalation (never the content). Keeps only a minimal theme log — never a transcript, never a diagnosis.

Relationship communication coaching from the user's own account only — reflective listening, I-statements, naming the pattern before the fix. Runs a self-harm screen (hands off to /support-coach) and an abuse/coercive-control screen (hands off to the National Domestic Violence Hotline, stops coaching) before every request. Never contacts the partner; keeps only a minimal theme log.

Recommends real, priced, unread books matched to stated genres, sourced from a publisher or retailer with a fetch date. Keeps a reading list (recommended/reading/finished) so nothing is recommended twice. No paid connector required.

Picks the healthiest realistic order at the chains actually in reach, with calories, protein and price quoted from the chain's own published data with a URL and fetch date, plus the swaps that do the work.

Applied coaching on human and sales psychology (persuasion, negotiation, framing), grounded in named, sourced frameworks (Cialdini, Voss, Kahneman/Tversky) rather than invented advice. Screens every request first for personal distress or relationship-safety signals and hands off to /support-coach or /couples-coach. Never diagnoses or types a real named person.

The single writer to the user's external calendar. Merges every S1 member's schedule/<skill>.md proposal under the fixed priority ladder in docs/interview-framework.md §7, writes through tools/gcal.py with SHAI:<skill> tags, resolves a collision only when the losing block's own file documents the interlock, and lists everything else as a needs-you item rather than guessing.

Runs the user's own smart home through the official APIs their accounts can authorize — reads and commands through their Home Assistant or SmartThings hub, Nest direct once its OAuth path exists, Alexa and Ring as exact manual-fallback checklists. Unlock, open, disarm and camera-setting changes are approval items every time; every camera read is logged; no frame is ever stored; timed requests are proposal blocks /life-planner places.