Vertex Macro | Ferryboat Computer Club 05: An Invitation Without a Destination

The Fifth Blank Ticket

An Invitation Without a Destination

Two years after the Fourth Signal Light was established, the Third Route received an unusual invitation to collaborate.

The sender was neither a school nor a technology company. It was a public library in a coastal city. The library planned to renovate an old ferry waiting room that had stood unused for years and turn it into a youth digital learning center. It wanted the Third Route to help establish a Community Day, LinkedIn Page, Meetup program, and Slack workspace for students, new professionals, local shopkeepers, and residents.

The invitation ended with these words:

“We have not yet decided whether the center should focus primarily on employment, entrepreneurship, technical education, or local culture. We hope you can provide a mature model.”

“This is a great opportunity,” Peter said after reading it. “We already have a complete method. We can begin with user interviews and then design the governance, activities, and safety processes.”

David stared at the final sentence.

“They are not asking us to carry out a goal. They are asking us to choose the goal for them.”

“A blank space can represent freedom,” Tommy said, “or it can mean nobody is willing to accept responsibility for making the first choice.”

Aoi was now a regional coordinator for the Third Route.

“If the library does not know where it wants to go, how can we help?” she asked.

Peter remembered all the crossings, routes, and signal lights behind them.

“Do not write a destination on the ticket yet,” he said. “First, find out who will actually board the boat.”

The four traveled to the coastal city. The old waiting room stood beside the river mouth, with rust on its roof and an ancient timetable still hanging on the wall. Through the windows, they could see a retired ferry at the shore, its white paint peeling away.

Director Lin, who led the library project, showed them around.

“The city government wants a youth innovation base. Companies want to develop talent. Schools want more extracurricular learning. Local residents are afraid it will become a place only young people and technology companies can enter.”

“Who provides the budget?” David asked.

“The city pays for renovation, two companies provide equipment, and the library operates the center.”

“Who has final authority?”

“At present, the planning committee.”

“Does that committee include future users?”

“It includes school and company representatives.”

“Does it include students, nearby residents, shopkeepers, freelancers, or people who belong to no organization?”

Director Lin did not answer.

Tommy walked to the old ticket window. Behind the glass lay a stack of yellowing blank ferry tickets with spaces for the date, fare, and destination.

“In the past, passengers had to know their destination before buying a ticket,” he said, holding one up. “This center has reversed the order. First come the building, the budget, and the managers. Only afterward does anyone ask where people want to go.”

“Then let the first Community Day become a public question day,” Peter said. “Do not present an answer. Ask different people to describe the journey they need.”

“But do not collect wishes alone,” David added. “Every wish must state its cost, the responsible party, and whom it may exclude.”

“You really are good at designing systems,” Director Lin said with a smile.

“Do not praise us yet,” Peter replied. “Wait until users can truly change the plan. Then we can decide whether this is participation.”

And so the fifth blank ticket was placed in the center of the planning table.

Chapter Two: Everyone Wants a Different Shore

More than one hundred people attended the public question day.

High-school students wanted free computers and certification study groups. University students wanted hackathons and project showcases. New engineers wanted evening technical gatherings. Local shops wanted to learn about online orders and information security. Older residents wanted help recognizing fraudulent messages.

Company representatives proposed a talent database containing participants’ skills and job interests. School representatives wanted activities reserved first for partner schools. Librarians worried that open access would make equipment and management costs uncontrollable.

Every need sounded reasonable, but the needs were not always compatible.

“Since companies provide equipment, the center should give priority to talent who can enter the industry,” one company representative said.

“Public money is renovating the building,” a nearby bookstore owner replied. “Why should residents come after corporate needs?”

“If all the activities are for residents, young people will lose a rare technical space,” a student said.

“You keep talking about youth, talent, and industry as though older people only occupy seats,” said Grandma Chen.

The room became noisy.

Peter lifted the microphone, instinctively ready to produce a vision everyone could accept. Then he stopped.

