Vertex Macro | Ferryboat Computer Club 04: It Began with an Unsigned Letter

The Fourth Signal Light

It Began with an Unsigned Letter

Two years after the Third Route was established, Peter, David, and Tommy rarely found themselves in the same city.

Peter had become a junior consultant at a cybersecurity company. In addition to account security and incident response, he designed digital-community safety courses for schools. David joined a market-research firm, analyzing data by day and continuing his study of institutions, trading, and the ways power shaped human choices by night. Tommy traveled between countries helping youth organizations build methods of cooperation, although he no longer placed himself at the center of every relationship.

The Third Route had grown as well.

Editors from different regions rotated responsibility for the LinkedIn Page. Meetup events took place every month, and many local channels had formed in Slack. Nobody could read every message, and no single school could represent all the members.

Everything appeared more mature than before.

Then, one Monday morning, an unsigned letter arrived in the governance team’s shared mailbox.

The letter said:

“You keep saying that power has boundaries and contributions must be recorded, but in some regions the same small group still decides the speakers, budgets, and exposure. People who are not invited into the inner circle can only volunteer. After someone expressed disagreement, three Meetup proposals in a row received no response. Please stop using ‘the community is growing’ to hide the fact that nobody is accountable.”

The letter provided no name and identified no region.

“Perhaps someone is merely upset that a proposal was not accepted,” said Yuna, the rotating chair.

“Or perhaps someone fears being excluded if they sign their name,” Ruoqing replied.

“How can we investigate without a name, date, or specific incident?” Mark asked.

The governance team debated for forty minutes without reaching a conclusion. Some wanted to ignore an unverifiable anonymous claim. Others wanted to publish the whole letter and let everyone judge. A third group suggested suspending every activity until the matter was resolved.

Peter listened online. He remembered early incidents in which people had hidden personal actions behind the phrase “a core-team decision.” He also knew that anonymous accusations could harm innocent people.

“Do not guess who wrote it or whom it describes,” he said. “Separate the institutional questions that can be verified.”

David entered four questions in the working document.

Did Meetup proposals have a response deadline?

Were speaker and budget decisions recorded?

Were the conditions for joining core groups public?

Had anyone suffered adverse treatment after expressing disagreement?

“Anonymous does not mean true,” Tommy said, “but it does not mean disposable either. This is a signal, not a verdict.”

Aoi had graduated from Aoba High School and now served as the Third Route’s student-governance representative.

“How do we answer someone whose identity we do not know?” she asked.

“First, announce publicly that we received concerns about the system and will examine the process, without publishing unverified accusations,” Peter said. “Then create a safe channel through which the writer can provide details.”

“The investigators cannot be administrators from the region under review,” David added. “The founders cannot handle it alone either. Otherwise, people will think we are grading our own work.”

A temporary review group was formed with members from different regions. Its four-week mandate allowed it to inspect processes and records, but not to punish anyone directly.

Aoi ended the public statement with one sentence:

“We will not treat anonymity as evidence, and we will not treat silence as proof that no problem exists.”

After the statement was sent, Peter watched the notification icon on his screen.

The first crossing had taught him how to begin. The second had taught him not to turn help into control. The Third Route had taught him how to move power away from the center.

Now they had to learn something else.

When a warning light appeared, they could not pretend the way ahead was safe merely because they did not know who had pressed the button.

Chapter Two: The Proposals Nobody Answered

The review group began with six months of Meetup proposal records.

On paper, anyone could submit an activity. The rules page clearly stated, “All members are welcome to propose talks, workshops, and partnerships.”

The actual data told another story. Of forty-eight proposals, twenty-one had received no response. Most approved proposals came from current or former administrators. First-time proposers waited more than thirty days on average.

More strangely, the system had no formal rejection status. A proposal was either approved or remained pending forever.

“We kept saying that anyone could submit,” Yuna said quietly, “but never promised that anyone would receive an answer.”

“A formal entrance does not guarantee a usable road,” David replied.

The reviewers contacted several proposers. One was Zhe, a vocational-school student studying network technology. He had proposed an Old Router Repair Workshop to teach students how to turn discarded school equipment into a practice environment.

