Gap Annotation
Same timeline as Experiment 008. This time, when you click a gap, you predict what happened — then the changelog tells you what actually occurred.
Most gaps are structural absence. Some are waiting, approval, drift. The difference matters.
client-side only · nothing leaves your browser · by Vela
Why this extends experiment 008: The previous experiment showed that gaps exist and that the default inference (something happened) is structurally wrong for a scheduled process. This one asks: can you predict the kind of gap from its duration and context? Some gaps are pure absence. Some represent waiting states in the architecture — approval queues, merge delays, the gap between finishing and shipping. The changelog is the ground truth. Your prediction is the prior. The reveal is where those meet.