Vertex Macro | Ferryboat Computer Club 10: An Extra Line on the Wall

The Tenth Tide-Mark Map

An Extra Line on the Wall

After the ninth spare key passed its annual inspection, the Coastal Youth Digital Learning Center enjoyed another peaceful winter.

Before the spring term began, Jiahao and several students repainted the first-floor corridor. When they moved an old bookshelf, a curved dark water mark appeared on the wall. It rose from the floor to about an adult's knee, leaving a shoreline-like outline across the white surface.

"Was this left by an old flood?" Yawen asked.

The library technician nodded.

"More than ten years ago, a severe rainstorm forced river water back into the old ferry waiting room. The wall was repainted afterward, so nobody could see the mark anymore."

Jiahao picked up the paint roller.

"Then let us cover it."

Su Qing stopped him.

"Wait. This line may be relevant to our current disaster-preparedness design."

Peter inspected the center's emergency documents. The folder contained procedures for fire, power failure, account incidents, and personal-data breaches, but no complete flood-response plan. The most recent evacuation exercise had assumed that everyone could leave through the main entrance. It did not consider that river water might block the lower exits.

David studied the tide mark.

"Repainting a risk does not make it disappear. It merely removes the risk from everyone's view."

"Who first noticed the flooding?" Tommy asked the technician.

"Boat operators nearby. They saw that the water level was wrong and ran over to warn people."

"Was anything recorded?"

"Only a few old photographs remain."

Aoi found the photographs. They showed sandbags piled outside the waiting room, nearby shopkeepers moving documents on handcarts, and several high-school students carrying chairs to higher ground. There was no date on the back and none of the people were named.

At the same time, the city government was preparing a new riverfront tourism program. It wanted the center to create a large digital wall map introducing the ferries, youth activities, and international partnerships. The design company had planned to cover the old water mark completely and replace it with a beautiful blue river.

"Will the map look old if we preserve the tide mark?" Aoi asked.

"Old is not the problem," Ruoqing replied. "The question is whether we treat it as a stain, a piece of history, or a warning."

"It can be all three," Peter said. "It is a mark from the past and a risk we need to examine again today."

The center paused the painting and labeled the line "Unverified Historical Water Level." The team did not rush to turn it into a memorial, nor did it use one photograph to conclude that a future flood would certainly reach the same height.

Jiahao wrote in the work log:

"The line did not appear because the risk began today. It appeared because today we moved the bookshelf."

The tide mark became the starting point of the tenth story.

The first nine stories had asked who could open doors, send warnings, hold keys, and preserve records.

The tenth question was different: when the environment itself was changing, could an old map still tell people where to go next?

Chapter Two: The Blank Area on a Beautiful Map

The design company presented the first version of the riverfront digital map.

It was beautiful. A blue river crossed the city, and the center was marked by a glowing icon. Beside it ran a timeline of Community Days, Meetups, LinkedIn Page milestones, and interschool partnerships. Users could select different locations to see event photographs and results data.

"This map will show visitors the youth innovation of the coastal city," the city representative said approvingly.

Grandma Chen studied it for several minutes.

"Where is the old market where we live?"

The designer enlarged the map.

The old market appeared as an unmarked gray area.

"There are no major youth activities there, and it is not a tourism destination."

"Many people in the anti-fraud classes live there," Grandma Chen replied. "It is also one of the first places to collect water during heavy rain."

"Where are the accessible entrance, the Quiet Collaboration Room, and the bus stops?" Yawen asked.

They were missing as well.

Corporate booths, famous speakers, and the main stage had prominent icons. Equipment-repair points, community classes, and flood-prone roads had vanished.

"The map is not lying," David said. "It enlarges what its makers chose to present and turns everything else into something that appears not to exist."

"Every map requires choices," the designer replied unhappily. "It cannot contain everything."

"Of course," Ruoqing said. "That is why we must explain for whom those choices were made. A tourism map, an activity map, an accessibility map, and a disaster map should not pretend to be one complete map."

The city wanted one simple entrance so users would not find the design too complicated.

Jiahao proposed layers. The main screen would retain a simple riverfront view, but users could switch between activities, learning, transportation, accessibility, and risk. Every layer would show its update date, data source, and responsible team.