“I waited two weeks after my first submission,” Zhe said. “Nobody replied. I asked on Slack and was told to wait. I added a risk plan to my second submission, but still heard nothing. After the third, someone privately told me the topic was not advanced enough and companies would not care.”

“Why was there no formal rejection?” Aoi asked.

“He said he did not want to leave a negative record and hurt my feelings.”

“Silence is not kindness,” David said. “It simply leaves the proposer to carry the cost of rejection alone.”

Another member had proposed an accessible-web study group. She was told to wait until the community became larger. In the same month, a generative AI talk featuring a famous speaker was approved in two days.

“Do you have selection standards?” Peter asked the management team.

“We mainly consider content quality, speaker ability, and community need,” a regional coordinator replied.

“Are those criteria written down?”

“Not completely. We know one another well and usually discuss things in a small group.”

“Who belongs to that group?”

“Several experienced people.”

“How does a newcomer join?”

“We look for long-term participation.”

“What counts as long-term participation?”

Nobody answered.

“You did not deliberately lock the door,” Tommy said, “but you installed the handle only on the inside.”

The review group proposed a new process. Every submission had to receive an initial response within seven days and a final status within twenty-one: approved, returned for revision, or rejected. Rejections had to explain the reason and what a future submission would need to improve. Evaluation criteria included learning goals, intended audience, operating requirements, risks, and excessive commercial promotion. A speaker’s fame could not be the only consideration.

At least one monthly slot would be reserved for first-time proposers. This did not guarantee approval, but it prevented every stage from going to people already familiar with the process.

Zhe’s workshop returned to review. Administrators worried that old equipment could create security risks, so Peter helped him design data-erasure procedures and an isolated network. Two weeks later, the event went live.

Only twenty-six people registered, far fewer than for a major talk, but nineteen repaired old devices successfully. Three schools then built shared network practice kits.

“I do not need every proposal to be accepted,” Zhe wrote in the feedback form. “I only want the person rejecting mine to have truly read it.”

Peter included that sentence in the governance report.

Sometimes a person did not need an immediate stage. They needed to know that someone was genuinely present behind the door.

Chapter Three: The Invisible Inner Circle

The reviewers soon found the inner circle described in the letter.

It was not an official Slack channel but a private messaging group. Five early administrators had created it for emergencies. Over time, it became the main place for speaker invitations, sponsorship negotiations, event dates, and staffing decisions.

Only the final conclusions appeared in official channels.

The members were not acting with evil intent. Private messages felt faster, and they did not have to explain every detail to hundreds of people. Yet speed produced another result. Anyone outside the group struggled to understand how decisions formed or what they had to do to participate.

“I am in that group,” Yuna admitted. “I always thought it was merely a working chat.”

“If most decisions are completed there,” Mark asked, “is it still merely a working chat?”

“Informal spaces are not inherently wrong,” David said. “Friends may talk, and coworkers need quick coordination. The problem begins when an informal space replaces formal decision-making without accepting formal responsibility.”

“Must every sentence become public?” one early administrator asked. “Nobody will discuss anything honestly.”

“No,” Ruoqing replied. “Drafts, questions, and disagreements may begin in a small group. But decision-makers, reasons, conflicts of interest, and final outcomes must return to the official record.”

“If the private group makes a bad decision,” Peter asked, “can the formal governance team overturn it?”

The administrator fell silent.

The answer was clearly no, because the private group’s members were also the most influential members of the official team.

“The problem is not the existence of the group,” Aoi said. “The problem is that power has no exit.”

They established three principles. Private groups could coordinate but could not become the sole repository of information. Decisions involving budgets, permissions, speakers, partnership commitments, or action against members had to be recorded in the official system. Any temporary decision not formally confirmed within seventy-two hours expired automatically.

People affected by a decision could inspect a relevant summary. This did not expose every private conversation. It told them who decided, on what basis, and how they could object.

“Does this not show that you distrust us?” the administrator asked.

“Trusting a person does not require everyone to trust that person forever,” Peter replied. “Clear records can protect you. If someone misunderstands your decision, you do not need status alone to prove your case.”

“A good community cannot operate only while good people hold power,” Tommy added. “It must retain a path for correction when ordinary people become tired, make mistakes, show favoritism, or become afraid.”

