ONLY-13: weight waking-hours overlap, name a long-distance gap as the deal-breaker

main

Commit

karthik-rameshkumar5d ago

Two of the best-scoring couples were eleven hours apart and the card never said so. The timezone signal was worth 7 points, linear in the offset, and lost the deal-breaker slot to tabs versus spaces.

Replace it with overlap in waking hours, weighted 15. Each chronotype has a sixteen-hour local waking window (early birds up at 06:00, office hours at 08:00, night owls at 10:00); both windows are shifted to UTC and the signal is the share of the day both people are awake. Night owls in Bengaluru and Mexico City are awake together eight hours a day; an owl and a bird in the same city, twelve. Hours keeps its 23 points; the extra weight comes from stack, tone, PR size, pairing and indentation, and the weights still sum to 100.

A gap of more than eight hours marks the signal as a hard clash, and a hard clash is named as the deal-breaker regardless of the points ranking. It carries no flat cost: the labellers rated both long-distance couples in eval/couples.json in band knowing the gap, and a sweep showed a cost of three points or more moves them out of band. The card now says "Bengaluru and Mexico City are 11.5h apart, so dinner is a video call" and the score stays where the labellers put it.

Eval stays at 20/20. Tests cover the deal-breaker rule (including the boundary at exactly eight hours), the overlap values for same-city, same-timezone-different-rhythm and long-distance couples, and that moving the far partner closer raises the score and clears the deal-breaker. Two existing assertions moved to couples within eight hours of each other because distance now takes the slot for the pairs they used.

Co-Authored-By: Claude Fable 5.1 noreply@anthropic.com Entire-Checkpoint: 01M38XA8304R5HFBT520EZ0VJP

Checkpoints

Weight Timezone Overlap for Couple Matching

Claude CodeFable 5.1
View session
Checkpoint 1