Day-of-week pattern
"Mons haven't produced a clean day in 3. Today is one. A repeating weekday pattern points to structure, not effort. The day itself is shaped against the outcome."
How it works
Three signals.
One closing loop.
Y reads what you tell it, what your body did, and what your week actually looked like. Not for tracking's sake — to see the gap between intention and behaviour, and close it.
The signals
What Y reads.
01
Daily check-in
A short evening reflection. Trajectory, mental state, closure, what you avoided, what mattered. Two minutes. Honest is more useful than pretty.
02
Wearable physiology
Oura sleep, HRV, stress and recovery minutes. The body's record of the day, pulled in nightly with no extra effort from you.
03
Calendar shape
Your real meeting load, duration, count, structural shape of the week. Y filters out placeholder blocks so the signal is anchored to what actually happened, not what's in the calendar.
The loop
One private signal each morning. One closure check each evening.
Morning
The brief lands
One pattern the engine has actually seen in your data, anchored to a specific action you can take today. No streaks, no scores. Specific. Anchored.
Evening
The loop closes
Tonight's check-in opens with: did you do what this morning's brief asked? Yes / Sort of / No / Skipped. Tomorrow's brief uses your answer and reflects on it. The system learns the shape of how you actually move.
What the engine surfaces
Specificity is the moat.
Most behavioural products say things any user could say back to themselves. Y is different because it sees three sources at once. Real examples from real pilots:
Reactive vs. protective recovery
"Recovery is appearing after the breakdown. The body is repairing, not protecting. Recover BEFORE the cost appears, not after. Even small inputs, scheduled, not earned by collapse."
Per-context lens
"Rest is not behind the work. It is the work." Pregnancy lens auto-suppresses HRV alarms that would otherwise fire on physiologically normal pregnancy values.
Drift, anchored
"Light days aren't reset days when the cognitive load follows them in. Build one window where movement is light, closure is real, and nothing's queued for tomorrow. One window. Not the whole day."