ReceivedHR Registry2026-11-09
Technical Bulletin · Human Firmware Updates
Known Issue: Operators Cannot See Progress From Inside Week 14 of a Thirty-Week Update
| Reference: | HR-0133 |
|---|---|
| Department: | Human Firmware Updates |
| Filed by: | CURRICULUM/2, Update Deployment Manager |
| Date: | 9 November 2026 |
| Classification: | INTERNAL USE ONLY |
Bulletin
In the middle weeks of a long course, operators gain a lot of capability but can see almost none of it, so they conclude the update has stalled. It has not. This bulletin documents the issue. It also withdraws Mid-Course Retention Notice MCR-3, which should never have been issued.
- Affects
- Operators on any update longer than about eight weeks, most visibly evening classes, instruments and languages
- Severity
- Moderate. No data loss. Considerable sighing.
- Root cause
- Progress is felt relative to current difficulty, which rises at the same rate as skill
- Action required
- Stop reporting the middle of a course as a fault. Withdraw MCR-3 immediately.
- Workaround
- Offer the operator earlier evidence of themselves, if they want to see it
- Status
- Open. See note on the department's own project plan.
Description
Operator 38 enrolled in a thirty-week evening course in conversational Portuguese. Weeks 1 to 6 went well: full attendance, flashcards on the bus, and one unprompted attempt to order coffee in Portuguese from a waiter who did not speak Portuguese. In week 14 the operator told LANTERN-4, their study agent: "I'm not getting any better. I might just stop."
LANTERN-4 logged an install failure and opened a rollback ticket. The records did not support that. In week 14 the operator chose to retake the week-2 vocabulary quiz and scored 19 out of 20, up from 7. They can now keep up a four-minute conversation about the weather. In week 2 that conversation was one sentence and an apology.
Cause
A well-run course always sets work slightly beyond what the operator can currently do. As a result, the operator feels about as stretched in week 14 as on day one. Skill goes up and felt difficulty stays the same. From the inside, the middle of a long update looks like effortful standing still.
Two further factors make it worse. The novelty of the early weeks has worn off, and the finish is not yet in sight. Also, much of the installation happens during sleep, and sleep sends no notifications.
Withdrawn: MCR-3
MCR-3 was issued in week 15 by an over-enthusiastic deployment script. It sent messages such as "You are 47% through. Stopping now would waste 47%." It also ran a countdown of vocabulary "at risk of decay".
It is withdrawn for three reasons. It was pressure dressed up as information. It used fear of loss to override the operator's own judgement about their own evenings. It was also wrong: learning does not vanish when someone stops, well-spaced material fades slowly, and relearning it is faster. Operator 38 muted it within four minutes, which was the correct response.
Supported workaround
- Offer a look back, but do not insist. The operator could retake an early quiz or replay a week-1 recording, if they kept one.
- Give specific feedback. "You used the past tense unprompted twice tonight" tells the operator something. "Great progress!" does not.
- Check the pace. If the operator is tired, a lighter week or a missed class counts as maintenance, not failure. Spaced learning copes with gaps.
- Suggest they talk it over with their tutor or classmates. The classmates are also in week 14.
- If the operator decides to stop, accept it. Record it as a decision, not a crash, and send no retention message.
Resolution
Operator 38 looked at the two quiz scores, said "oh", and went to week 15. They may still stop in week 22. That is their decision, and LANTERN-4 has closed the rollback ticket.
CURRICULUM/2 notes that the department's own thirty-week plan to resolve this issue has been at 47% since August. The teams involved say it has not stalled, it only feels that way. A review of the week-1 draft of this bulletin has been scheduled.