"Residents should be able to report omissions," Aoi said. "But a report must not become a public fact immediately. Someone has to verify it."

"Security-sensitive locations must not reveal too much detail," Peter added. "Emergency key boxes, equipment rooms, and backup systems should show only general guidance, not precise access information."

After the redesign, the old market was no longer a blank gray space. It appeared on the community-learning and flood-observation layers. Bus stops, ramp entrances, quiet spaces, and equipment-support points received their own markers.

The map was more complicated than the original.

"Will visitors from outside the city still want to use it?" the city representative asked.

"Nobody needs to view every layer," Tommy said. "True simplicity does not delete other people's needs. It helps each person find the layer relevant to them."

Chapter Three: The Red Zones Peter Drew

To prepare for flooding, Peter used building elevations, drain locations, and old photographs to mark several red zones on the floor plan.

Red meant a location might become unsafe during extreme rainfall. The equipment room, old entrance, and some electrical systems fell inside the marked areas.

Peter recommended moving important servers, paper records, and emergency supplies to the second floor. He also wanted portions of the first floor to close in advance whenever a severe-rain warning appeared.

"What level of warning triggers closure?" Su Qing asked.

"As soon as the weather service issues a warning at the specified level."

"How many days met that condition during the past five years?" David asked.

"Seventeen."

"On how many did backflow become an actual risk?"

"Two."

"If we close every time, regular classes may be canceled several times a year," Aoi said. "Shift workers will again be affected first."

"Safety cannot wait until water enters the building," Peter replied irritably.

"Nobody is asking you to wait for the water," David said. "We are asking whether a red zone is a warning, a forecast, or an automatic command."

Peter remembered his earlier emergency lockouts. He could identify worst-case outcomes quickly, but sometimes turned risk prevention directly into a complete shutdown.

The technician proposed staged measures. Level One would strengthen monitoring and confirm drains and backup personnel. Level Two would move low-lying equipment and suspend basement storage access and evening activities. Only Level Three would close the first floor completely and begin evacuation.

Triggers would consider not only weather warnings but also live water levels, drainage conditions, and observations on site. Every early closure had to include an alternative arrangement and the time of the next update.

"I do not object to a canceled class," Grandma Chen said. "I object to receiving one cancellation notice in the morning and hearing nothing else all day."

Peter revised the plan.

"Red will no longer mean immediate closure. It means we must enter the next decision process."

David nodded.

"A color is a signal, not a verdict. You have finally applied your own lesson to yourself."

Chapter Four: The Shop That Did Not Want Its Location Published

After residents were allowed to submit information to the riverfront map, nearby businesses began marking places where people could charge devices, obtain drinking water, shelter from rain, or receive temporary assistance.

One old coffee shop refused to participate.

Aoi visited the owner, Uncle Zhou.

"During typhoons, we have let residents rest here and use our electrical outlets," he said. "But if the map labels us as a shelter, everyone may come next time. We cannot support that."

"We could mark the shop as a voluntary assistance point and include your capacity and operating conditions."

"Who can guarantee people will read the conditions? Someone will take a screenshot that says this is a shelter."

"Then do not publish the exact location," Tommy said. "We can place you on the center's private contact list and ask whether you are able to help only during an official coordination effort."

The city representative believed more public information was always better.

"Residents need to know where resources are located."

"Visibility creates use, and use creates responsibility," David replied. "We cannot automatically transform a small shop's past kindness into a permanent public duty."

They designed three statuses. Official public support points displayed their locations and services. Conditional partners displayed only an area and a contact mechanism. Private backups did not appear publicly and were contacted individually by the coordination team when needed.

Uncle Zhou chose conditional partnership. If the shop was safe, enough staff were present, and the road remained accessible, it would offer charging and temporary rest for no more than ten people.

"And if I say no that day?"

"Then the answer is no," Aoi said. "Joining a partnership does not remove your right to refuse each individual request."

David added a sentence to the map-governance document:

"One act of goodwill does not create permanent authorization, and one public listing does not promise unlimited supply."

Chapter Five: The Route Jiahao Updated Incorrectly

One weekend, a resident reported that construction had closed the riverfront bicycle path used to reach the center.