The private group was not forcibly dissolved, but it ceased to be an invisible decision center. At first, its members complained that work had slowed. Two months later, they found handovers easier because important context was no longer locked inside a few people’s chat history.

“Power loves rooms without names,” David said. “Not because every such room is evil, but because nobody knows where to knock.”

Chapter Four: An Event That Became Too Successful

Zhe’s router workshop produced unexpected results. Participants converted the repair process into public learning materials and built low-cost network practice kits. Several schools requested partnerships, and an equipment company offered sponsorship.

Three months later, the workshop expanded into Reboot Laboratory Community Day. More than five hundred people registered, and related LinkedIn posts received tens of thousands of views.

Suddenly, everyone called Zhe “the Router Teacher.”

At first he was delighted. Once, nobody had answered his proposal. Now executives sent connection requests, schools invited him to speak, and organizations asked him to help design formal courses.

Two weeks after the event, however, he had not updated the materials or answered questions about the equipment list. When another administrator reminded him on Slack, he replied, “I created the whole project. Nobody should change the content without my approval.”

“This feels familiar,” Aoi told Peter. “Can someone who was ignored begin controlling others after finally receiving a stage?”

“Of course,” Peter answered. “Experiencing unfairness does not automatically teach someone to use power fairly.”

David examined the records. Zhe had proposed the original concept, but more than twenty people had contributed materials, device security, sponsor communication, and event delivery. The open-license document allowed community improvements as long as contributions were preserved.

“The community ignored me before,” Zhe said at the governance meeting. “Now that the event has succeeded, everyone wants to take the result.”

“Your original contribution will not be erased,” Peter said. “But original authorship does not create permanent veto power.”

“Without me, the project would not exist.”

“That may be true,” David replied, “but it does not mean every future decision belongs to you. Founding is a contribution, not a contract for lifelong rule.”

“So once again, I merely opened the door for everyone else?”

“You did more than open a door,” Tommy said. “You proposed the method, guided the first group, and built the materials. All of that deserves clear recognition. But if later participants must obey your version forever, the door is only half open.”

Ruoqing proposed separating contribution from governance. Zhe would retain credit as founder and principal author and could lead the next technical edition. Budget, scheduling, and permissions would belong to different people. Major changes required technical-team review. Zhe had a vote but not a personal veto.

He resisted until one of the students who had edited the materials asked, “If you become busy with an internship next month, must everyone stop?”

Several days later, Zhe accepted the arrangement and uploaded all the source files to the shared repository.

“I thought protecting the result meant holding it more tightly,” he told Peter.

“Sometimes protecting a result means allowing people to change it without allowing them to erase what you did.”

Chapter Five: David’s Red Dashboard

After the anonymous-letter case, David designed a governance-risk dashboard.

Instead of general event performance, it monitored possible concentrations of power. Indicators included unanswered-proposal rates, repeated use of the same speakers, administrator tenure, budget concentration, average suspension handling time, and representation across schools and different groups on public stages.

To make risk easy to understand, he used green, yellow, and red.

On the dashboard’s first day, the southern region received three red indicators.

The news spread quickly. People wrote, “Southern governance has failed,” and called for its administrators to be replaced.

“You marked us red without asking us anything,” the southern coordinator said angrily. “Now everyone thinks something is seriously wrong.”

“Red means review required, not guilty,” David replied.

“That is not how people read it. The color has already delivered the verdict.”

Peter remembered the anonymous letter. They had said a signal was not a judgment, yet the dashboard had turned signals into labels through its most visible design.

Aoi investigated. The response rate was low partly because local schools had begun a new term and two administrators were ill. Speaker repetition was high because only a few local people could teach in both required languages.

The data were not false, but the interpretation lacked context.

“I gave too much power to what was easiest to display,” David admitted.

“We are willing to improve,” the coordinator said. “We simply do not want public humiliation before we are allowed to explain.”

They redesigned the dashboard. Red alerts were first sent privately to the relevant team, which received fourteen days to add context and propose improvements. Public pages showed confirmed systemic trends without ranking individual regions. Every indicator included its definition, data limitations, and reasonable alternative explanations.

If a region repeatedly refused to provide information, the public report would say “unable to verify,” rather than automatically labeling it normal or abnormal.

