Sleep

How it works

The mechanics of this kit, plainly — what runs and when, where the data lands, and what you look at.

• Sleep sync runs every day · 7:30am and keeps the Your nights dashboard fresh. Every morning — reads a connected health account, if you have one, and redraws the board.
• Sunday read runs sundays · 8am and keeps the Your nights dashboard fresh. Sundays — one pattern seen in the week, and one small thing worth trying.
• What is captured lands in the Sleep log dataset, which lives at Data/Sleep Log in your vault — yours to open, search, and edit like any other file.
• What is captured lands in the Sleep target dataset, which lives at Data/Sleep Target in your vault — yours to open, search, and edit like any other file.
• The Your nights dashboard reads from the dataset and shows, at a glance: night by night, hours asleep · last night, hours asleep · average night, hours · against your target, this week · usual bedtime · usual wake · naps, last 7 days · average night, by what you mentioned · average night, by how rested you felt · nights at a glance · this week's pattern.

The wiring, in one breath: Sleep capture writes to Sleep log · Sleep target setting writes to Sleep target · Sleep log shown by Your nights · Sleep target shown by Your nights · Your nights kept fresh by Sunday read · Sleep capture given to Vale · Sleep target setting given to Vale · Vale runs Sleep sync · Vale holds Nights compared · Vale holds Shift and travel plan.

Getting the most from it

A kit earns its place when it changes what you look at and what you say, not when it is installed. This is the rhythm that makes it pay.

• Say how you slept in the morning, in passing — "about seven hours, up once" is plenty — or let a connected watch, ring or app sync it. Add whatever came with the night if it matters to you: a late coffee, a drink, a hot or noisy room, how rested you felt, a nap and how long. Vale never asks for any of it, and never rounds up or fills in a number you do not have; a blank is honest.
• Put a night right by saying it again: "last night was nearer six". A second mention of the same night corrects the first rather than adding a row, so the line never shows a dip that did not happen; a night a connected account brought in keeps its figures unless you correct one on purpose. Every row on the Sleep log is yours to edit by hand too.
• Read the board on Sunday after the read, not after one night. The line is the story and the last night is one dip on it; the usual bedtime and wake, and how much they wander, are the honest signal the board is built to show.
• Take the one small thing worth trying at the end of the Sunday read as exactly that: an option drawn from your own week, and nothing more. The read says where the short nights fell and what you said came before them, and in a week you did not log it sends nothing at all.
• Set a target only if a number genuinely means something to you. The "Against your target" figure is arithmetic, not a grade, and "No target" is a perfectly good state.
• The two averages, by what you mentioned and by how rested you felt, count only the nights where you said it, and they show what went together, not what caused what. Ask Vale "do my nights after a drink run shorter?" for the count each way with the working; if you keep Journal & Reflections or Training & Recovery, it can set your nights beside your mood or your sessions too.
• Facing night shifts or a long flight, ask for a timetable: Vale finds what a named health or sleep body says about moving sleep times, works it on your own usual times and keeps it as a note in your vault. No source, no timetable, and never a medicine.
• If poor sleep is wearing you down for weeks, take the one line Vale will say about a GP seriously. The kit keeps a record; it does not treat anything.

Make it yours

Nothing here is fixed. The pieces are ordinary agents, routines, datasets and dashboards, so anything you know about shaping those applies. Retire whatever earns nothing.

Things people usually change first

Say any of these in chat, or edit them on the kit’s page in the app.

• The target, or removing it entirely.
• When the Sunday read arrives, or turning it off and just keeping the board.
• Whether the morning sync runs at all — it does nothing without a connected account, and can be paused either way.
• How much Vale says back when you mention a night — most people want a word, or nothing.
• Whether Vale keeps what came with a night (how rested you felt, a coffee, the room, a nap) or just the hours.

Your first run

Installing starts a short setup conversation — not a form. Answer roughly, correct later.

1. Installing ends with "Meet Vale" — a short conversation, not a form: last night, if you remember it, goes straight on the log; the number of hours that counts as a good night for you, or no target at all, which is a perfectly good answer and is never asked about again. It never asks why you sleep the way you do. Before it asks, Vale looks at what 1Presence already knows and at any sleep tracker export or sleep diary in your vault, offers what it finds for you to confirm, and asks only for the gaps.
2. From then on there is nothing to open. Say "slept about seven hours, up twice" in any conversation and the night goes on the log; the board shows the line, the last night and the running average from the first night, and the usual bedtime and wake once a fortnight of nights is there.
3. Skip the conversation, or stop part-way, and the door quietly stays open: until your first night is on the log, the Kit page, the board and Vale's chat each carry an offer to carry on, and Vale offers it once the next time you talk. A target is the other part, and it is optional: tell Vale you do not want one, or that you have finished setting up, and it stops asking. The Sunday read stays silent rather than reading an empty log.
4. If you have a connected health account, the morning Sleep sync pulls the nights it recorded (twelve months back on the first run) and fills only what you did not say yourself; if you have not, chat alone works exactly as well and it will not pester you to connect one.

Watch the first pass, then tell it what you would have done differently — that correction teaches it more than any setup could.

The essentials

Learning, preferences and run costs work the same in every kit — so they are covered once, in the Kits guide.

Living with a Kit — the Kits guide →

← All kits