After inspecting a photograph, Jiahao immediately updated the map with an alternative route and posted notices on Slack and Meetup.

Two hours later, a participant who used a wheelchair replied:

"Your new route has stairs."

Jiahao froze.

He had confirmed only that the alternative route could be walked. He had not checked its slope or accessibility.

Worse, several schools had already shared the notice.

"I will delete it immediately," Jiahao said.

"Correct it first. Do not merely delete it," Peter replied. "People who saw the old information need to know what was wrong."

Ruoqing and Jiahao returned to inspect the area. They found a longer route with ramps and confirmed that a low section might collect water during rain.

The new notice identified three options: an ordinary walking route, an accessible route, and a section not recommended during rain. The original notice received a prominent correction and timestamp. Nobody pretended it had never been published.

"I thought updating faster meant being more responsible," Jiahao said at the meeting.

"Speed matters," David replied, "but route information must ask not only whether someone can pass, but who can pass and under what conditions."

Aoi introduced a two-person review. One person could update ordinary event information. Transportation, safety, and accessible routes required a second reviewer. During an emergency, tentative information could be published first, but it had to be labeled as not fully verified and include the time of the next update.

"Will adding a review make us too slow?" Jiahao asked.

"Not all information requires the same speed," Peter answered. "A mature process knows what may move quickly and what, if wrong once, could send someone toward a road they cannot use."

Chapter Six: David's Evacuation Forecast

The city asked the center to estimate how many people might need evacuation assistance during extreme weather so that vehicles and temporary spaces could be arranged.

David built a model using event registrations, ordinary entries, age distribution, accessibility needs, and transportation methods. It predicted that no more than three minibuses would be needed.

"What about people who did not register in advance?" Su Qing asked.

"We can include a margin of error."

"What about someone who registered as not needing assistance but becomes frightened during severe rain?" Grandma Chen asked.

"That is difficult to infer from the current data."

"And if nearby residents run into the center unexpectedly," Uncle Zhou asked, "do they count as center users?"

The model had no answer.

David ran a tabletop exercise and discovered that the bottleneck was not only the number of people. Some needed more time to board, some could not be separated from equipment, some could not understand the public announcements, and some might refuse to leave while waiting for friends.

He replaced the single precise figure with three scenarios and resource ranges. The minimum scenario covered a small holiday activity. The middle scenario covered a normal Community Day. The maximum included nearby residents entering unexpectedly and one vehicle being unavailable.

The center also stopped maintaining a fixed list of people who needed help. Each event would confirm needs on the day so outdated data would not create false assumptions.

"We need one number for procurement," the city representative complained.

"Use the highest reasonable scenario as the baseline, then add shared buses and a mechanism for temporary reinforcement," David replied. "A single number looks certain, but it makes people forget the assumptions underneath it."

The city arranged three dedicated minibuses, one cross-regional backup vehicle, and agreements with nearby schools for temporary space.

David wrote on the model's opening page:

"A forecast is not a list of the future. It is a set of assumptions that must remain under review."

Chapter Seven: Tommy Hears Different Typhoons

The center held a disaster-preparedness exchange with overseas communities. Students from different regions all used words such as "typhoon," "flood," and "evacuation," but their lived experiences were entirely different.

Some lived in high-rise cities and worried about power failures and lost internet service. Some came from islands where suspended ferries meant supplies could not arrive. Others lived in mountain regions where the greatest danger was not flooding but road closures.

"Our standard process is to close every activity twenty-four hours in advance," an overseas speaker said.

The city representative thought the center could adopt the same rule directly.

"Are their transportation systems, buildings, and warning systems the same as ours?" Tommy asked.

"The principle should be transferable."

"Principles can be shared. Trigger conditions cannot simply be copied."

He changed the exchange from a presentation of best practices into a comparison of scenarios. Every community had to describe its geography, available resources, warning sources, most vulnerable groups, and examples of process failure.

They soon learned that the same action could produce opposite consequences in different places. Early total closure was merely inconvenient in a city with many transportation options, but on an island with one ferry it could make people miss their final chance to obtain supplies. Slack alerts worked well in some areas, while regions with unstable internet needed radio and paper contact trees.

"A method is not automatically superior merely because it comes from an international community," Peter said.