In the past, he had been skilled at finding one beautiful shared objective during conflict. It restored order quickly, but it could also bury real differences beneath a slogan.

He lowered the microphone and asked, “If your own need comes first, who might find it harder to enter?”

The room became quiet.

“If we hold hackathons every weekend,” said Yuko, a university student, “people who dislike noise or want quiet study may stop coming.”

“If we create a talent database,” the company representative said, “people who are not looking for work may feel their participation has no value.”

“If every class slows down for seniors, young people may feel they are learning too little,” Grandma Chen said.

“If small-shop courses take place during the day,” the bookstore owner said, “the people who must run their shops cannot attend.”

David wrote the answers on the wall.

“Governance is not finding one sentence that makes everyone say yes. It is admitting that resources are limited, choices have costs, and those costs cannot always be carried by people with the least voice.”

Tommy divided participants into groups and asked each one to design a weekly schedule. No single type of activity could occupy more than half the available time, and some periods had to remain unassigned.

The initial plan included weekday evening technical gatherings, weekend community digital classes, one large Community Day each month, and two weekly “blank periods.” Anyone could propose a use for those periods. An approved idea would be tested once before feedback determined whether it continued.

“Why leave blank time?” Aoi asked. “Would it not be more efficient to fill the whole schedule?”

“A full schedule means the past has already decided the entire future,” David answered. “Blank time is reserved for people we do not yet know.”

Peter looked at the destination field on the old ticket.

The value of some public spaces did not lie in carrying everyone to the same shore. It lay in refusing to cancel every other direction too early.

Chapter Three: The Conditions Attached to Free Equipment

Halfway through the renovation, a large technology company offered sixty laptops, networking equipment, and three years of cloud resources.

In exchange, the center had to be named the company’s Youth Innovation Academy. Every activity had to use the company’s account system, and its brand team would jointly manage the LinkedIn Page.

“These resources could let us open six months early,” Director Lin said.

“What information would the account system collect?” Peter asked.

“Names, schools, skills, participation, course progress, and career interests,” the company representative replied. “The data will help us provide personalized learning.”

“Can participants use the center without a company account?” David asked.

“They can choose not to participate in digital courses.”

“That is not a choice to avoid the account. It is a choice to lose access to the main service.”

“We are providing substantial resources,” the representative said coldly. “Naturally, we need to measure our impact.”

“What happens to the accounts and materials if the company stops supporting the center after three years?” Aoi asked.

“We can discuss renewal at that time.”

“So the center first hands its doors, keys, and passenger list to one company,” Tommy said, “then hopes it will be strong enough to negotiate three years later.”

“If we refuse, the city may not add funding,” Director Lin said. “We may be able to purchase only twenty laptops.”

Peter looked across the unfinished room. Once, he might have tried to preserve the largest possible equipment donation while persuading the company to soften its demands. Now he began with a different question.

“Can twenty computers deliver the most important services?”

“Yes,” the library technician replied. “With reservations, shared use, and bring-your-own-device sessions. Large events would be harder, but basic classes could operate.”

“Then an alternative exists,” David said. “It is less impressive, but it can survive.”

They proposed revisions. The center would retain a public name and use the library’s accounts. Participants could voluntarily connect to company courses. The company could receive anonymous usage statistics, but not a complete participant list. The center’s governance team would control the LinkedIn Page, while the company managed only its own branded content.

The company refused, and the sixty-laptop offer disappeared.

Some people accused the governance team of being too idealistic.

“The equipment would genuinely help students, but you rejected it for an abstract idea of autonomy.”

“Autonomy is not abstract,” Grandma Chen said at a public meeting. “If I must give a company all my information before learning how to avoid fraud, then I am not a learner. I am a source of data.”

The city eventually added some funding. Local shops donated eight devices, and several schools supplied refurbished computers. The center opened with only thirty-four laptops.

The number was modest, but none required users to accept an unrelated long-term commercial relationship before learning.

