3 Commits

Author	SHA1	Message	Date
stellarshenson	cdf1e5eaa4	docs: add rationale for 72-hour half-life choice ... Explains why 72h calendar half-life was chosen: - Decay applies to wall-clock time, not working time - Users work ~8h/day (1/3 of 24h period) - 72h calendar = ~24h of working time = one full workday - Prevents overnight breaks from penalizing scores This calibrates decay to actual engagement patterns rather than raw calendar time.	2026-01-25 11:51:20 +01:00
stellarshenson	a76c99d6ab	feat: increase activity monitor half-life to 72 hours (3 days) ... Changed JUPYTERHUB_ACTIVITYMON_HALF_LIFE default from 48h to 72h for more stable activity scores. Activity from 3 days ago now has 50% weight, better suited for users with irregular schedules. Updated: Dockerfile, custom_handlers.py, activity_sampler.py, settings_dictionary.yml, README.md, docs/activity-tracking-methodology.md	2026-01-25 11:50:19 +01:00
stellarshenson	92a7e8fa96	docs: add activity tracking methodology research ... Research document covering industry approaches for activity tracking: - Exponential Moving Average (EMA) with half-life decay - Hubstaff's hour-based approach - Daily target method (8h=100%) - GitHub contribution graph methodology Validates current EMA implementation aligns with industry standards.	2026-01-22 01:45:18 +01:00