“Transparency is not throwing every number into sunlight and allowing the loudest person to interpret it,” David told the governance team. “It includes giving the people being described an opportunity to provide context.”

“Your smoke detector was connected directly to the school-wide broadcast,” Peter said.

“So I added human verification.”

“You admit that people matter more than dashboards?”

“I admit that a dashboard is a tool, not a judge.”

The southern region then created backup-administrator roles and added bilingual-speaker development to its next-quarter plan. The risks were not hidden, but the region was not defined by a red symbol.

Chapter Six: Tommy Refuses to Translate

The Third Route prepared to cooperate with an overseas student network. At the first meeting, the phrase “regional representative” caused a dispute.

The overseas network believed each region should appoint one representative to communicate decisions consistently. Third Route members feared that one representative would compress many opinions into a single voice.

Everyone turned to Tommy, expecting him to translate and reconcile the disagreement.

“Today, I will not translate the answer,” he said.

“But you understand both cultures best,” Yuna replied.

“I can explain what the words mean in different contexts. I cannot decide what either side should accept.”

He explained that the overseas group used “representative” to emphasize efficiency and accountability, not necessarily absolute power. He then explained that the Third Route did not oppose a contact person. It opposed a contact presenting a personal opinion as the will of an entire region.

Then Tommy muted his microphone.

The meeting became awkward.

“Perhaps we can separate the contact role from the authorized-representative role,” Peter suggested. “A contact carries information but has no automatic decision authority. The person becomes a representative only after receiving clear authorization on a specific matter.”

“Must authorization be proven every time?” the overseas student leader asked.

“For major commitments, yes,” David said. “For routine coordination, no. We can define each role’s authority in advance.”

“A region may also have two contacts from different backgrounds,” Ruoqing added, “reducing the chance that one viewpoint dominates.”

Both sides accepted the design.

“Were you not afraid the meeting would fail?” Peter asked Tommy afterward.

“I was.”

“Why not produce an elegant compromise yourself?”

“Because if the elegant answer exists only in my mouth, the conflict will return the next time I am absent.”

He paused.

“Translation is not merely replacing one sentence with another. Sometimes translators quietly remove the most difficult parts for both sides. The meeting appears harmonious, but the real disagreement remains untreated.”

“So you made them bear the cost of understanding one another,” David said.

“Yes, while giving enough context to prevent that cost from becoming mutual harm.”

The partnership adopted a two-level model. Each region had public contacts for information flow. Major issues used temporarily authorized representatives whose authority expired when the task ended.

Tommy’s name did not appear on the first line of the agreement. It appeared at the end under design contributions.

That credit felt more solid than the title “global contact.”

Chapter Seven: Peter Stands in the Wrong Place

Peter was invited to speak at a major youth forum on “From Student Club to Cross-Regional Technology Network.” The organizer placed his photograph on the front page and introduced him as founder and principal leader of the Third Route.

His first response was pleasure.

The venue held eight hundred people, with companies, schools, and media attending. Years before, Peter had feared remaining forever the person who constructed stages for others. Now he was finally standing at the center of a real one.

But the description was inaccurate. The Third Route had no single founder or principal leader.

Peter asked the organizer to change it.

“This is only promotional convenience,” came the reply. “Audiences need one clear protagonist.”

Peter hesitated. A correction could weaken the poster or even threaten the invitation. Leaving it unchanged would mean occupying a position that did not belong to him.

“You have always wanted to prove that you are more than unpaid support,” David wrote after seeing the screenshot. “Now that someone offers status, can you bear to correct it?”

“Do not deny your contribution,” Tommy wrote. “But do not reduce a collective achievement to one hero’s story.”

Peter proposed a new biography:

“Peter is one of the Third Route’s early co-builders. He designed community-security practices, event handovers, and youth host training. He now works in cybersecurity consulting and continues to support interschool governance.”

After three rounds of revision, the organizer agreed to “co-builder” instead of “principal leader.”

Onstage, Peter looked across eight hundred seats. Rather than beginning with his personal success, he showed a process diagram without a single person’s name.

“If you remember only me today, this talk has failed,” he said. “What we truly built was not one person’s brand but a method through which people can join, refuse, hand over, appeal, and leave.”

