Personal Training OS — Design Elements

UID:

VERSION:

CLASSIFICATION:

PREFIX:

Type	Level	UID	PREFIX	REFS	Title	Statement	Rationale
SECTION	1				Schema design elements
DESIGN	1.1	DES-ARCH		Parents: ARCH-001 Create all databases up front ARCH-003 Create even if used later	DES-ARCH Full architecture created up front	Create all fifteen databases at build time with schema in place, regardless of immediate use. See design-schema section 3.
DESIGN	1.2	DES-VIEWS		Parents: NAV-001 Personal Training OS page NAV-002 Child of Personal Dashboard NAV-003 Link below Inbox NAV-004 Entry points to all databases ARCH-002 Linked references to existing game databases HOK-001 Both teams equal HOK-003 Linked views for both teams	DES-VIEWS Dashboard page and linked views	A Personal Training OS page under Personal Dashboard, linked directly below Inbox, presenting linked views for every database and side-by-side equal linked views of the external Team A and Team B game databases. See design-schema section 18.
DESIGN	1.3	DES-AUTO		Parents: AUTO-001 Build automation fields in now AUTO-002 Standard automation field set AUTO-003 Source vocabulary AUTO-004 Manual default source AUTO-005 Manual override blocks overwrite AUTO-006 Sync populates provenance fields AUTO-007 Failure surfaces in Sync Status	DES-AUTO Standard Automation Block	A shared eight-field automation block (Source, Source ID, External URL, Imported At, Last Synced At, Sync Status, Manual Override, Raw Data/Notes) applied to every integration-fed database, plus the sync contract that a set Manual Override blocks automated overwrite and failures surface in Sync Status. See design-schema section 2.
DESIGN	1.4	DES-PEOPLE		Parents: PEO-001 Create People database PEO-002 People as primary identity model PEO-003 Seed Primary User and Secondary User PEO-004 Optional Notion User and external IDs PEO-005 Secondary User first-class across areas PEO-006 Person relation on attributable databases	DES-PEOPLE People identity hub	People database with Person title, Active, optional Notion User and External IDs, and Role. Seeded with Primary User and Secondary User both as Athlete so Secondary User is selectable everywhere. Every person-attributable database relates to People by relation, not free text. See design-schema section 3.
DESIGN	1.5	DES-TS		Parents: TS-001 Create Training Sessions TS-002 Automation fields on sessions TS-003 Session Type TS-004 Status TS-005 Relates to People TS-006 Distance field TS-007 Run Type field TS-008 Shoe and Route relations REL-001 Session relationships	DES-TS Training Sessions core schema	Central activity log with Person, Session Type, Status, Date, Distance, Run Type, and relations to Training Blocks, Races, Running Shoes, Running Routes, and Exercise Log, carrying the Standard Automation Block. See design-schema section 4.
DESIGN	1.6	DES-HIST		Parents: HIST-001 Seed 5-mile hill repeats HIST-002 Seed 11-mile long run	DES-HIST Historical run seeds	Two completed Training Session seed rows: 5-mile hill repeats and 11-mile long run. See design-schema section 4.
DESIGN	1.7	DES-CAL		Parents: CAL-001 Calendar is source of planned runs CAL-002 Event creates a Training Session CAL-003 Source is Calendar CAL-004 Source ID is event ID CAL-005 External URL from event link CAL-006 Future events are Planned CAL-007 Session Type Run or Race CAL-008 Distance from title when obvious CAL-009 Run Type when explicit CAL-010 No inference when implicit	DES-CAL Calendar import mapping	Calendar run/race events map to Training Sessions with Source Calendar, Source ID as event ID, External URL from event link, Status Planned for future events, Session Type Run or Race, Distance parsed from title when obvious, and Run Type set only when explicit else left unset. See design-schema section 4.1.
DESIGN	1.8	DES-HOCKEY		Parents: HOK-002 Existing game databases are source of truth HOK-004 Count only after Attended HOK-005 Game Training Session fields HOK-006 Default not counted until Attended HOK-007 Attended marks it counting HOK-008 Not attended excluded from load	DES-HOCKEY Hockey game session and counts formula	Hockey Game sessions carry Attendance Status, Team, RPE, Notes, Recovery notes, and relations to the external game databases. A Counts Toward Training? formula returns true only when a hockey game is Attended, so unplayed games never inflate training load. See design-schema section 4.
DESIGN	1.9	DES-RACES		Parents: RACE-001 Create Races database RACE-002 Person and automation fields on races RACE-003 Seed Example Half Marathon RACE-004 Seed Example 5K RACE-005 Runs relate to Race	DES-RACES Races schema and seeds	Races database with Person, Date, Type, Goal, Goal Time, Status, Days Out formula, relations to Training Blocks/Goals/Training Sessions, and the Standard Automation Block. Seeded with Example Half Marathon and Example 5K. See design-schema section 13.
DESIGN	1.10	DES-SHOES		Parents: SHO-001 Create Running Shoes SHO-002 Seed an example running shoe SHO-003 Session to Shoe relation SHO-004 Total mileage rollup SHO-005 Garmin gear can improve mileage REL-003 Rollups for mileage and load	DES-SHOES Running Shoes with mileage rollup	Running Shoes database with Retirement Threshold, a Total Mileage rollup summing related Training Session Distance, and % of Life Used / Status formulas. Seeded with an example running shoe. Garmin gear data can override later. See design-schema section 14.
DESIGN	1.11	DES-ROUTES		Parents: RTE-001 Create Running Routes RTE-002 Seed generic routes RTE-003 Session to Route relation	DES-ROUTES Running Routes	Running Routes database with Type, Distance, Description, and a back-relation to Training Sessions. Seeded with four generic routes. See design-schema section 15.
DESIGN	1.12	DES-BLOCKS		Parents: BLK-001 Create Training Blocks BLK-002 Sessions relate to Block	DES-BLOCKS Training Blocks	Training Blocks database with date range, Focus, Status, relations to Goals/Races, and rollups over related Training Sessions. See design-schema section 5.
DESIGN	1.13	DES-GOALS		Parents: GOL-001 Create Goals GOL-002 Goals relate to People including Secondary User GOL-003 Goal to Race relation	DES-GOALS Goals	Goals database relating to People (including Secondary User) with Type, Target, Target Date, optional Race relation, and Status. See design-schema section 6.
DESIGN	1.14	DES-EXLIB		Parents: LIB-001 Create Exercise Library LIB-002 Record required equipment EQP-001 Templates reflect available equipment only EQP-002 Available equipment set EQP-003 Treadmill constraints EQP-004 Stickhandling ball pending EQP-005 No unavailable equipment assumptions	DES-EXLIB Exercise Library with constrained equipment	Exercise Library with Category, Movement Pattern, and an Equipment Required multi-select whose options are restricted to the available-plus-pending set only, so unavailable gear is not selectable. The treadmill option label carries its no-incline and 8:00/mi limits. See design-schema section 7.
DESIGN	1.15	DES-TEMPLATES		Parents: TMP-001 Create Workout Templates EQP-006 No template requires unavailable equipment	DES-TEMPLATES Workout Templates doable by construction	Workout Templates composed of Exercise Library exercises via an Exercises relation (satisfying TMP-001's "composed of exercises"), plus a Drills relation to Hockey Drills for hockey templates and an Equipment relation; because the equipment set excludes unavailable gear, no template can require it, satisfying the no-unavailable-equipment rule by construction. See design-schema section 8.
DESIGN	1.16	DES-EXLOG		Parents: TMP-002 Create Exercise Log	DES-EXLOG Exercise Log	Exercise Log relating to Training Sessions and Exercise Library, with Person and Date rolled up from the session, plus sets/reps/weight/distance/duration/RPE. See design-schema section 9.
DESIGN	1.17	DES-METRICS		Parents: MET-001 Create Metrics/Check-ins MET-002 Automation fields on metrics MET-003 Metrics sources MET-004 Metrics relate to People	DES-METRICS Metrics / Check-ins (daily wide)	Metrics/Check-ins as daily wide rows per person with weight, resting HR, HRV, sleep, readiness, soreness, mood, steps, VO2max, the Standard Automation Block, and sources Garmin/Apple Health/Apple Watch/Manual. See design-schema section 10.
DESIGN	1.18	DES-NUTRITION		Parents: NUT-001 Create Nutrition Log NUT-002 Automation fields on nutrition NUT-003 Nutrition sources NUT-004 CSV and API import later NUT-005 Nutrition relates to People	DES-NUTRITION Nutrition Log	Nutrition Log per person with Date, Meal, macros, the Standard Automation Block, sources MyFitnessPal/Manual, and support for later CSV/API import. See design-schema section 11.
DESIGN	1.19	DES-WEEKLY		Parents: WKR-001 Create Weekly Reviews WKR-002 Manual at first WKR-003 Automatable later	DES-WEEKLY Weekly Reviews	Weekly Reviews per person, manual numeric fields at first with narrative Wins/Challenges/Focus, automatable later. See design-schema section 12.
DESIGN	1.20	DES-DRILLS		Parents: DRL-001 Create Hockey Drills DRL-002 Drill equipment excludes net	DES-DRILLS Hockey Drills	Hockey Drills with Category and an Equipment Required multi-select limited to stick, shooting pad, cones, balance boards, and pending stickhandling ball, with no net option. See design-schema section 16.
DESIGN	1.21	DES-RESOURCES		Parents: RES-001 Create Resources	DES-RESOURCES Resources	Resources reference database with Type, URL, Topic, and Notes. See design-schema section 16.
DESIGN	1.22	DES-RELATIONS		Parents: REL-002 Metrics and Nutrition relate to People PEO-006 Person relation on attributable databases	DES-RELATIONS Relationship map and rollups	Ownership and cardinality of all relations, ensuring Metrics and Nutrition relate to People and that shoe mileage and hockey load are derivable via rollups rather than manual tally. See design-schema section 17.
SECTION	2				Design decisions (candidate change requests)
DESIGN	2.1	DES-D1		Parents: EQP-005 No unavailable equipment assumptions	DES-D1 Equipment as constrained multi-select, not a database	Availability is enforced by restricting Exercise Library / Hockey Drills equipment option lists rather than modeling an Equipment database, since the requirements mandate exactly fifteen databases and Equipment is not one.	Keeps to the baselined database list; unavailable gear is unselectable. Alternative (Equipment as a 16th database with an Availability status) is a candidate change request if inventory tracking is later wanted.
DESIGN	2.2	DES-D2		Parents: RACE-003 Seed Example Half Marathon	DES-D2 Times stored as text with optional numeric seconds	Notion has no duration type, so Goal Time / Result Time are text H:MM:SS with an optional numeric seconds field where math is needed.
DESIGN	2.3	DES-D3		Parents: HOK-002 Existing game databases are source of truth	DES-D3 Two hockey-game relations (Team A, Team B)	Notion relations are single-target and the two game databases are separate sources of truth, so Training Sessions carry two relation properties disambiguated by Team.
DESIGN	2.4	DES-D4		Parents: MET-001 Create Metrics/Check-ins	DES-D4 Metrics as daily-wide rows	Metrics/Check-ins are one wide row per person per day, optimized for manual entry; high-frequency wearable streams would use a long-format companion added when an integration lands.
DESIGN	2.5	DES-D5		Parents: RACE-003 Seed Example Half Marathon RACE-004 Seed Example 5K	DES-D5 Compound seed statuses kept literal	The compound seed statuses Training/Registered and Registered/Planned are preserved as literal select options alongside atomic options so the seeds match the requirements exactly.
SECTION	3				Non-functional design
DESIGN	3.1	DES-NFR-PRIV		Parents: NFR-PRIV-001 Health data kept private NFR-PRIV-002 Least-scope integrations	DES-NFR-PRIV Privacy - private workspace and least scope	Data lives in the private Notion workspace (not public); integrations request only the minimum scopes. See design-schema automation contract.
DESIGN	3.2	DES-NFR-DATA		Parents: NFR-BKP-001 Backup and recovery NFR-PORT-001 Data portability NFR-RET-001 Indefinite history retention	DES-NFR-DATA Backup, portability, retention	Periodic Notion export provides backup and recovery; data stays API-accessible and exportable for portability; no automatic deletion so history is retained indefinitely.
DESIGN	3.3	DES-NFR-UX		Parents: NFR-PERF-001 Responsive rollups at expected volume NFR-USE-001 Mobile low-effort capture	DES-NFR-UX Performance and mobile usability	Single-user, low-hundreds data volume keeps rollups responsive; the Notion mobile apps provide low-effort cross-device capture.