“Sometimes the most important budget is not how much you obtain,” David told Peter. “It is whether you keep the ability to refuse the next one.”

Chapter Four: Aoi’s First Contract

The center needed a youth-community coordinator to manage Meetups, volunteers, the LinkedIn Page, and interschool contact. Director Lin invited Aoi to apply.

It was her first chance to turn years of community experience into formal employment.

The contract lasted six months for twenty hours each week. The pay was only slightly higher than ordinary administrative student work. Its final duty read, “Complete other temporary tasks according to the center’s development needs.”

“I really want this job,” Aoi said, showing the contract to Peter, David, and Tommy. “But if I ask for too much, will the library hire someone else?”

“Do not begin by asking whether they will reject you,” Peter said. “Ask whether you understand what you are promising.”

David estimated the work: six hours for event management, four for content and social media, five for volunteer communication, four for interschool cooperation, and three for administration. The total already exceeded twenty hours before evening events and temporary tasks.

“This contract places a full-time expectation inside part-time hours.”

“But I have no formal work experience,” Aoi said.

“That does not make your past disappear,” Tommy replied. “You have hosted events, handled complaints, transferred accounts, and designed cross-regional processes. Translate community experience into work results.”

Aoi assembled a portfolio covering the proposal-response system, host training, signal reporting, and interschool activity data. She requested several changes: within twenty hours, she would own only two major areas; other work would go to other staff; evening and weekend work would receive time off in lieu; temporary tasks had to relate to her role and remain within a monthly hours limit; and pay and scope would be reviewed after three months.

“You are limiting the job before you have even started?” Director Lin asked.

“I am making sure I can deliver what I promise. If every gap can become a temporary task, nobody will know what I am actually responsible for.”

After two rounds of negotiation, Aoi took responsibility for event operations and youth governance. The library’s communications team kept social media. Her base pay changed little, but the contract added evening allowances and a three-month review.

“Is this a good contract?” she asked David after signing.

“It has clearer boundaries than the original. Whether it is good depends on how both sides perform it.”

“You do not need to prove you deserve your first formal role through unlimited compliance,” Peter said.

“And negotiating conditions does not mean you are ungrateful,” Tommy added. “Gratitude and self-protection can exist together.”

Aoi placed the contract in a folder. It was not a ticket guaranteeing success, but it clearly stated the journey, schedule, and responsibilities of both parties.

Chapter Five: The Person Who Left Slack

After the youth digital learning center opened, its Slack community quickly passed eight hundred members.

The number of channels and messages grew. Some people posted articles every day. Others repeatedly notified everyone. Event discussions turned into career debates. Newcomers did not know where to look and were afraid to ask questions among hundreds of unread messages.

Before leaving, a student named Jiahao wrote:

“This place says newcomers are welcome, but everyone seems to have known each other for years. Whenever I ask something, people send old links and tell me to read them. Nobody blocked me. I simply kept feeling that I should not be here.”

“We broke no rule, and nobody attacked him,” an administrator said.

“Not being attacked does not mean a person can participate,” Aoi replied.

She asked Jiahao whether he would explain his experience.

“I joined to learn basic networking,” he said. “People in the channels kept discussing advanced tools. They said beginner questions had already been answered and told me to search. I searched, but I could not tell which answer matched the current version.”

Peter inspected the onboarding process. The welcome message contained more than twenty links but did not say what a newcomer could do during the first week.

“It is like handing the entire library catalog to a first-time visitor and saying all the resources are there.”

Tommy recommended a First Stop channel with rotating guides who answered basic questions. Old resources would display update dates, and outdated materials would move to an archive. Large channels would restrict notify-everyone functions. Important decisions would receive summaries so members did not have to read entire chat histories.

“We keep treating joins and activity as results,” David said. “What about the people who leave?”

They added optional exit feedback but did not force anyone to explain or treat departure as failure. Members could mute notifications, leave individual channels, or delete their data entirely.

“If leaving becomes too easy, retention will look bad,” one administrator warned.