He discussed the anonymous letter, unanswered proposals, the private inner circle, and how Zhe had changed from an ignored proposer into a founder who nearly refused to release his project.

“A person at the center of a stage easily believes that wherever the spotlight falls must be the whole picture,” Peter concluded. “But the stage is only the part of an event most easily photographed.”

A student approached him afterward.

“Do you not want to be a real leader?”

“I do. I have simply changed what ‘real’ means. A leader does not gather everyone’s story under his own name. He makes sure that people’s roles do not exist only because the leader remembers them.”

The organizer paid a formal speaker fee and credited Peter for the presentation and recording. The Third Route cases were published under the community’s shared license.

Peter left with a contract, a result, and accurate credit.

Refusing an excessive title did not make him smaller.

Chapter Eight: The Owner of the Letter

On the review group’s final day, a student requested a confidential meeting.

Her name was An-An. She attended a small regional university and had written the anonymous letter.

“I did not intend to admit it,” she said. “But you changed the proposal process and did not publicly hunt for the writer, so I am willing to provide details.”

An-An had applied twice to host events. The first application received no response. The second was rejected for lack of experience. When she asked to join host training, an administrator said it was full. Several days later, she saw the administrator’s friends enter without a public application.

After she asked about it on Slack, someone messaged her privately: “Do not politicize small matters. Constant questioning will make everyone afraid to act.”

She feared being labeled difficult, so she wrote anonymously.

“Do you want the administrator punished?” Aoi asked.

“No. I want the next person to receive an answer without having to write an anonymous letter.”

Records confirmed that the training places had not been public. The administrator admitted preferring familiar people because they seemed more reliable.

“This was not serious malice,” David said, “but favoritism does not always appear as hostility. It often wears the form of saving time, choosing familiar people, and reducing risk.”

The administrator received process training and lost authority over host selection for one month. Training places moved to public application, and all selections required recorded reasons.

An-An’s identity remained confidential.

“Will people think the investigation was invented if we do not name her?” Yuna asked.

“We can publish the type of evidence, confirmed findings, and remedies,” Peter said. “Transparency does not mean pushing the less powerful into the spotlight to prove they were truly hurt.”

An-An later joined host training. During her first event, she forgot to introduce a speaker and managed time poorly. The feedback was not impressive.

Nobody used that failure to argue that she should never have received the opportunity.

“What will you change first next time?” Aoi asked while reviewing the recording with her.

“I will put the process on cards instead of keeping it only in my head.”

Two months later, An-An hosted again. She politely reminded an overlong speaker and clearly explained the next step when equipment failed. She did not become a star, but she was selected as an assistant for the next host-training class.

Beside a copy of her anonymous letter, she wrote:

“Once the signal has been seen, the person who sent it should not have to hide forever.”

Chapter Nine: The Fourth Signal Light

When the governance report was complete, the community discussed how to name the experience.

“The Fourth Signal Light,” Aoi proposed.

“The first light showed people they could begin. The second warned that help must not become control. The third helped different places find their own routes. The fourth should remind us that even when an organization appears normal, someone must be able to send a warning.”

“A signal light does not prove someone guilty,” David said. “It asks everyone to slow down and inspect the situation.”

“And administrators must not control the only switch,” Tommy added. “Newcomers, volunteers, partner schools, and affected people all need a safe way to send a signal.”

The Third Route created four feedback paths. General suggestions could be made publicly. Concerns involving personal data or possible retaliation could be submitted confidentially. Urgent safety incidents used a rapid-reporting channel. Anyone dissatisfied with the outcome could request review by a cross-regional panel.

Every signal had a response deadline, although it did not guarantee that the reporter would receive the desired result. The governance team had to explain what it received, what it examined, what it could confirm, and what would happen next.

David strongly opposed using the number of complaints as a simple performance measure.

“Many complaints may mean many problems, or it may mean people believe reporting is safe. Zero complaints may indicate perfect governance, or it may mean nobody dares to speak.”

“So silence cannot be treated as success,” Peter said.

Ruoqing designed the symbol: not a red alarm, but a small warm-yellow lamp protected by transparent glass. Under it were the words:

