Before You Begin
This document assumes you have already read the safety documentation and understand that Velo-X is not a medical device. If you haven't, stop here and read When to Stop first.
The first thirty nights are not about results. They are about building a signal relationship between the device and your specific REM profile. Everyone's baseline is different. The device adapts to yours.
Resist the temptation to increase sensitivity settings during the first two weeks. The algorithm needs a clean dataset before it can optimize. Interference from aggressive settings will corrupt the baseline.
- Charged device (full charge, 3–4 hours from empty)
- Velo-X app installed and paired via BLE
- A consistent sleep window — same ±30 minutes each night
- A sleep journal, physical or digital (not the app)
- No alcohol for 48 hours before the calibration night
- No new sleep supplements during the first two weeks
Most users do not experience a lucid dream during the first thirty nights. This is not a failure. The protocol is calibration, not performance.
Calibration Night (Night 0)
Night 0 is a passive data collection session. The device will monitor but will not emit any light signal. This gives the algorithm your unperturbed REM signature.
Open the app. Confirm firmware is v3.2 or later. Run the strap-fit diagnostic. EOG impedance should read below 5 kΩ on both sensors. If either reads above 8 kΩ, reposition the strap and retest.
Power on the device with a single press. The haptic pulse (0.2 G, 80 ms) confirms standby mode. Do not interact with the device again. Sleep in your normal position.
Open the app within 15 minutes of waking. The calibration summary shows estimated REM onset time, cycle count, and signal quality score. A score above 72 is sufficient to proceed to Night 1. Below 60: repeat Night 0.
Week One — Nights 1–7
The device begins emitting light cues starting Night 1. Default settings: intensity 0.08 cd/m², 2 pulses, 600 ms interval. Do not change these.
You will probably not perceive the cues consciously. You may notice nothing at all for the entire first week. This is normal and expected.
- Reality checks: 10 per day minimum, each with genuine doubt — not mechanical
- Sleep journal: write immediately on waking, note quality of transitions and unusual clarity
- Cue review in app: cross-reference device logs with journal each morning
- No daytime naps during Week One
| Outcome | Meaning | Action |
|---|---|---|
| No adjustment needed | Signal quality consistent | Proceed to Week Two |
| Increase sensitivity +1 | Cues absorbed without response | Accept if no sleep debt |
| Extend baseline | Insufficient signal quality | Repeat calibration night |
Week Two — Nights 8–14
By Night 8, the device has enough data to begin adaptive scheduling. Cues will no longer be emitted at fixed intervals — the algorithm targets the optimal window within your REM cycle.
Some users report the first anomalies during Week Two: a dream element that feels slightly wrong, a moment of heightened awareness before sleep onset, or the briefest sense that something outside the dream was trying to communicate. These are integration attempts — not lucid events.
- Continue reality checks, increase to 15 per day if Week One felt passive
- Begin prospective memory training: identify one dream element to look for each night
- Log cue-response pairs in the app, mark any dreams where something felt unstable
- Maintain sleep window — variance above 45 minutes degrades adaptive scheduling
Some users notice lighter sleep or more frequent waking during Week Two. This typically resolves by Night 11–12. If it persists beyond Night 14, lower intensity by one step. Do not discontinue abruptly — taper over 3 nights.
Week Three — Nights 15–21
Week Three is typically when the first confirmed lucid event occurs, if it occurs during the first month. The device's model is now mature enough to place cues within the narrowest optimal window.
It may also be when nothing notable happens. Both outcomes contain information. The absence of a lucid event does not indicate failure — it indicates that your recognition threshold has not been crossed yet.
| Option | Notes | Frequency |
|---|---|---|
| WBTB supplement | 5–6h after sleep onset, 20–30min awake then return | Max 2x/week |
| Daytime naps | 20 min, before 15:00 only | Permitted |
| Pulse count increase | 2→3, only if app recommends and no fragmentation | Conditional |
Week Four — Nights 22–30
By Night 22, the device's model is stable. Week Four is the first period in which the adaptive algorithm operates without major recalibration.
Your job is to stay consistent. After Night 30, the app generates a full protocol summary: REM onset average, cue success rate, and recommended configuration for continued use. Save this report.
- Continue with current settings if results are satisfactory
- Increase to advanced protocol (see Signal Parameters & Tuning, v3.2)
- Reduce cue frequency to maintenance mode (2–3 nights per week)
- Full pause for 7–14 days if glossy fatigue has appeared
Signal Interpretation
The cue is two red pulses at 625 nm, below conscious perception threshold. Your dreaming brain will not perceive it as light. It will perceive it as an anomaly in the dream narrative — and attempt to resolve it.
| Pattern | Description | Frequency |
|---|---|---|
| Direct integration | Appears as a red light, warning indicator, or flash within the dream | Common |
| Narrative redirection | Dream scene shifts abruptly — logged as 'scene cut' | Common |
| Emotional response | Wave of unease or urgency without obvious source | Moderate |
| Failed integration | Nothing. Signal processed and discarded. | Most common |
| Recognition crack | Moment of doubt: 'this is strange.' Target state. | Rare |
When It Doesn't Work
If thirty nights have passed without any notable event, the protocol has not failed. Some users require a longer baseline. Some require a different configuration. Some require a complete pause.
| Cause | Description | Fix |
|---|---|---|
| Inconsistent sleep window | Variance >45 min degrades the algorithm | Tighten window |
| Alcohol or sedatives | Suppresses REM by 20–40% | Eliminate or reduce |
| Sleep debt | Recovery sleep crowds out REM | Address debt first |
| Over-anticipation | Monitoring for the cue interferes with it | 5-night pause |
| Strap fit degradation | EOG signal quality drops over time | Run fit diagnostic |
Appendix: Default Calibration Table
Factory defaults and recommended ranges for first-month use. Do not adjust beyond these ranges without reading Signal Parameters & Tuning.
| Parameter | Default | Range | Unit |
|---|---|---|---|
| LED intensity | 0.08 | 0.02 – 0.8 | cd/m² |
| Pulse count | 2 | 1 – 6 | pulses |
| Pulse interval | 600 | 300 – 1200 | ms |
| REM detection threshold | 28 | 12 – 40 | µV |
| EOG impedance limit | 5 | 1 – 8 | kΩ |
| HRV sampling rate | 64 | 32 – 128 | Hz |
| Cue delay after REM onset | 8 | 4 – 20 | min |
| Haptic confirm intensity | 0.2 | 0.1 – 0.4 | G |
| BLE sync interval | 300 | 60 – 600 | s |