Vertex Macro | Ferryboat Computer Club 11: The Broadcast with No Speaker

The Eleventh Echo Pier

The Broadcast with No Speaker

Two years after the Eighth Unsent Letter became public, the Coastal Youth Digital Learning Center was already operating under a new team.

Su Qing served as director, Aoi led public participation, and Jiahao was the technical learning team's official coordinator. Peter, David, and Tommy still attended some Meetups, but they were no longer present in every decision.

Early one Saturday morning, before the center had opened, the public-address system along the riverfront suddenly came to life.

"Everyone, proceed immediately to Assembly Area Two. Everyone, proceed immediately to Assembly Area Two."

Nearby shopkeepers raised their shutters. Morning runners stopped. Several passengers waiting for the ferry turned toward the youth center. Yet the staff on duty had no idea what had happened.

Jiahao rushed into the control room.

"Who activated the announcement?"

The system showed no operating record. It displayed only a five-year-old test recording playing on a loop.

After receiving the call, Peter ordered the team to stop the broadcast without deleting any records. The staff silenced the public speakers, preserved the system state, and sent people outside to explain that there was currently no evacuation event.

The crowd gradually dispersed after fifteen minutes.

"It was only an equipment malfunction," a city maintenance worker said. "The scheduling module may have activated by mistake."

"Why could a test recording use the official emergency channel?" David asked.

"It was more convenient for testing in the past."

"Why is there no audit record?"

"The old system did not have full audit capability."

"Then why is it still connected to the production environment?"

The maintenance worker had no answer.

Su Qing looked up at the silent loudspeaker.

"Nobody issued an order just now, yet the entire riverfront heard one."

"A voice can still be treated as authority after it has become separated from its speaker," Tommy said, "especially when it comes from a public system."

The center formed an investigation team. Peter handled the technical incident, David examined permissions and responsibility, Jiahao organized the equipment history, Aoi interviewed affected residents, and Tommy reviewed whether the same problem existed in other language versions.

Jiahao titled the incident page "The Broadcast with No Speaker."

The title did not mean that nobody was responsible. Responsibility had been divided into too many fragments. Someone had made the recording, someone had installed the system, someone had maintained it, and someone had preserved the old settings. In the end, nobody could explain why an expired sentence still had the power to order everybody to leave where they were.

The eleventh story began with an echo that had no visible speaker.

Chapter Two: Who May Press the Button?

The investigation found eleven different ways to activate the broadcast system.

The fire department could activate it. So could the city disaster office, the youth center's duty room, and ferry control. Two maintenance companies still had remote test permissions, while an old tablet contained an administrator account that had never been disabled.

"Do eleven entrances mean we have excellent redundancy?" Jiahao asked.

"They may also mean nobody knows the actual boundary," Peter replied.

The city representative believed that an emergency system was safer when more people could activate it.

"If only one department has the button and nobody can contact it, we have a problem."

"The problem is not the number of entrances," David said. "It is what each entrance can do, under what conditions it can do it, and who must explain the action afterward."

They tested the permissions one by one. The maintenance companies could play official evacuation announcements as well as test sounds. Ferry control needed to notify only the pier, but it could broadcast across the entire riverbank. A youth-center duty officer could start an announcement but could not cancel a riverfront-wide message.

"They can start it but cannot stop it?" Aoi asked.

The maintenance worker nodded.

"Cancellation was limited to the city because we feared somebody might stop a real warning by mistake."

"What if the city cannot be reached?"

"The procedure does not say."

Peter redesigned the permissions. Test audio could play only on a test channel and could not connect to public loudspeakers. Official messages were divided into building, pier, riverfront, and city scopes. The person activating a message had to select a reason, scope, and review time. If the system went offline, a physical button could still be used, but it would trigger local recording and a later audit.

David required every activation power to have a corresponding stop or transfer process.

"Power must be designed not only to begin, but also to end."

The city representative worried that the interface would become too complicated.

"During an emergency, people do not have time to review many options."

Jiahao proposed a situation-based interface. Fire, flooding, equipment incidents, and unknown conditions would each have a clear entry point. The system could recommend a scope according to the location, but it would not publish automatically. The user still had to confirm the facts on site.

During the first drill, the duty officer issued a building-level alert in forty seconds and correctly published a recovery message after the event ended.

"Speed does not mean removing judgment," Peter said. "It means preparing in advance what can be prepared during ordinary times."

Chapter Three: Grandma Chen Did Not Hear the Same Message

When Aoi interviewed residents, she discovered that the same broadcast had not been the same message in every person's ears.

