# Nike Domain - Technical Specifications

> Legacy Planned Physical Wellness and Fitness Instruction Domain (TODO
> Phase 15)

This document records the technical intent for Nike should it ever be extracted
into its own workspace. No `@nike/*` packages are published today; the
corresponding runtime code lives under Lilith and Shakti paths.

## Status

Legacy planned-only domain. No workspace packages exist yet.

## Planned Package Prefix

- Historical/planned: `@nike/*`
- Current implementation references: `libs/lilith/fitness-animation` and
  `apps/lilith/svc-ai/src/*-instruction`

## Core Domain Objects

The types below capture the central entities a Nike implementation would need.
They are design sketches, not yet enforced by a live package.

```typescript
type WorkoutId = string;
type ExerciseId = string;
type FitnessSessionId = string;
type PoseAssessmentId = string;

interface Exercise {
  id: ExerciseId;
  category:
    | 'calisthenics'
    | 'strength'
    | 'cardio'
    | 'mobility'
    | 'flexibility'
    | 'rehab'
    | 'dance'
    | 'sport';
  difficulty: 'beginner' | 'intermediate' | 'advanced' | 'elite';
  requiredEquipment: string[];
  safetyContraindications: string[];
}

interface WorkoutPlan {
  id: WorkoutId;
  goal:
    | 'strength'
    | 'endurance'
    | 'mobility'
    | 'fat_loss'
    | 'rehab'
    | 'sport_performance'
    | 'general';
  exercises: ExerciseId[];
  schedule: string;
  progressionModel: 'linear' | 'undulating' | 'skill_tree' | 'adaptive';
}

interface PoseAssessment {
  id: PoseAssessmentId;
  exerciseId: ExerciseId;
  score: number;
  findings: Array<{
    joint: string;
    issue: string;
    severity: 'low' | 'medium' | 'high';
  }>;
  safetyAction: 'continue' | 'modify' | 'pause' | 'stop';
}
```

## Planned API Surface

- Exercise library and progression APIs.
- Workout plan generation and adaptation APIs.
- Pose and form assessment APIs.
- Biometric and wearable ingestion APIs.
- Instructor avatar and content generation APIs.
- Safety, contraindication, rehabilitation, and modification APIs.

## Requirements and Constraints

These constraints apply to any future implementation and reflect both safety and
privacy obligations:

- Safety checks must run before progression recommendations are issued — a user
  must not receive an advanced progression if an active contraindication
  applies.
- Rehabilitation content must preserve medical disclaimers and referral
  boundaries; Nike does not replace professional medical advice.
- Biometric and video-derived data must follow privacy and consent rules; data
  collected for form analysis may not be repurposed without explicit user
  consent.
- Pose assessment scores must report confidence levels and avoid overclaiming
  precision given the variability of camera angle, lighting, and body
  morphology.