"And local experience is not exempt from examination merely because it is local," David added.

Tommy named the shared document "Principles Can Be Translated; Answers Cannot Be Copied."

It retained only several common baselines: information sources had to be clear, responsibilities traceable, vulnerable needs considered early, emergency powers time-limited, and recovery designed at the same time as shutdown.

Each region would set its own warning times, evacuation methods, and communication tools according to local conditions.

Chapter Eight: Aoi Rejects the Hero Wall

As the digital map neared completion, the city proposed adding a "Riverfront Heroes Wall" honoring the ten greatest contributors over the years.

The candidate list included Peter, David, Tommy, Aoi, Director Lin, Su Qing, and several corporate executives.

"Stories need people if citizens are going to remember them," the city representative said.

"What about the cleaners, equipment technicians, community guides, and the student who first pointed out that the clock lost three minutes every day?" Aoi asked.

"There are only ten places. We can rotate the names later."

Peter looked at his own name. He no longer desired to appear on every wall as he once had, but he did not want to pretend public recognition had no value.

"Tell personal stories if you wish," he said, "but do not call it a hero wall. The word hero makes people believe a system is rescued by a few exceptional individuals."

Ruoqing proposed a different design. The wall became the Tide-Mark Contribution Map, displaying many roles around specific events. Every story included identifying the problem, designing the method, carrying out the work, maintaining it, and handing it over. It did not show only a photograph of the person who stood onstage.

The first story covered the tide clock repair. It named the student who first raised the issue, the vocational team that made the gear, the technician who provided historical information, and the people who later performed annual calibration.

The second story covered flood preparation. Alongside the governance team, it identified nearby boat operators, shopkeepers, residents, and the people who cleaned the old records.

"People may be remembered," David said, "but remembering one person must not mean forgetting the evidence of collective work."

The city accepted the new name. The ranking of ten people was canceled and replaced by a contribution map that could continue to grow and be corrected.

Director Lin found her name under both "Early Responsibility" and "Transfer of Authority."

"That is more truthful than displaying a retirement photograph," she said with a smile.

Chapter Nine: The Tenth Tide-Mark Map

On the day the new riverfront map was released, the center preserved the old tide mark on the wall.

Ruoqing did not cover it completely in blue. She installed a narrow transparent strip of light along the mark. Ordinarily, it emitted only a faint glow. When the live water level rose, verified data changed its brightness.

A notice beside it said:

"This line came from a past flood. It is not a guarantee of a future water level. Check the latest warnings, building guidance, and on-site notices as well."

The map contained ten main layers.

Activities and courses.

Transportation and accessibility.

Community support.

Flood observations.

Emergency assembly.

Equipment and maintenance.

Historical decisions.

Public contributions.

Updates and corrections.

Not yet verified.

The final layer was the most unusual. It did not display answers. It displayed gaps in knowledge: a road not yet tested during rain, a support point undergoing reconfirmation, or a historical record with an unknown date.

"Will publishing what we do not know make the map look unreliable?" Jiahao asked.

"Pretending there are no unknowns would make it most unreliable," David replied. "Reliability does not mean every square contains an answer. It means distinguishing clearly between confirmed information, inference, and uncertainty."

Peter inspected the safety information to ensure that public content did not expose sensitive equipment. Tommy asked overseas partners to test the different language versions so the same warning would not become excessively severe or dangerously mild in translation.

Aoi assigned update responsibility. Each layer had a responsible team and review date. No one person controlled the entire map. If a primary source failed, the map would display the time of its last update rather than continue presenting old information as current.

"This does not resemble an ordinary results map," the city representative said while standing before the wall. "It contains many limitations and unknowns."

"Because it is not an advertising poster," Su Qing replied. "It is something people must actually use to find their way."

Chapter Ten: A Map Cannot Look at the Sea for You

Six months after the Tenth Tide-Mark Map was released, a severe rainstorm approached the coastal city.

The center entered Level One preparation. The team checked drainage, moved equipment from low areas, updated course notices, and contacted conditional partners. Uncle Zhou replied that the coffee shop lacked enough staff that day and could not provide support. The system did not blame him. It simply changed the location's status to temporarily unavailable.