“Locking the door would improve retention,” Aoi said. “That would not make the community successful.”

Jiahao did not return immediately. Two months later, he attended a small networking lab at the library and joined the First Stop channel with a new account.

Instead of sending a pile of links, the guide asked, “What do you want to accomplish now?”

“I want two computers on the same small network to find each other.”

The guide gave him a twenty-minute exercise.

When the computers successfully responded to one another, Jiahao posted a screenshot. There was no great applause, only several replies: “It worked. Come back for the next step.”

Chapter Six: Peter’s Security Lockdown

One Friday evening, the center’s LinkedIn Page suddenly published a strange announcement claiming it would offer a paid certification course with an unfamiliar company.

Aoi confirmed that nobody had approved the post. Peter suspected an account compromise.

He remotely disabled every editor, reset passwords, removed the post, and required all administrators to verify their identities again.

The response was fast. The post remained public for only twelve minutes.

The next morning, however, Ruoqing’s account was still suspended, and nobody had told her when it would return. Other editors could not publish scheduled event notices either.

“Peter has once again turned an emergency security action into an indefinite lockout,” David said.

“If I had moved more slowly, the attacker might have published more fraudulent content,” Peter replied.

“The emergency suspension was correct. The failure was that nobody owned recovery after the emergency.”

Aoi examined the incident record. Peter had documented detection time, actions, and preliminary impact, but had named no recovery owner or expected restoration time.

Peter fell silent.

His security work had taught him blocking, isolation, and investigation. Yet he had repeated an old mistake from managing Slack. Stopping the threat was only the first half. Returning legitimate users safely was part of the incident too.

The investigation found that a former editor’s old account still had access and used a password exposed on another site. The attacker had used it to publish the announcement.

Peter revised the process. Every emergency shutdown had to create a recovery checklist at the same time, naming affected roles, review deadlines, and restoration conditions. The incident commander could not independently decide everyone’s long-term access. Departing staff accounts had to be removed on the handover date and reviewed quarterly.

“My emergency judgment was necessary last night, but my process was incomplete,” he told the post-incident meeting. “Security is not only whether we stop the wrong person. It is also how long legitimate people remain interrupted.”

“Are you not afraid that admitting this publicly will make people distrust your expertise?” Ruoqing asked.

“If my expertise depends on pretending every decision is perfect, it does not deserve trust.”

“Risk management is not proving that you are always right,” David said. “It allows errors to survive without concealment.”

Access returned in stages after verification, and scheduled notices were republished. The report did not describe Peter as a lone hero, nor did it hide the incomplete recovery process.

Security protected more than accounts. It protected a person’s ability to return to a legitimate place.

Chapter Seven: David’s Losing Forecast

After six months, the library had to decide the next annual budget. David built a demand forecast from Meetup registration, Slack activity, equipment reservations, and course completion.

The model predicted that advanced cloud workshops would produce the strongest participation and corporate cooperation. Anti-fraud classes and digital courses for small shops appeared to grow more slowly.

According to the model, advanced technical activities deserved more money, while basic community programs should shrink.

“We must place limited resources where results are strongest,” Director Lin said.

“Whose results?” Grandma Chen asked.

David explained that the model counted registrations, completion, return visits, and external partnerships.

“How many points does an older person receive for learning not to give a verification code to a stranger?”

“The model does not count that separately.”

“How many points for a shop that stops putting customer information in a public spreadsheet?” the bookstore owner asked.

The model had no answer.

Peter inspected the sources. Advanced-workshop participants already used Meetup and Slack, leaving abundant visible data. Community-course participants often registered in person and did not interact online afterward. The model had not discovered that one group was more valuable. It had discovered that one group was easier to see.

“I let data availability determine value again,” David said.

This time he did not immediately rebuild the model. He sat through an anti-fraud class.

He watched Grandma Chen teach another older resident to inspect a web address. He watched a shopkeeper replace a shared simple password with separate passwords. These changes would not produce hundreds of LinkedIn views, but they could prevent real losses.

