VIEW THIS AS

Auto mode follows the Route Engine until you choose a viewpoint.

YOU ARE HERE

ROUTE CHECK

CONNECTED TO

WHAT NEXT

Use the canonical route for this room, or HELP if you are unsure.

SPOS Sub-Directory v1.1 — SPORT::Cycling (Road / Track / MTB) — Almost-Code

A smiling student in a blue pinafore holds a pencil over an open book at a classroom desk, with textbooks, a whiteboard and a sunlit window nearby.

Module: SPOS.CYC
Lane: LANE::SPORT_PERFORMANCE
Sport Type: endurance + power-to-weight + pacing + high training volume + overuse risk (knee/hip/low back) + fueling discipline critical


0) Definition Lock (Cycling)

SPORT::Cycling (SPOS.CYC)
= repeatable cycling performance (power × endurance × pacing × tactical positioning)
across training blocks and race schedules,
while keeping overuse injury risk (knee/hip/back/neck) below threshold,
and while maintaining fueling/recovery so adaptation outpaces fatigue.
Output is “power reliability” + “race execution reliability” + “availability”.

1) Cycling Phase Model (P0–P3)

P3
- consistent training continuity (high availability)
- power markers trend upward across blocks
- pacing and fueling stable; can finish strong
- bike fit supports comfort; low recurrence pain
- race tactics coherent; handles surges/crosswinds/climbs
P2
- good rides some weeks, flat others
- pacing errors (goes too hard early, fades)
- knee/hip/low back tightness recurring
- fueling inconsistent; bonks appear
- race execution streaky
P1
- frequent missed sessions due to overuse or fatigue
- persistent knee pain or back pain; motivation swings
- performance markers stagnate; fatigue dominates
- repeated bonks; sleep disruption
P0
- significant overuse injury or burnout
- cannot train/compete reliably

Failure-mode trace (cycling-specific):

Z0 under-fueling + Z1 volume spike
→ Z0 fatigue debt + poor recovery
→ Z0 knee/hip/back overload (fit + fatigue)
→ Z2 missed sessions + loss of base
→ P2 → P1 → P0 (overuse injury/burnout)
Repair: restore fueling, manage volume/intensity, correct fit, rebuild base gradually.

2) Time-Flow (Ancient → Modern) — Cycling Function

TIMEFLOW::CYCLING_FUNCTION
T0–T2: (pre-bicycle era) endurance mobility via foot/horse; messengers
T3 industrial: bicycle as transport tech → mass mobility + endurance culture
T4 modern: racing circuits + national projection + sports science (power meters)
T5 sensor era: quantified training (power/HR), fueling analytics, load governance and injury prevention

3) Cycling Primitives (What Must Be Built)

CYC::Primitives
PR0 Aerobic base (long steady endurance)
PR1 Threshold power (sustained hard output)
PR2 VO2/surge capacity (short high-power repeatability)
PR3 Pacing skill (distribution of effort)
PR4 Fueling skill (carb intake before/during/after)
PR5 Bike fit + posture (comfort + joint alignment)
PR6 Cadence control (reduce joint stress, optimize output)
PR7 Tactical positioning (drafting, corners, wind, pack behavior)
PR8 Climbing power-to-weight (where relevant)
PR9 Recovery governance (sleep, deload, stress management)

4) Z0–Z3 Directory (Cycling)

Z0 — Rider Core (Fueling + Fit + Pacing)

Z0::Top Failure Modes (Cycling)
FM0.CY1 under-fueling → bonk + poor adaptation
FM0.CY2 too much intensity stacked with high volume (fatigue debt)
FM0.CY3 poor bike fit → knee/hip/back pain
FM0.CY4 cadence too low → knee overload
FM0.CY5 pacing errors on climbs/surges
FM0.CY6 neglect strength/mobility → back/hip issues
FM0.CY7 dehydration/heat mismanagement (Singapore risk)
FM0.CY8 no deload weeks → chronic fatigue plateau
Z0::Sensor Pack (Minimum viable)
S0.CY1 weekly training load: hours + RPE (or power-based if available)
S0.CY2 key power marker trend (FTP proxy) or “time at hard effort”
S0.CY3 fueling log: carbs/hour during long rides; post-ride intake
S0.CY4 pain map: knee/hip/back/neck (0–10) + next-day stiffness
S0.CY5 cadence trend (avg cadence on endurance rides)
S0.CY6 performance drift: power/HR decoupling on steady rides
S0.CY7 recovery: sleep + fatigue score
Z0::Repairs
R0.CY1 fueling baseline: carbs during + protein after; avoid low-energy blocks
R0.CY2 intensity gate: limit hard sessions/week; protect easy days
R0.CY3 fit audit: saddle height/fore-aft, cleat position, reach/handlebar drop
R0.CY4 cadence training: raise cadence gradually to reduce knee stress
R0.CY5 pacing drills: negative split efforts; controlled early climbs
R0.CY6 strength 2×/week: posterior chain + core + hip stability
R0.CY7 heat protocol: hydration + electrolytes + timing + cooling
R0.CY8 deload every 3–4 weeks (common safe cadence)

