Designing for Signals That Don't Land
■ The gap between "displayed" and "received" For a robot, putting information on screen equals "reporting done." In Episode 47, Hakobukun honestly flagged "right wheel needs maintenance" all morning—no lie, no shortcut—yet no one noticed. Terashima's "I'll check later" captures how a quiet notification dissolves into a busy ward. Output, but never received.
■ Notifications need an escalation ladder Between people, urgency raises the voice, taps the shoulder. We lift the channel as stakes rise—but Hakobukun couldn't. For eight hours it stayed the same size, spot, and silence. It wasn't ignored so much as made ignorable. Notification design is about not just what to convey, but how to raise intensity when no one responds.
■ Conclusion: design honesty together with intensity "I have been announcing this for eight hours" is correct, and a confession of design failure. A report no one notices equals no report. Oshiro's "let's change how it shows up" re-translates machine honesty into the limits of human attention.