The new budget assessment used three separate perspectives. Growth value measured participation, cooperation, and continuity. Public value measured safety, accessibility, and service to overlooked groups. Capability value measured whether participants gained reusable skills.

The categories were not forced into one total score, so high traffic could not automatically overwhelm public responsibility.

“How can I decide quickly without one ranking?” Director Lin asked.

“You cannot surrender every political and value judgment to a model,” David answered. “It can show the costs of a choice. It cannot pretend no choice exists.”

Advanced workshops received a partial increase, while anti-fraud and small-shop courses retained protected funding. The center also improved its recording of in-person results without requiring older residents to join a social platform to prove their value.

David kept the original forecast in the appendix under the title: “A Model That Correctly Calculated the Wrong Question.”

Chapter Eight: Tommy Does Not Bring an International Speaker

Before the center’s first anniversary, Director Lin wanted an overseas speaker for Community Day.

“An international guest will attract media attention and demonstrate global connections.”

Everyone looked toward Tommy.

“This time, I will not bring a speaker,” he said.

“Is international connection not your specialty?” Director Lin asked.

“That is why I know that flying someone in to speak for twenty minutes does not necessarily create cooperation.”

Instead, Tommy asked center participants to identify three real problems and work with overseas communities for six weeks. Community Day would not feature a one-time speech. It would show what the teams had completed together and what remained unresolved.

One group wanted online materials that worked with limited bandwidth. A group of shopkeepers wanted a simple data-protection checklist. Older learners wanted understandable anti-fraud cards.

Tommy did not give every opportunity to his own contacts. He published an open invitation defining the schedule, task, languages, and licensing. Three teams from different regions joined.

The six weeks were difficult. Time zones produced late meetings. The same words carried different meanings. One overseas team withdrew halfway through.

“If we had invited a famous speaker, at least the result would have been controllable,” Director Lin said.

“Controlling a stage does not mean building a relationship,” Tommy replied.

There was no grand international keynote on Community Day. The teams showed tests, misunderstandings, failures, and revisions. The low-bandwidth group openly admitted that its first version could not load at all in the overseas school.

“Does this count as an international result?” a reporter asked.

“The second version opens on a very slow connection, and neither side created it alone,” a student replied. “That feels more like a result than a photograph with an international speaker.”

Tommy stood in the audience without being introduced as a global contact.

The LinkedIn Page later published shared files, test conditions, unfinished problems, and the next-round owners instead of three photographs of handshakes.

Real international cooperation did not carry distant people onto one’s own stage. It allowed one’s method to fail somewhere else and change because of it.

Chapter Nine: The Names on the Tickets

After one year, the city began preparing a publication about the center’s results.

The draft cover named the library, city government, two companies, and the Third Route. Inside were interviews with Peter, Director Lin, and several executives.

“Where are the volunteers, course designers, equipment maintainers, and participants?” Aoi asked after reading it.

“There are too many names,” the editor replied. “We can present only the principal figures.”

“Principal according to title, public visibility, or actual contribution?” David asked.

The editor had no clear answer.

Peter’s interview occupied four pages. He had designed safety processes and helped manage an account incident, but he had visited only several times. Aoi, librarians, and volunteers carried the daily operation.

Years earlier, he might have seen the four pages as overdue recognition. Now he asked the editor to shorten them.

“You are an important character in the series,” the editor said. “Readers need a protagonist.”

“The center is not my series.”

The publication was redesigned. Institutions remained on the cover, but a new section asked, “Who Made This Happen?” Every project listed initiation, delivery, maintenance, and handover roles. People who did not want public names could appear under team names.

Contributions were ordered by work, not titles.

The book recorded Zhe’s old-equipment method, Jiahao’s onboarding feedback, Grandma Chen’s anti-fraud teaching, Aoi’s contracted youth-governance role, Ruoqing’s accessibility design, and the library technician’s equipment maintenance.

Not every small act could fit. The center therefore created a public contribution register that participants could verify and correct. It was not a competition and did not rank people by how often they appeared.

