System Overview
Hardware, software, and biometrics work together in structured, standardized sessions. This page shows the blueprint: what physically and digitally exists in a session, and how the major system layers interact.
The system stack
System Overview
Hardware, software, and biometrics work together in structured, standardized sessions. This page shows the blueprint: what physically and digitally exists in a session, and how the major system layers interact.
The system stack
The system stack
Each layer has a distinct role. Together they deliver structured stimulus, measure response, and support progression over time. Details live on subpages; here is the high-level view.
What physically creates the stimulus.
Sessions are structured and repeatable — not manually improvised.
Sessions are measured, not guessed.
Sessions compound and improve over time.
The system stack
Each layer has a distinct role. Together they deliver structured stimulus, measure response, and support progression over time. Details live on subpages; here is the high-level view.
What physically creates the stimulus.
Sessions are structured and repeatable — not manually improvised.
Sessions are measured, not guessed.
Sessions compound and improve over time.
Integration
The flow is: stimulus → monitoring → data capture → adjustment. Here’s what that means inside a real session — not as a textbook diagram, but as operational logic.
From stack to reality
The four layers aren’t abstract — they map to a real, repeatable session structure. Here’s the bridge between the architecture and what happens in practice.
A session is built from multiple discrete blocks. Each block has a defined role in the exposure sequence — hypoxic or hyperoxic — so the stimulus is structured, not continuous or random.
Oxygen levels shift between blocks according to the protocol. Alternation is deliberate: it creates the intermittent stress and recovery pattern that drives adaptation.
Block length and transition timing are specified, not improvised. That’s what makes sessions repeatable and comparable across time.
Throughout the session, SpO₂ and heart rate are captured and aligned to the block structure. You see response in context — not just a single number at the end.
Architecture, not marketing
Open stimulus model versus structured conditioning model. The difference isn’t marketing — it’s how the system is built. Segmentation and logging matter because they’re what make progression measurable and repeatable instead of guesswork.
Exposure is delivered; response is not structurally captured or used to refine the next session.
Stimulus is segmented, response is logged per phase, and future sessions are informed by prior data.
Why this contrast matters: Without segmentation, you can’t attribute response to a specific part of the session. Without logging, you can’t track whether tolerance is improving. Without structured progression, you’re either repeating the same stimulus indefinitely or changing it by guess. The architecture of this system is built so that each session informs the next — that’s the structural difference.
Same architecture, every platform
The four-layer architecture exists across all platforms. Whether boxed, performance, or custom install, the system stack remains the same — only how it’s deployed changes.