Chương 78: Civic Node Error

Senn's tablet screamed without making sound. That was the only way Mateo could describe it. The screen did not flash red. It did not blare an alarm. It simply displayed so many blue error boxes at once that the light became loud. Civic node candidate detected. Municipal template unavailable. Settlement template insufficient. Guild template insufficient. Camp template insufficient. Hazard assembly template insufficient. Error: category receiver missing. Darren leaned in.

"I understood maybe four of those words and resent all of them."

"It thinks Juniper is something," Horace said. Maya folded her arms.

"Amazing. We have also suspected that." The blue folder's first page still showed the question: What are you when people are already living there? It was a dangerous question because it sounded like respect and paperwork had made a baby. The room wanted to answer. Mateo could feel it in the way people leaned forward, in the way Horace's pencil hovered, in the way even the west hall went quiet around the notice lamp. Names were useful. Names were bait.

Both facts had to sit at the table and not stab each other with a fork. Sort the Pile opened.

Threat profile: category receiver missing Primary weapon: pressures community to create a receiving office so outside systems can process it Secondary weapon: treats uncategorized function as instability until a central receiver appears Known weakness: errors can identify system limits rather than community failure Available counters: error-as-evidence, no receiver clause, function inventory, already-living test, template refusal, relation map Mateo read it. Mrs. Vance pointed at the tablet.

"So the machine is confused and wants us to appoint a bucket."

"A receiving office," Varrow said.

"Bucket with a tie." Varrow paused.

"Not inaccurate." Rosa looked at him.

"Careful. Agreement may be contagious." Kade Rill's shield displayed an empty square. Above it, text appeared. Category receiver required for civic node processing. Rosa said, "No receiver." The shield immediately produced a warning. Without receiver, node may remain unofficial. Horace's face tightened. There it was again. The old hunger for a page outside Juniper that admitted Juniper existed. Nobody mocked it this time either. They had learned enough not to make dignity fight alone.

Lenora spoke gently and publicly, which was harder than either word sounded.

"Unofficial to whom?" The shield flickered. External systems.

"Does the clinic stop needing clean water if external systems dislike our vocabulary?" No. The author's narrative has been misappropriated; report any instances of this story on Amazon.

"Does the west hall stop needing warm benches?" No.

"Does dinner stop being dinner?" Maya asked. The tablet hesitated.

"It better not," Darren muttered. No. Maya nodded.

"Then the error belongs to the external system first." Horace wrote: ERROR-AS-EVIDENCE. Under it: A system's inability to process Juniper does not prove Juniper is incomplete. Senn scanned the card. Counter-standard candidate detected.

"Do not get excited," Rosa said to the tablet.

"Can tablets get excited?" Niko asked.

"This one gets condescending. Excitement is not impossible." They built the function inventory next, because every good answer seemed to begin with refusing to answer the prettier question. Kitchen fed people. Clinic tracked care and protected rest. Shelter kept bodies out of weather. Repair kept floors, pipes, rails, and doors from becoming fresh enemies. Routes connected Juniper to outside without selling the road. Child corner protected children from becoming loose labor or decorative hope.

The warning bell called attention without creating a mayor. Horace recorded without owning. Mateo stamped when the room had done enough work to make stamping safe, and sometimes not even then.

"Already-living test," Murray said. He wrote it on the back of a cereal box because Juniper's civic future apparently smelled faintly of marshmallow. Does the decision change food, care, shelter, route, safety, work, children, records, or exit for people already living here? If yes, affected seats first. If no, do not create an office to look impressive. Althea tapped the route board.

"Add outside routes. If it changes who can get here or leave here, route gets a seat."

"And dissent," said the man from west hall. Rosa looked at him. He lifted both hands.

"I am learning to be annoying responsibly." Mrs. Vance nodded.

"Public service." The folder tried again. Civic node processing still requires receiver. Mateo looked at the relation map on the folder's page. Lines crossed, looped, split, returned. They were messy because life was messy and because anyone who tried to clean them too fast usually wanted a handle.

"Receiver not found," Mateo said. The words appeared on the tablet. Receiver not found. The shield repeated them. Receiver not found. The blue folder brightened. For one breath, Mateo thought it would punish them for failing the form. Instead, it displayed a new line. Error preserved. Horace's pencil stopped.

"Preserved?" Senn read the next lines. Error identifies incompatible external processing requirement. Local function continues. Potential civic node remains uncaptured. Darren sat back.

"We broke it by letting it stay broken?"

"No," Rosa said, but she was smiling a little.

"We stopped fixing the wrong thing." That became the heart of the page. Juniper did not need to solve the external system's missing bucket by becoming bucket-shaped. It needed to preserve the error long enough for everyone to see where the pressure was coming from. The assembly formed slowly because nobody trusted it when things formed fast now.

Potential assembly: Civic Node Error Standard Materials: error-as-evidence card, no receiver clause, function inventory, already-living test, affected seats first, template refusal, relation map, dissent record Effect: protects Juniper from creating a central receiving office merely to satisfy external processing; preserves category errors as evidence of outside system limits while keeping local functions visible, reviewable, and tied to affected work Cost: 2 Focus Risk: external systems may continue treating Juniper as unofficial, delayed, or administratively inconvenient Horace read the risk.

"Administratively inconvenient," he said softly. Mrs. Vance put one hand on his shoulder and did not make it a lesson.

"They can suffer." Mateo stood carefully. Rosa watched him.

"Two Focus," he said.

"Still a cost."

"Yes."

"Do you know why you are spending it?" That was not a challenge. That was Rosa making sure the room did not confuse exhaustion with permission. Mateo looked at the relation map, the error cards, the people already standing around the decisions that affected their own work.

"Because if we create one receiver to make the error go away, everything we built today starts looking temporary." Rosa nodded once. Mateo stamped the error-as-evidence card, the no receiver clause, the function inventory, the relation map, and the already-living test. Focus pulled through him cold this time, not painful so much as clarifying. The blue light did not flood the room. It followed the lines on the map, brightening each relation without straightening it.

"Civic Node Error Standard," Mateo said.

"Juniper does not create a central receiver just because an outside system cannot process living relations. Category errors are evidence of the system's limits, not proof that people here are unfinished. Food, care, shelter, route, safety, children, work, records, dissent, and exit stay tied to affected seats. Local function continues. The error remains visible." The folder accepted the stamp. Civic Node Error Standard established. Receiver requirement blocked. External category error preserved.

Local function map stabilized. Kade's shield went blank. Then it displayed a single question. If no receiver owns the node, who speaks when the outside asks? Maya sighed.

"I hate reasonable sequels."