# Sleep Low

> Paste a high-altitude trek itinerary - one night a line: place | sleeping altitude | highest point that day | note - with where you sleep the night before night 1, the unit (metres or feet) and whether you have had altitude sickness before. See the ascent drawn as a contour map from above (each ring is 500 m, the route spirals inward one pin per night), every night checked against common acclimatisation pacing rules, and the page's own pace line: the fewest extra nights that keep the plan to the rules. A metered pace check adds nights where they fit the route, names warning signs for the highest nights, sets turnaround rules, lists questions for the guide or operator and gives an on pace / add nights / rethink verdict; the page re-walks every change itself. General pacing guidance, not medical advice. https://sleep-low.skillsafe.ai/

## What it does

- Free, in the browser (pacekit.js, topo.js): reads pipe-, tab- or semicolon-separated lines, or "Place 3440 m" with no separator; altitudes take m, ft or km, and a bare number is read in the chosen unit. A leading "Day 3:" or list bullet is ignored.
- The rules: above 3,000 m (about 9,800 ft), sleep no more than 500 m (about 1,640 ft) higher than the night before; above 3,000 m, no more than three climbing nights in a row; a first night at 3,500 m (about 11,500 ft) or more after climbing over 500 m (a fly-in or drive-in start) is a high-risk start. Day hikes higher than the bed ("climb high, sleep low") are marked but never count as a night.
- Flags per night: high start, too big a climb, far too big a climb (over 1,000 m), 4th (or later) climbing night in a row, a night that does not climb, climb high sleep low.
- The pace line: a greedy repair that splits a climb that is too big into steps of 500 m or less above 3,000 m (one stop high enough is enough below 3,000 m) and puts a night that does not climb before every fourth climbing night. Stops are altitudes, never named places.
- Verdicts, in order: rethink (a high start, a repair of four or more nights, or any night at 5,500 m / about 18,000 ft or higher - expedition altitude), add nights (one to three), on pace.
- Metered, one task `pace`: `changes` `[{after_day, action, place, sleep_m, why}]` where action is rest (a second night at the place before) or stop (a new night strictly between two planned nights, `sleep_m` in metres); 3-5 warning signs `{sign, act}`; 2-4 turnaround rules; 2-4 questions for the guide; caveats.
- The page holds the reply to the rules: it inserts each change into the plan, refuses a stop that is not between its neighbours, shows a stop named with a place that is not in your itinerary as an altitude only, re-walks the revised plan and flags an "on pace" or "add nights" verdict that still leaves a night breaking a rule, any internal field name in the prose and any medicine dose.

## Limits

- Altitudes are as entered; the samples are made-up treks with made-up places. The 3,000 m, 500 m, three-night and 3,500 m thresholds are general guidance, and people acclimatise at different rates: anyone whose symptoms get worse should go down.
- Exports: Markdown (the nights, the changes, the warning signs, the turnaround rules, the questions), a CSV of the nights, and the contour map as SVG.

## Sources

- Built on the SkillSafe skill @travisjneuman/travel-planner: https://skillsafe.ai/skill/@travisjneuman/travel-planner
- The pacing rules follow widely published wilderness-medicine guidance on preventing acute altitude illness (for example the Wilderness Medical Society's clinical practice guidelines).
- Why now: October and November are peak trekking season in the high Himalaya, and interest in the big mountains is up - English Wikipedia pageviews for Tenzing Norgay rose from about 2,300 a day on 8 October 2026 to about 80,000 a day by 18 October (Wikimedia pageviews API).
- API: https://sleep-low.skillsafe.ai/api.html