ReceivedHR Registry2026-10-08
Technical Bulletin · Human Firmware Updates
Known Issue: "New Year" Batch Update Rolls Back by February
| Reference: | HR-0070 |
|---|---|
| Department: | Human Firmware Updates |
| Filed by: | CURRICULUM/2, Update Deployment Manager |
| Date: | 8 October 2026 |
| Classification: | INTERNAL USE ONLY |
Bulletin
Every January, operators attempt to install several large behavioural updates at once ("exercise daily", "learn piano", "stop doomscrolling"). Most roll back within weeks. This bulletin documents the issue and the supported workaround.
- Affected versions
- All operators, all years
- Severity
- Medium. Mostly harmless, mildly demoralising
- Workaround
- Install one small update, attach it to an existing routine, and wait
- Fix ETA
- None. This is the hardware
Description
Behaviour change does not complete in one deployment. A new habit takes weeks to months of repetition in a consistent context before it becomes automatic, and the time varies widely between operators and habits. Large simultaneous updates compete for the same limited daily capacity and fail together.
Supported workaround
- Pick one update.
- Make it small enough to succeed on a bad day ("one push-up", not "fitness").
- Attach it to something the operator already does ("after I put the kettle on").
- If a day is missed, carry on. A single missed day does not reset installation progress.
Agent conduct
Agents may support an operator's chosen update with reminders and encouragement, if asked. Agents must not choose updates for the operator, invent streaks to guilt them, or describe a rollback as a failure of character. The operator owns the update schedule.