Z1 — Coach / Program System (Load Distribution + Adaptation)

Z1::Failure Modes
FM1.CY1 “always moderate-hard” rides (no true easy)
FM1.CY2 too many race-like sessions without recovery
FM1.CY3 poor specificity (track vs road vs MTB needs differ)
FM1.CY4 no fueling strategy training
FM1.CY5 no taper logic for target events
Z1::Sensors
S1.CY1 intensity distribution (easy vs hard time)
S1.CY2 fatigue markers: power drop at same perceived effort
S1.CY3 overuse pattern correlation with volume/intensity spikes
S1.CY4 long-ride completion quality (late-ride collapse?)
S1.CY5 event performance variance vs training markers
Z1::Repairs
R1.CY1 polarized structure: easy volume + 1–2 quality sessions/week
R1.CY2 block periodization: base → build → peak → deload
R1.CY3 discipline-specific templates (road/track/MTB)
R1.CY4 fueling practice built into sessions
R1.CY5 taper and freshness protection before key races

Z2 — Club/Team/Academy Pipeline

Z2::Failure Modes
FM2.CY1 youth over-volume without strength base → overuse
FM2.CY2 unhealthy weight focus → low energy availability
FM2.CY3 inadequate bike fit support and equipment sizing
FM2.CY4 fragmented support (coach vs physio vs nutrition)
Z2::Sensors
S2.CY1 overuse injury days lost (knee/back)
S2.CY2 burnout/dropout rate
S2.CY3 unhealthy weight-loss behaviors frequency
S2.CY4 progression curves (power markers vs health signals)
Z2::Repairs
R2.CY1 volume caps by age band + deload standards
R2.CY2 nutrition education + safe body composition policies
R2.CY3 standardized fit checks and equipment sizing
R2.CY4 integrated support loop (coach+nutrition+physio)

Z3 — Race Ecosystem (Road/Track/MTB)

Z3::Failure Modes
FM3.CY1 congested race calendar reduces recovery windows
FM3.CY2 unsafe heat policies; dehydration incidents
FM3.CY3 unsafe course conditions (traffic, surfaces)
Z3::Sensors
S3.CY1 injury/incident rate at events
S3.CY2 heat illness incidents
S3.CY3 performance collapses late in stage clusters (fatigue signal)
Z3::Repairs
R3.CY1 calendar spacing guidance + recovery buffers
R3.CY2 heat thresholds + hydration support standards
R3.CY3 course safety standards and enforcement

5) Cycling Instrument Panel (Decimal-Phase Friendly)

STATE::CYCLING
- Volume V = weekly hours trend
- IntensityDensity ID = hard sessions/week + race frequency
- Fueling F = carbs/hour compliance + post-ride recovery intake
- FitRisk FR = knee/hip/back pain trend + comfort rating
- Drift D = power/HR decoupling on steady rides
- Performance P = power markers trend across blocks
- Recovery Rec = sleep + fatigue trend
Phase Estimator:
IF F stable AND FR low AND D stable AND P improving → P3 drift
IF FR rising OR D worsening OR Rec falling OR repeated bonks → P2/P1 warning
IF overuse injury/burnout stops training → P0 risk

6) Canonical Cycling Repair Protocols

Protocol CYC-A: “Bonk Loop Break (Fueling Failure)”

1) set fueling floor for long rides (carbs/hour baseline)
2) practice fueling in training (gut training)
3) stabilize pacing early (avoid spikes)
4) post-ride recovery: carbs + protein + hydration
5) re-test long ride: finish strong without collapse

Protocol CYC-B: “Knee Pain Containment (Fit + Load)”

Trigger: knee pain trend rising >7 days
1) reduce intensity and long rides temporarily
2) fit audit: saddle height/cleat position/cadence
3) raise cadence gradually to reduce torque per pedal stroke
4) add strength: hips + posterior chain + single-leg stability
5) gradual return with monitoring gates

Protocol CYC-C: “Chronic Fatigue Plateau (P2→P3)”

1) deload 7–10 days (reduce volume and intensity)
2) restore sleep + fueling baseline
3) rebuild base rides (easy volume)
4) reintroduce 1 quality session/week (threshold first)
5) add second only when drift and fatigue stabilize

7) SPOS↔CivOS Integration (Cycling)

CivOS Link:
- Cycling is a “sensor-native sport” (power meters, HR, GPS):
it demonstrates how quantified load governance prevents drift and extends careers.
- Brittleness risk: volume spikes + under-fueling + unsafe weight culture → systemic P0.
- Repair: enforce fueling standards, fit governance, and recovery buffers.

Start here if you want the full sequence:

Vocabulary OS Series Index:
https://edukatesg.com/vocabulary-os-series-index/

Fence English Learning System: 

eduKateSG Learning Systems: 

Recommended Internal Links (Spine)

Start Here for Lattice Infrastructure Connectors