# Hermes Physique Check-in — Planning Draft

- intent: clear
- review_required: false
- status: awaiting-approval
- topology:
  - Dedicated Hermes profile and gateway: create an independent `physique-coach` agent with its own bot identity, service process, gateway state, credentials, SOUL, skills, memory, sessions, cron jobs, and data directory.
  - Structured check-in storage: persist a dedicated append-only physique check-in dataset, separate from daily workout plans and the default Hermes state.
  - Coaching context: make the latest check-in and rolling weekly aggregates available to the profile without treating old Markdown as live state.
  - Safety and data integrity: preserve missing/estimated values, provenance, and correction history.
- discovered_evidence:
  - The default Hermes gateway is running; no named profiles are currently active.
  - Hermes officially supports one independent gateway process per profile, each with separate bot token, state, config, SOUL, skills, memory, sessions, and cron jobs.
  - The existing default-profile workout bot is a separate custom Discord process and must remain untouched.
  - The supplied coaching records define the morning fields and weekly review loop.
- recommended_defaults:
  - Use a fresh `physique-coach` Hermes profile and dedicated Discord bot token; do not clone the default profile's memory, SOUL, or cron jobs.
  - Use a dedicated Discord channel for the coach, with the profile gateway installed as its own systemd user service.
  - Deliver the check-in at 08:11 KST by default, using the profile's own cron schedule.
  - Store an immutable daily check-in record plus a separately derived current-state/weekly-summary view.
  - Keep workout scheduling as an optional follow-up after the check-in, not a competing morning message.
- pending_action: write `.omo/plans/hermes-physique-checkin.md` after user approval; do not implement yet.