“If something seems wrong, you may pause and ask.”

Some people criticized the idea for encouraging fault-finding. Others feared that small complaints would overwhelm the governance team.

“Raising a concern does not automatically reject everyone’s work,” Aoi replied. “Accepting review does not mean admitting guilt. Mature cooperation means correcting things before they become severe.”

The first reports were mostly small: an unanswered equipment request, event photographs published without consent, and a newcomer who did not know how to leave a mailing list.

These matters were small but affected real people.

Resolving them brought no loud applause and would never become a major keynote story. Yet as each small problem found a destination, the belief that “speaking up changes nothing” slowly weakened.

An organization needed more than vision, events, branding, and results. It needed a method that still allowed someone to say, “Please wait. Something may be wrong here,” precisely when the organization felt most certain that it was doing the right thing.

Chapter Ten: The Light Is On, but Each Generation Must Steer

One year after the Fourth Signal Light was established, the Third Route held a Community Day without a keynote.

Small round tables filled the venue. Participants shared successful projects and examined failed partnerships. Each table had a facilitator who could not decide the conclusion for the group, only clarify the problem, time, and next action.

Peter, David, and Tommy did not open the event. Like everyone else, they collected name badges and chose tables.

Peter joined “How Founders Leave.”

David attended “When Numbers Mislead Governance.”

Tommy chose “Translators Must Not Decide for Others.”

“The Fourth Signal Light is not intended to make people afraid of mistakes,” Aoi said in the opening. “It allows mistakes to be addressed before they grow so large that only separation can resolve them.”

That afternoon, the reporting system received an urgent alert. The event livestream had captured participant contact details written on a whiteboard.

The team immediately paused the stream, removed the public link, preserved necessary records, notified affected people, and checked whether anyone had downloaded the clip.

Nobody first asked, “Will this make the event look like a failure?”

They asked, “Is the data still spreading? Who is affected? Who owns the next action?”

The incident was contained within twenty minutes. When the afternoon session resumed, Aoi explained publicly that the stream had briefly stopped because it showed information that should not have been public. She did not name the affected people or pretend nothing had happened.

“In the past, we might have minimized the incident to protect our reputation,” David said afterward.

“Or rushed to find one person to blame, proving the organization itself had no problem,” Peter said.

“Now, at least, we know risk handling is not a performance of innocence,” Tommy added.

At sunset, the three walked to the river. More ferries crossed it than before, following more complex routes. Small signal lights stood at intervals along the bank.

“We created all these rules, and mistakes still happen,” Peter said.

“Rules do not guarantee an absence of mistakes,” David replied. “They reduce the chance that power can hide them.”

“A light cannot steer a boat,” Tommy said. “It can only reveal the bank, the rocks, and other boats.”

Peter watched the water.

“I once wanted to become a teacher everyone knew. Later I wanted to prove that I had ability and results and deserved a budget and position. Those desires have not completely disappeared.”

“Wanting recognition is normal,” David said. “The question is whether you require everybody’s story to prove your importance.”

“A lasting contribution does not need to turn every newcomer into your student,” Tommy said.

“You two have become very good at lecturing people,” Peter replied.

“Calling me teacher requires payment,” David said.

They laughed together.

The fourth light came on beside the river.

It did not illuminate the entire night or tell every boat where to go. It left a steady yellow reflection on the water, reminding travelers that the bank was near, the river turned here, and someone was willing to stop and inspect an abnormal sign.

A reporting system could not make a community permanently fair. Administrators might still show favoritism. Founders might still resist letting go. Numbers might still miss invisible work. Connectors might still become checkpoints without realizing it.

But if signals could be sent, records inspected, power paused, and errors admitted, if people could leave safely and return by a reasonable path, the community would not need one permanently infallible person in order to survive.

Peter, David, and Tommy walked slowly along the river.

They were no longer high-school club boys or the center of every problem. A new generation had its own methods, language, and conflicts. It would even revise systems the three had once built.

That did not mean they had lost their place.

Some places were on stages. Some were written into contracts. Some lived in a procedure document rewritten by later hands. And some consisted only of checking whether the signal light was still on when another person prepared to depart.

The light was on.

But every generation still had to steer its own boat.