Most young people knew the location of Assembly Area Two because they had participated in drills. Nearby shopkeepers assumed that it was an internal youth-center announcement and did not act immediately. Several older residents heard only "proceed immediately" and did not know where they were supposed to go.

"The loudspeaker was loud," Grandma Chen said, "but the wind carried away the second half. I knew only that something sounded urgent."

A recently arrived resident could not understand the main-language version. He saw everyone moving and simply followed them.

Tommy inspected the multilingual settings. The second-language announcement played ninety seconds after the main version. Worse, the translation used a word closer to "shelter" than "assembly area," which might make people believe that long-term accommodation was available there.

"The wording is not literally wrong," the city translator said.

"Emergency language cannot be judged only by whether it matches a dictionary," Tommy replied. "We must ask what listeners will do after hearing it."

Ruoqing joined the design work and proposed short sentences, repeated locations, directional guidance, and visual lights. The announcement would no longer say only "Assembly Area Two." It would say:

"Proceed to the east-side assembly area on the second floor of the youth center. Enter through the riverfront entrance and follow the yellow lights."

Electronic displays and mobile notifications would provide synchronized information for people with hearing difficulties. For people who did not use phones, on-site guides and direction lights had to work independently.

"If different channels update at different speeds, which one is official?" David asked.

"Every channel will show the update time and incident number," Peter replied. "If the channels disagree, the on-site commander must publish a correction. Users cannot be left to guess."

After testing the new version, Grandma Chen said, "This time I know where to go, but the text is still too small."

Jiahao immediately wanted to enlarge everything.

"First test different distances and lighting conditions," Ruoqing said, stopping him. "If everything becomes larger, the page may no longer contain all the essential information."

After three rounds of testing, text, sound, lights, and on-site guidance finally supported one another.

"Sending the same sentence does not mean everyone receives the same message," Tommy wrote in the report. "Real communication is measured by whether the other person can take a safe next step."

Chapter Four: The Recordings Jiahao Wanted to Delete

After the investigation, Jiahao wanted to delete every old test recording.

"They are outdated, and this time they nearly caused confusion."

"Outdated content should leave the live system, but not necessarily be deleted completely," Peter said. "Some recordings are incident evidence and may have training value."

"How long should they be retained?" Su Qing asked.

Nobody answered immediately.

The old system contained more than four hundred audio files. Some had no dates, some had no language labels, and some referred to assembly areas that no longer existed. Several even contained the names and private telephone numbers of former administrators.

"Retention is not free," David said. "The more data we keep, the greater the risk of misuse, exposure, and confusion."

Jiahao proposed three categories. Current official messages would remain in a controlled system. Incident-related recordings would have defined retention periods and restricted access. Pure tests, duplicates, and material of unknown origin would be reviewed and deleted.

Tommy added that multilingual versions could not be removed one language at a time. Otherwise, future records might preserve only the main-language history and hide the translation problems that had occurred.

"But we cannot permanently retain every person's voice in the name of organizational learning," Aoi said.

The center contacted recorders who could still be identified and explained the purpose and retention period. Personal recordings without verifiable permission and without necessary incident value were deleted. Current staff recorded new training material instead of repeatedly using the voices of people who had left.

When Jiahao deleted the first group of files, the system required a reason.

He wrote:

"Not because the past has no value, but because the past should not continue issuing orders to the present without an expiration date."

Chapter Five: Peter Receives His Own Voice

While new announcements were being recorded, the city proposed using Peter's voice.

"People know you. A familiar voice will inspire greater trust."

Peter recorded sample messages for fire, flooding, and service restoration. His voice was calm and clear. It did sound more approachable than a synthetic voice.

"What happens after you leave this role?" David asked.

"The recordings can remain in use," the city representative replied. "That is also a public contribution."

"What if policy changes and someone edits the recordings into a new message?" Peter asked.

"Technical controls can prevent that."

"What if I want to withdraw permission?"

The representative fell silent.

Peter remembered the way organizations had once borrowed his name as an endorsement. A voice, like a name, could add trust to a system while making people believe that he remained responsible.

He proposed licensing terms. The audio could be used only for approved original sentences and could not be synthesized into other content. Permission would last two years, after which it had to be renewed. Every playback would identify the responsible incident authority rather than treating Peter personally as the source of the command. If the material became outdated or was misused, he could require its removal.

The city considered the conditions excessive and chose a professional voice actor instead, applying the same licensing principles.

"Do you regret it?" Aoi asked. "Your voice might genuinely have reassured people."

"I can speak on site, and I can record messages for limited uses," Peter replied. "But I do not want a recording to keep making decisions in my name during a future I know nothing about."

