split assistant
A bounded assistant for beginner weekly split planning. Ben gathers only decision-critical context, drafts an unsaved seven-day split preview, and keeps revision chat separate from saving.
Purpose
Ben exists to reduce the blank-page problem in split planning. The assistant is not a coach, diagnostic tool, or medical system. It helps a beginner turn a few constraints into a weekly structure that can be previewed, revised, and then saved only when the user explicitly accepts it.
That boundary is intentional. The product already owns persistence, day ordering, rest-day handling, and workout logger preload. Ben's role is to supply a reasonable draft for those existing systems instead of bypassing them.
Inputs Ben tries to learn
The chat prompt asks for only the information that changes the split: schedule availability, rough days per week, experience level, equipment, session length, goals, focus areas, and exercises or conditions to avoid. When information is missing, Ben should ask one concise follow-up rather than sending a long intake form.
Determines which weekdays become training days and where rest days should sit.
Keeps exercise choices aligned with a full gym, home gym, machines, dumbbells, cables, or bodyweight-only setup.
Shapes the split type and exercise emphasis without prescribing weights, guaranteed outcomes, or advanced programming.
Draft contract
A generated draft must be a seven-day split. Weekday values are normalized to Monday through Sunday, rest days contain no exercises, and training days generally contain three to six exercises with two to four sets per exercise.
The parser still treats model output as untrusted. It fills missing weekdays with rest days, clamps extreme set counts, accepts simple generated labels such as Day 1, and rejects duplicate weekdays. The draft remains unsaved until the user creates it through the normal split API.
Revision loop
When a preview exists, the current unsaved draft is sent back to Ben as context. That lets the user ask for targeted changes such as shorter sessions, more upper body work, or home-gym substitutions without re-explaining the entire split.
The UI makes revision mode explicit with an Ask for changes action and a composer state that says the next message is changing the preview. Revised drafts replace the unsaved preview; they do not mutate saved split data.
Safety boundaries
Ben avoids medical advice, injury rehab plans, diagnoses, and promises about outcomes. If the user mentions pain, injury, illness, pregnancy, or a medical condition, Ben should recommend checking with a qualified clinician and keep the generated structure conservative.
The assistant also avoids weight prescriptions. Logit's workout journal can record and compare loads, but split generation stays at the structure level: weekdays, workout types, exercises, and target set counts.