Daily meditation practice working full time: two buddies, not one, bracketing the workday from both ends

Because the morning and evening windows around a 9 to 5 are two different problems. The morning slot competes with sleep and a meeting calendar that wakes up at 9. The evening slot competes with dinner, family, and decompression. They almost never converge to the same UTC overlap with the same other human. The match engine in src/app/api/auto-match/route.ts treats each session as its own slot in the candidate pool, so your morning sit can be matched with one person on the planet and your evening sit with someone else entirely. The relevant code lives in lines 191 to 209, and the comment in the source reads 'twice-a-day practitioners should get two different buddies, per design'.

The matching cron builds a list of session slots, not a list of people. A person who sits twice a day appears as two rows in the slot list, one for morning and one for evening. The greedy pairing loop tracks usedSlots as a Set of strings of the form 'personId:session', not just 'personId'. So when your morning slot is consumed by a match with person X, your evening slot is still available to be matched with a completely different person Y. The same loop also tracks usedPersonPairs to make sure X and Y are not the same human, even by accident. Both Sets are visible in src/app/api/auto-match/route.ts.

It is the only filter the engine applies as a hard cut. Your morning sit time is converted to UTC at signup using your provided timezone, and the matcher rejects every candidate whose own UTC slot is more than 60 minutes off. For a working professional, this means a 6 AM local sit on the US West Coast can match a person whose 6 AM local is up to an hour away in UTC, but not a person whose 7:30 AM is on a different continent. The same +/- 60 minute test runs independently for the evening slot, against an entirely different candidate pool. The hard filter lives at line 164 of src/app/api/auto-match/route.ts.

That question is for an authorized assistant teacher at a 10-day course, not for this site. The Goenka tradition's recommendation for old students is two hours per day, and the right address for any operational question about your sit is dhamma.org and your assistant teacher. What this site can speak to is the calendar layer: the matcher does not care about duration as a hard filter, but it does soft-prefer same-duration pairings via the session_duration field on waitlist_entries. If you and your buddy both put down 60 minutes, the engine ranks that pairing above one where you put down 60 and the other person put down 30.

Three things, in order. First, an empty morning leaves the cell empty in any logging instrument; the page does not punish you. Second, if you cannot show up at the agreed Meet time for several days running, your buddy's signal will tell you the partnership is paused, not failed. Third, the system has a 3-day expiry rule for matches that never get confirmed, after which both people are returned to the pool with no penalty and a new match attempt starts. The expiry logic lives in expireStaleMatches in src/lib/db.ts. The whole architecture is built around the assumption that working calendars blow up, not around the assumption that they will not.

Yes. The morning and evening matches are independent records. You can let the evening match expire on its own without touching the morning relationship, and re-enter the pool for evening only when your calendar gives that hour back. There is no streak counter in the system to penalize the gap, no leaderboard, no churn metric pointed at you. The morning buddy never sees the evening match, and the evening buddy never sees the morning one.

An app reminder pings your phone. A buddy notices an empty Meet room. The asymmetry is the entire point. For working professionals the binding constraint is not motivation, it is whether something other than yourself notices the absence. The matcher engineers that 'something' as a real human, twice a day if you want, on a permanent Google Meet link that does not expire and does not need a subscription. Apps are addressed in more detail at /t/best-meditation-apps-april-2026.

The matcher does not care about US time zones at all. It cares about UTC. A 5 AM morning sit in Singapore and a 5 AM morning sit in Berlin are not the same UTC slot, and they will not match each other; they will each match a different cohort, possibly someone in India for one and someone in Egypt for the other. The point of converting to UTC at write time is that the pool is global. A working professional in any time zone has a real chance of finding two different humans, one for each session, somewhere on the planet whose day is shaped to overlap.

The site is built for old students of S.N. Goenka 10-day courses, because the technique itself is transmitted at those courses by an authorized assistant teacher and not on this site. The signup form has an old-student field for that reason. If you have not sat a course yet, the right next step is dhamma.org. Once you have sat one, the buddy match is here, free, and the dual-session option is there for full-timers from the start.

The repo is open. The cron handler is /src/app/api/auto-match/route.ts, the eligibility filter starts around line 78, the +/- 60 minute UTC test is at line 164, and the dual-session pairing logic is at lines 191 to 209. The companion offline runner is /scripts/find-matches.mjs, which executes the same algorithm against the database for inspection. Everything described on this page can be read in a few hundred lines of TypeScript. There is no opaque ranking model, no engagement score, no upsell path.