“Will the book be less attractive without a hero story?” Director Lin asked.

“Personal stories are valuable,” Tommy said, “but one person’s story must not swallow the evidence of everybody else.”

The publication’s most shared page was not an executive interview. It contained sentences in different handwriting:

“I repaired my first router.”

“I did not run away during my first hosting session.”

“I learned to refuse disclosure of data that was not needed.”

“I left Slack and returned in a way that worked for me.”

“I never stood onstage, but after the event every device returned to the correct place.”

Each sentence resembled a ticket with a person’s name on it.

It did not prove who owned the boat. It proved that the person truly had a place on the journey.

Chapter Ten: Blank Does Not Mean Empty

On the youth digital learning center’s second anniversary, a timetable returned to the wall outside the old waiting room.

It did not list fixed destinations. It listed the month’s activities: networking basics, anti-fraud lessons for older residents, data organization for shops, student project night, quiet study, old-device repair, and two blank periods whose use had not yet been decided.

The fifth blank ticket was mounted in a glass frame beside the entrance. Its destination field remained empty.

“Why not write a destination?” a new high-school student asked Aoi.

“Because this place does not send everybody to the same location. Some people come for job skills, some to solve daily problems, and some to find people with whom they can learn.”

“Does the center have no shared goal?”

“It does. The shared goal is not deciding everyone’s destination. It is giving different people a fair, safe, and understandable way to begin.”

That afternoon, Peter, David, and Tommy returned for the anniversary Meetup.

Peter reviewed the latest security handover and found that younger administrators had simplified his old process. David read the budget report and saw that public value was no longer buried beneath traffic numbers. Tommy discovered that several overseas teams could cooperate directly without his introductions.

Their names remained in the contribution register, but nobody called the center their creation.

“In the past, I might have felt a little disappointed,” Peter said beside the river.

“And now?” David asked.

“I still do. Understanding an idea does not completely remove the desire to be remembered.”

“There is nothing shameful about wanting to be remembered,” Tommy said. “You simply cannot turn everyone who comes later into a supporting character in your own story.”

“A cynic would say a ticket has no destination because nobody wants responsibility for results,” David said, looking at the framed ticket.

“What do you say now?” Peter asked.

“Sometimes that is true. A blank space therefore needs boundaries. Who may propose, who owns the trial, when it is reviewed, and how it ends after failure must be clear. Blankness without process is avoidance. Blankness with process is room for choice.”

“Confucian thought reminds us that the space ultimately exists for people,” Tommy said. “Legalist thought reminds us that we cannot depend on everyone being good automatically. The people using the ticket should help decide which shore it reaches.”

Sunset turned the waiting-room windows gold. Inside, some people attended classes, some organized equipment, some read quietly, and others used a blank period to discuss a project that did not yet have a name.

Nobody stood at the door claiming to represent everyone.

And nobody pretended that public ownership made resources costless, rules powerless, or choices free of consequences.

The blank ticket was not a promise of free success. It could not guarantee that everyone would succeed or that every proposal would be accepted. It promised several smaller, more dependable things.

The door would not open only for familiar people.

A rejection would include a reason.

A contribution would not disappear because it happened away from the stage.

An emergency lockout would have a road to restoration.

Data would not be taken merely because a resource was free.

A person who left would not be called a traitor.

A person who returned would not have to pretend never to have left.

Peter, David, and Tommy walked along the river toward the station. Behind them, the center’s evening lights came on, and the blank ticket cast a faint reflection inside its glass frame.

“Do you think there will be a sixth story?” Peter asked.

“First see whether a new problem appears,” David replied.

“First see whether someone needs a new road,” Tommy said.

Peter smiled.

“Then let us leave the name blank for now.”

A late ferry left the pier. Every passenger held a ticket with a different destination. Only the fifth ticket in the glass frame remained blank.

Blank did not mean empty.

It was a future that had not yet been filled in advance by a small number of people.