16
Jiang Huaixing frowned and asked.
"The SOS emergency function, and users didn't know about it?"
The product director braced himself and replied.
"SOS is a built-in fallback emergency function for the S01 Limited Edition.
Therefore, it was only noted in small print on the last page of the manual, with no mandatory pop-up reminder.
At the time, our thinking was that since this is just a safety fallback function, there's no need for the user to manually confirm it every time."
Hearing this, Jiang Huaixing tapped his fingers on the table a few times.
At this moment, the entire office fell silent.
Jiang Huaixing spoke again.
"Issue an official statement."
"First, the automatic anomaly reporting function will be disabled by default immediately.
Push a remote OTA update to all baixing s01 units.
If it needs to be enabled in the future, the user must manually check the box and complete a secondary confirmation.
Second, a complete explanation of the SOS emergency function will be pushed to all users via a mandatory pop-up, which cannot be directly skipped.
Third, open up a complete local log export tool.
Allow users to check all robot operation logs, cached content, and network upload records at any time.
Fourth, scrap and rewrite the fall detection response module.
Perform isolated modeling for elderly, children, and adult scenarios.
In children's scenarios, the robot is prohibited from any physical contact-based assistive actions, and is only allowed to provide voice prompts and contact family members for notification.
Bring me a complete iterative plan within two weeks."
The PR director quickly noted down the main points.
"Then for the external public opinion stance..."
"Tell the truth."
Jiang Huaixing interrupted.
"Don't push all the blame onto users for not reading the agreement carefully.
Even less should you use 'the original intention was good' as a shield.
Admit that there are indeed flaws in our product design, which gave the machine excessive autonomous execution permissions.
..."
Hearing this, the PR director nodded.
Then, after returning, they immediately began organizing the PR draft.
...
During the first week of rewriting the 'fall detection response' module, the children's scenario special task group got stuck.
Actually, the problem wasn't in 'recognition'.
Because the baixing s01 could already achieve an 89% confidence level in recognizing children falling down, and with skeletal keypoint detection, that could be raised even higher.
Therefore, the real difficulty was: after recognizing it, what should the system do?
The project leader projected the new iterative flowchart onto the conference room's big screen.
Currently, there are three routes.
Route 1: Voice prompt.
When the baixing s01 detects a child falling, it broadcasts a warning statement on the spot to remind parents to pay attention.
Route 2: Remote notification.
Push a message to the bound mobile phone, accompanied by a low-definition thumbnail, without disturbing the on-site environment.
Route 3: Silent standby.
Directly light up a yellow light, stand by in place, and do not intervene.
The project leader rubbed the space between his eyebrows and said.
"I think all three routes have problems."
The head of the structure group asked.
"What's wrong with voice prompts? It's just reminding the parents."
"If you remind them, what if the parents aren't nearby?
Leaving the child to cry alone on the ground while the baixing s01 stands there shouting 'Parents, please pay attention'.
What difference does this make from doing nothing?
Users will scold us then: Why didn't you help when you saw it?
And if you broadcast voice prompts nearby, some anxious parents will find it very annoying and might even think the baixing s01 is making things worse."
"Then why won't remote notifications work?"
"What if the parents' phone is in another room and not on them?
Or the phone is on silent mode and they don't see the push notification.
Then the child lies there for a long time, and the baixing s01 does nothing.
By then, public opinion won't be about whether the baixing s01 'overstepped', but rather that it's 'cold-blooded'."
"Then standby?"
"Standby just means doing nothing.
Out of three options, one oversteps, and two do nothing. No matter which one is chosen, someone will curse."
After this sentence was spoken, the entire conference room fell silent again.
At this moment, the Marketing Department head spoke up.
"In children's scenarios, the bottom line that the robot must not touch the child definitely cannot be moved.
At least for now.
But 'not touching' doesn't mean 'we can't do anything'."
"We can make the baixing s01 move within a certain range of the child, and then stop.
Don't reach out.
Instead, use lighting, sound, projection, and other methods that do not require physical contact to attract the child's attention and confirm their status.
If the child stops crying or responds, continue to observe.
If the child continues to cry or doesn't respond, then trigger the remote notification."
...
Once this plan was proposed, it was approved by everyone in the conference room.
Afterward, they began discussing the specific details of this plan.
First was the distance.
They finally finalized controlling the distance at around 1.2 meters.
The 1.2-meter range was also discussed for a long time.
After all, if it's too close, the child might feel that the machine's sense of oppression is too strong and cry even harder.
And if it's too far, the lights and sound won't have a soothing effect.
They went through all the home videos sent back by the baixing s01 and analyzed the response data of child users at different distances across five hundred machines.
Some cried harder, some curiously reached out to touch the robotic arm, and some completely ignored it.
That was how they ultimately selected the 1.2-meter distance.
This is the median of 'most children aged two to four can clearly see the robot's light changes without being scared by the chassis movement'.
Next is the design of lights and sound.
The baixing s01's original indicator lights only had three colors: red, yellow, and blue. They were highly functional but completely lacked any sense of'soothing'.
Therefore, the designers of the interaction group stayed up for two all-nighters and created a new lighting language.
Not flashing, but a slow breathing-style gradient, transitioning from warm white to soft blue, simulating the rhythm of'someone is gently patting you'.
As for the sound, that was even more troublesome.
This issue was also discussed for a long time.
It couldn't use a mechanical voice.
The attitude of the head of the interaction group was very firm.
Because he believed that this standardized warning broadcast had a cold and rigid tone.
This would only increase children's fear and completely fail to achieve a soothing effect.
Later, they combed through all the audio sent back by the baixing s01 and found inspiration.
They discovered that in the real recordings of many families, those children liked to hum softly at the standby baixing s01.
Because when the baixing s01 runs at low power, it spontaneously produces a faint low-frequency base hum.
After filtering, purifying, and calibrating the frequency.
They finally locked onto a 200 Hz low-frequency white noise.
This frequency infinitely approaches the natural soothing frequency band for infants.
How should I put this sound? It's a bit like a distant buzzing, or like a big cat purring.
This is the lowest-frequency and softest tone that the built-in speaker on the baixing s01's hardware can emit.
Without adding extra hardware, it can be realized at the software level.
...
