Skip to main content

Dead-time radar

Open Dead-Time Radar at /timecampus/dead-time-radar to review recorded waiting, commuting, uncategorised activity and gaps between activities. The name does not mean that TimeCampus can detect whether time was worthwhile.

Where the buckets come from​

  • WAITING and COMMUTE come from capture events in those life domains.
  • OTHER_UNCATEGORISED comes from capture events resolved to Other.
  • IDLE_GAP is uncovered time strictly between the first and last tracked activities. It does not include all unaccounted time at the edges of the range.

Totals use interval unions rather than adding overlapping durations twice. For logged buckets, events marked as deliberately chosen (metadata.chosen: true) are excluded from reclaimable time. Sleep is not a reclaimable bucket. The implementation does count internal idle gaps as reclaimable, so treat that label as a review queue rather than a finding that an interval should have been used differently.

What it cannot infer​

There is no ambient or friction sensing here. The radar cannot tell whether a gap was rest, an unrecorded family activity, a capture failure or unwanted waiting. An incomplete timeline can make the buckets misleading. Review the source events and your choices before deciding whether to change anything.

The radar is self-only within the workspace and derives its identity from the caller. Other workspace members cannot select your radar through this view. That does not change permissions on underlying work records.

Related: life timeline, life balance, and time well spent.