Coaching & planning · Coaching
How Brick coaches
Deterministic plans, AI that explains, and consent-gated adaptations — the coaching philosophy.
Brick separates structure from story. The planning engine decides what lands on your calendar. AI explains why, narrates briefs and debriefs, and chats with you — it does not invent the next workout.
Deterministic first
Season shape, weekly volume, sport split, session placement, and workout prescriptions come from a rule-based engine. Given the same history, prefs, and races, the plan is reproducible and auditable. That is what makes Brick feel like a coach with a method — not a chatbot with a calendar UI.
AI is budget-capped and evidence-driven. It grounds claims in your data and never silently rewrites structure.
The closed loop
- 1
History, prefs, races, and limiters
- 2
Macrocycle — base → build → peak → taper
- 3
Weekly skeleton — longs, quality, fillers, strength
- 4
Session prescriptions — purpose, intensity, guidance
- 5
You train and sync activities
- 6
Readiness, limiters, and load update
- 7
Proposals you accept or dismiss
How the plan is built
Volume, session duration, and intensity come from different parts of your dossier. Training history sets safe weekly hours and how long a session can be; workout type and phase set intensity as a fraction of threshold; thresholds turn those fractions into watts, pace, or heart rate on the device. Full walkthrough: How training plans are built.
You stay in control
When readiness, missed key sessions, or load suggest a change, Brick opens a proposal — step up, step down, ease the week, reprioritize, rebalance, return to training, or recalibrate. Nothing structural changes until you approve. Details: Readiness, check-ins, and proposals.
Coach voice
- Experienced, direct, warm, and evidence-driven
- No invented numbers — claims tie back to your data
- Detail level scales with your coaching preference (educational → data-dense)
- Training guidance only — not medical diagnosis
What makes Brick different
- Tri-native bricks — long ride + brick run as an atomic pair in build/peak, not two unrelated sessions.
- Capacity from history — volume anchors to what you have actually done, with sensible comeback logic after layoffs.
- Limiter-aware work — detected weaknesses influence which sessions get priority. See Limiters and blind spots.
- Metric-aware prescriptions — Z2 and recovery are paced by heart rate; intervals and threshold work use power (bike) or pace (run/swim), with an HR ceiling on sustained quality when it matters.
- Life targets periodized to training— sleep, fuel, and hydration follow the day's load. Fuel, sleep, and recovery.