In the end, Peter recorded only an educational video explaining how to distinguish test, warning, evacuation, and recovery announcements. The video clearly displayed its recording date and reminded viewers to follow the current official notice.

He did not lend his voice to permanent authority.

He gave listeners a method for judgment instead.

Chapter Six: David's Echo Index

To measure the effectiveness of notifications, David created an Echo Index.

It calculated delivery rate, understanding, correct action, repeated forwarding, and correction time. A higher score meant that a message was better at guiding safe action.

In the first test, the main-language mobile notification scored ninety-two. The public broadcast scored sixty-eight. The paper contact tree scored only forty-one.

The city immediately proposed reducing paper communication and manual notification.

"If their scores are so low, resources should be concentrated on digital channels."

"What score does the mobile notification receive during a power and network failure?" Grandma Chen asked.

David had not included that scenario.

"The paper contact tree is slow in ordinary times," Uncle Zhou said, "but it tells me to call the two neighboring shops. Did the model count that relationship?"

It had not.

David looked at his model.

"Once again, I turned the easiest ordinary scenario to test into the main definition of value."

He redesigned the assessment and removed the single total score. Ordinary efficiency, offline resilience, accessible understanding, cross-language consistency, on-site usability, and recovery notifications appeared separately.

The paper contact tree was inefficient during ordinary times but strongest during network failure. Mobile notifications were fast but failed to cover people without smartphones. Public broadcasts could reach the riverfront quickly but were affected by wind and noise.

"Which channel is best, then?" Su Qing asked.

"No channel can be best alone," David replied. "The system needs each channel to continue when another fails. It does not need every channel to compete for one championship."

"You canceled the ranking again," Jiahao said with a laugh.

"Because this time we are comparing tools, not effort."

Chapter Seven: Tommy Does Not Translate the Warning

During a multilingual warning drill with overseas partners, the organizer asked Tommy to translate every message live.

He refused.

"Emergency notifications cannot depend on me hearing and translating them on the spot. If my connection fails, I mishear something, or I am absent, the entire language version disappears."

"But human translation sounds more natural," an overseas partner said.

"Natural does not mean verifiable. Emergency sentences need prior testing, approval, and version control."

They created a core message library covering tests, caution, activity suspension, movement to assembly areas, remaining in place, and recovery. At least two people familiar with local usage reviewed each language version, and every version underwent scenario testing.

Tommy remained involved, but his role changed from sole translator to cross-language process designer.

During the drill, one version translated "remain where you are" into wording closer to "remain inside the building." In a fire, those instructions could produce entirely different actions.

The team immediately stopped that version, issued a correction, and reviewed the related messages.

"Is the person who translated it responsible?" a student asked.

"That person is responsible for explaining and correcting the error," Tommy replied, "but the whole system problem cannot be placed on one person. Why was there no second review? Why did we discover the problem only during the drill? Those questions also require answers."

"Responsibility is not divided equally until nobody is accountable," David said. "It is allocated according to what each layer could actually control."

Chapter Eight: Aoi Hears Too Many Opinions

After the broadcast incident, the center invited residents to comment on the new notification system.

More than four hundred responses arrived in one month.

Some people wanted louder announcements, while others found them too noisy. Some wanted each message repeated five times, while others thought twice was enough. Some requested more languages, while others worried that longer announcements would delay action.

"If we accept every suggestion, the system will contradict itself," Aoi said.

"Does public participation mean we merely collect opinions and then decide everything ourselves?" Jiahao asked.

"Participation does not mean every response becomes a setting directly. People need to know which matters are preferences, which involve safety baselines, and which require testing."

Aoi divided the feedback into understanding, accessibility, noise, privacy, language, and operation. She then published how the center would handle each category. Items that could be corrected immediately were updated. Conflicting preferences went into testing. Safety-related items were evaluated jointly by professionals and users.

"You still did not follow my recommendation," one resident complained.

"Participation guarantees that your suggestion will be read, categorized, and answered," Aoi replied. "It does not guarantee adoption. If we reject it, we must explain why."

She also acknowledged that the most common views did not necessarily come from the people most affected. Online-form users responded heavily. Residents who did not use the internet were nearly absent.

The center added telephone interviews, on-site tests, and paper responses. Aoi did not treat four hundred online comments as the opinion of the whole community.

"Volume is not population," David said. "Silence is not agreement either."

Chapter Nine: The Eleventh Echo Pier

The revised public notification system passed acceptance testing. There were eleven major message points along the riverfront, including the ferry terminal, youth center, old market, bus interchange, and community activity grounds.

Ruoqing named it "The Eleventh Echo Pier."