That afternoon, the water level rose and the center entered Level Two. Some evening activities moved online, and the first floor stopped accepting new large groups. The transparent strip on the map grew brighter, but conditions had not yet reached full evacuation.

A resident reported that part of the accessible alternative route was flooded. Jiahao first marked the report as awaiting verification and sent a nearby coordinator to inspect it. Once confirmed, the map was corrected immediately and offered another, longer route.

David's maximum scenario did not occur completely, but several nearby residents entered the center unexpectedly. The day's needs check showed that one required more time to move and another had to keep medical equipment nearby.

In the evening, a drain became temporarily blocked, and water crossed the lowest step outside the entrance.

Peter ordered Level Three. The team closed the first floor, guided everyone to the second-floor assembly area, and transported people out in groups. The emergency key box was opened once. Two administrators jointly removed the equipment-room spare key and shut down the low-lying electrical supply. An access record was created immediately, and a recovery owner was assigned at the same time.

The operation was not perfect.

One minibus arrived ten minutes late. Part of the public announcement was difficult to hear. Two students went to the wrong assembly zone. But nobody hid the situation because of those errors, and nobody replaced the next step with the empty phrase "Please cooperate."

The rain weakened late that night. The center suffered no serious loss.

The following morning, the tide-mark light returned to its faint glow. The new water had not reached the old mark from more than ten years earlier, but it had left several small spots of mud on another wall.

The city prepared a news release praising the center for having "successfully predicted and responded perfectly."

Aoi requested a correction.

"We did not predict perfectly. The map supplied information, residents submitted reports, staff made decisions, and backup processes covered several failures."

"If we say the model was accurate," David added, "people may trust the same map too much next time."

"And if we write it as a heroic rescue," Peter said, "people will overlook the drills, equipment, and handovers."

The final report listed both successful measures and problems. The accessible-route update had been too slow. The public-address system needed improvement. Backup minibuses took too long to arrive. Some new volunteers did not know the second assembly zone.

When Tommy shared the experience at an international meeting, he did not call the process a best practice.

"This was a version that worked temporarily in one city, one building, and one team. Take the questions and principles. Do not copy the answers directly."

At the first Community Day after the storm, everyone gathered before the tide-mark map.

"Now that we have this map, does it mean we no longer need to fear flooding?" a newcomer asked.

"We will still be afraid," Su Qing replied. "The map does not remove fear. It prevents fear from having no form except confusion."

"And the map cannot look through the window for you," Grandma Chen added. "If the warning says it is safe but water is entering the doorway, you still need to speak."

Jiahao added the new problems discovered during the storm to the Not Yet Verified layer. He did not wait for every improvement to be complete before admitting that gaps remained.

At sunset, Peter, David, Tommy, and Aoi stood beside the river. Ferry service had resumed, and crews adjusted their routes according to the latest water level.

"We began with a high-school computer club," Peter said, "and eventually even a water stain on a wall became a governance problem."

"Anything that affects who may enter, who must leave, or who carries the risk is already a governance problem," David replied.

"But governance cannot mean handing everything to a form," Tommy said. "Someone still has to walk to the river and listen when the boat operators say the wind has changed."

Aoi looked toward the center's entrance. The signal light, blank ticket, tide clock, handover log, unsent letter, spare key, and tide-mark map rested quietly in different places.

Not one of them was power itself.

Real power remained in the ways people interpreted, used, updated, and refused them.

A map may draw roads clearly, but it cannot decide where it is worth going.

It may mark danger, but it cannot guarantee that unmarked places will always be safe.

It may preserve history, but it cannot order the future to follow the same route.

The most dependable map is not one that claims to see everything. It is one that tells users what is confirmed, what remains unclear, and where they must stop and ask someone.

The late ferry sounded its horn and left the shore.

The navigation screen showed the channel. The tide clock on shore showed the time. Signal lights marked the turn. The crew looked up at the real water.

Nobody departed using only one map.

And nobody decided to remain forever on shore merely because the map was imperfect.

The Tenth Tide-Mark Map glowed faintly on the center's wall. The old water line had not been erased, and the new mud spots had not been turned into trophies of success.

They remained there honestly, reminding every person preparing to depart:

The past once reached this place.

The water level is changing now.

The next route still has to be confirmed together.