"Why call it an echo?" the city representative asked. "Did this incident not teach us that echoes are dangerous?"

"The danger is not that a voice repeats," Ruoqing replied. "The danger is that repetition loses its source, time, and responsibility. A good echo tells people where it came from, whether it remains valid, and when it stops after the event ends."

Every message point displayed the same incident number and update time. Users could confirm the same incident through electronic displays, text messages, the website, or on-site personnel. Test messages began with a different tone and could not use official evacuation wording.

The system also made recovery a mandatory stage. Every restriction, closure, or evacuation notice had to name the person responsible for announcing its end. If the event remained unresolved, the system had to issue periodic updates instead of leaving people waiting indefinitely.

"Security processes used to focus on sounding the alarm," Peter said. "Now we finally treat a return to ordinary life as part of security."

"And every language must recover together," Tommy added. "The main language cannot announce that people may return while everyone else remains trapped in a state of danger."

"Every echo needs an expiration date," David said. "A warning without one eventually becomes background noise."

Chapter Ten: After the Voice Stopped

Six months after the Eleventh Echo Pier began operating, a ferry developed a mechanical fault while approaching the pier.

There was no collision, and nobody was injured, but the pier had to close temporarily. Ferry control issued a pier-level notice directing passengers to another boarding point.

The message appeared simultaneously through the public broadcast, electronic displays, text messages, and on-site personnel. Every version included the incident number, alternative location, and next update time.

An older passenger had no phone and could not hear the broadcast clearly. An on-site guide used the direction lights and paper instructions to lead him to a temporary shuttle bus.

An overseas traveler saw the second-language display but was unsure whether "suspended" meant that the service had been canceled for the entire day. Tommy was not present, but the tested message library stated clearly:

"This pier is temporarily closed. Ferry service has moved to the temporary eastern pier."

Service resumed forty minutes later. Ferry control issued a recovery notice, and the displays showed that the original pier had reopened.

The event caused no major confusion.

The post-incident review still found problems. One loudspeaker at the old market was too quiet. The temporary pier lacked sufficient lighting at night. One worker mistakenly treated a test group as an official recipient list.

The city wanted the success headline to read "Zero Injuries, Zero Complaints."

"No complaints does not mean everyone understood," Su Qing said. "We need on-site observations, delay records, and information about the people who required extra assistance."

The center interviewed different users. Most had understood the next step, but some had moved only because they followed the crowd. The next improvement added direction-confirmation points. Guides would not simply say "go forward." They would confirm that the person knew the destination.

That evening, Peter, David, Tommy, Aoi, Jiahao, and Su Qing stood beside the river as the final recovery announcement ended.

The loudspeaker became silent.

"I once thought a reliable system should speak loudly whenever needed," Peter said.

"Now we know it must also stop when it is no longer needed," David replied.

"And people must be able to ask who the voice belonged to, why it appeared, and whether it remains valid," Tommy said.

"A true public voice does not represent everyone merely because it is the loudest," Aoi said, watching the passengers pass. "It needs a source, a scope, and an expiration. Different people must also be able to understand and respond to it."

The tide clock rang on time without competing with the announcement. Signal lights illuminated the turn. The Tenth Tide-Mark Map showed the latest water level, and the ninth spare key remained sealed inside its secure box.

All those tools spoke in different ways, but none could replace human judgment.

A broadcast could tell people where to go, but it could not treat obedience as understanding.

Data could show how many people received a message, but it could not guarantee that every person knew the next step.

Translation could exchange languages, but it could not automatically exchange experience.

Public participation could collect voices, but it could not turn the loudest opinion directly into a shared decision.

The late ferry returned to the pier. Passengers boarded in order, the crew closed the doors, and staff confirmed that the pier broadcast system had returned to standby.

"What if another broadcast with no speaker appears in the future?" Jiahao asked.

"Trace the source, stop the spread, preserve the records, and confirm who owns recovery," Peter replied. "A system does not become permanently safe merely because it was once improved."

"Institutions lose vigilance most easily after success," David said. "People begin to treat the absence of incidents as proof that they will always be right."

Tommy turned toward the river.

"An echo can travel farther than the original voice. Before speaking, know the responsibility. After speaking, know when to let the voice stop."

Night wind crossed the pier. The loudspeakers did not sound again.

Silence no longer meant that nobody was responsible.

It meant the event had ended, recovery had been confirmed, and the system had returned the authority to speak to ordinary life.

The Eleventh Echo Pier stood beside the river without asking everyone to obey one voice forever.

It tried to do only one thing.

When speech was truly necessary, it helped people know where the words came from, why they had appeared, what they needed to do, and when they could stop being afraid.