Chapter 200: The Man Who Owned the Backup

Silas Veyr’s office occupied the upper floor of a building that had once belonged to a shipping company.

The old owners had covered its walls with maps, route schedules, and photographs of merchant vessels. Silas had kept the maps.

Everything else had been replaced.

The furniture was expensive without being decorative. The windows overlooked the northern commercial district, where carts moved between warehouses and merchants argued over delivery schedules. A large clock hung behind the desk.

Aria disliked it immediately.

Not because it was impressive.

Because it was positioned where every visitor could see it.

A reminder that their time belonged to someone.

Kelme noticed it too.

"Subtle," he whispered.

"Don’t start."

"I wasn’t going to."

"You were."

He smiled.

Across the desk, Silas Veyr stood to greet them.

"Aria. Lucan. And Kelme, I believe."

Kelme nodded.

"Charming Merchant."

Silas glanced at him.

"I beg your pardon?"

"Nothing. It’s a professional title."

Aria sat down before the conversation could become more complicated.

"Thank you for agreeing to meet us."

"Of course. I understand you’re interested in the regional transport consortium."

"We’re interested in how it operates."

Silas returned to his chair.

"An important distinction."

Lucan placed a folder on the desk.

"We’ve reviewed the public information. The consortium coordinates independent transport companies through a shared database. It also maintains an alternative booking channel during disruptions to the Regional Materials Exchange."

"Correct."

"Who owns the database?"

"The consortium does."

"Who owns the underlying information?"

Silas smiled slightly.

"That’s a more interesting question."

Aria waited.

"The participating companies retain ownership of their individual commercial records. The consortium receives permission to use selected operational information for coordination. It does not own the underlying contracts or customer relationships."

"Can it sell the information?"

"Not under the current agreement."

"Can it share the information with third parties?"

"Only with authorization from the relevant participant, or where a legal obligation requires it."

"Can you access it?"

Silas looked at her.

"I am a financial backer. I receive financial reports and performance summaries. I do not personally manage the database."

"That wasn’t my question."

For the first time, Silas stopped smiling.

He opened a drawer and removed a document.

"My investment agreement gives me access to aggregate performance data, audited financial statements, and reports concerning operational risk. It does not grant me access to individual customer records or the authority to alter bookings."

Aria examined the document.

The distinction was plausible.

It was also important.

"Who can alter bookings?"

"The participating companies can modify their own entries. The consortium’s administrative team can correct errors and coordinate shared requests. Every change is logged."

"Can the administrator override a company’s booking?"

"Only in specific circumstances, such as duplicate entries, technical errors, or a formally agreed emergency coordination procedure."

"Who approves an override?"

"The consortium’s operations committee."

"Who sits on it?"

"Representatives from participating carriers and warehouses."

"Do you have a vote?"

"No."

"Can you appoint members?"

Silas leaned back.

"I can recommend candidates. The members elect their representatives."

Aria wrote that down.

"Then why did you invest?"

"Because the official transport network was inefficient, and independent companies were losing money because of it. A functioning alternative benefits everyone who uses it."

"Everyone?"

"Everyone who participates."

"That is not quite the same thing."

Silas smiled again.

"No. It isn’t."

The conversation lasted nearly two hours.

Silas explained how the consortium had developed.

It began with four transport companies that were frustrated by repeated booking delays. They started sharing vehicle availability through a common ledger. Eventually, warehouses joined. The arrangement expanded, and a small administrative team was established to coordinate the information.

It was never intended to replace the Regional Materials Exchange.

It was intended to provide an alternative when the official system became unreliable.

The consortium now coordinated thirty-one transport companies and twelve warehouses.

Its records were not perfect, but its participants updated them more frequently than the official registry.

Lucan examined the performance figures.

"These delivery times are considerably better than the regional average."

"Because the consortium operates on smaller routes and doesn’t handle every category of material," Silas replied. "You should be careful when comparing the figures."

Lucan nodded.

"Fair."

Aria studied the investment report.

"Your returns are based on membership fees and coordination charges?"

"Primarily."

"Do you charge more during emergencies?"

"No."

"Do you reserve the right to change fees?"

"Under the agreement, fee adjustments require committee approval and advance notice."

"Can the consortium refuse a participant?"

"Certainly. It has to protect the integrity of its network."

"What does that mean?"

"Participants must provide accurate information, maintain agreed standards, and pay their fees."

"Who determines whether someone has violated those standards?"

"The operations committee."

"And can a participant appeal?"

"Yes, to the independent commercial review panel."

Aria looked at Lucan.

He had already found the relevant clause.

It existed.

That was encouraging.

Then she reached the section concerning emergency coordination.

Her expression changed.

"Silas, what does this mean?"

He leaned forward.

"Which section?"

"Clause fourteen. The consortium may temporarily suspend a participant’s access where continued participation threatens the stability of the network."

"That’s a standard protection."

"How long can the suspension last?"

"Until the matter is resolved."

"Who determines that?"

"The operations committee."

"Can the participant access its own historical records during the suspension?"

Silas looked at the clause.

"Not through the shared platform."

"Can it retrieve a copy?"

"Upon request."

"How quickly?"

"That would depend on the circumstances."

Aria closed the document.

"So a company could lose access to the network, and potentially to its own operational history, without a defined deadline for restoring access."

"Only if there were a serious breach."

"Then the agreement should define the breach, the duration, and the appeal process."

Silas considered her.

"You are unusually interested in the possibility of failure."

"Because the consortium exists to provide continuity. If its members can lose access without predictable procedures, then the backup system becomes another dependency."

Silas glanced toward Lucan.

"Your associate has a talent for finding the uncomfortable parts of an agreement."

Lucan smiled politely.

"I’ve learned to read the uncomfortable parts first."

Kelme nodded.

"He’s becoming difficult. It’s a sign of professional growth."

Silas offered them a tour of the consortium’s operations office.

Aria accepted.

The office occupied the ground floor of the same building as the investment firm. It was smaller than the Materials Exchange headquarters, but noticeably busier.

Operators sat at desks with route schedules and shipment lists. A large board displayed available vehicles, warehouse capacity, and current delivery requests.

A woman approached them.

"Mr. Veyr."

"This is Aria and her colleagues. They are examining our continuity arrangements."

The woman introduced herself as Nessa Corin, operations director.

She explained that the database was maintained by a small technical team, while the daily coordination work was handled by dispatchers.

"Can you show us what happens when a carrier becomes unavailable?" Aria asked.

Nessa opened a sample record.

"Each carrier updates its available vehicles. If a vehicle breaks down or a driver becomes unavailable, the carrier marks the assignment as disrupted. The system identifies affected deliveries and sends a notification to the relevant participants."

"Can another carrier take the delivery?"

"If one has suitable capacity and agrees to accept it."

"Does the system automatically transfer the booking?"

"No. That would create problems. The replacement carrier must confirm the vehicle, route, loading requirements, and price."

Aria nodded.

"Good."

Nessa continued.

"We also maintain a secondary copy of the database."

"Where?"

"In a separate facility."

"Who controls it?"

"Our technical administrator."

"Can the consortium operate if the main office is unavailable?"

"Yes, through the secondary system."

"Have you tested that?"

Nessa hesitated.

"We’ve tested the recovery process."

"Under realistic operating conditions?"

"Not with every participant connected."

Aria looked at Silas.

"So the consortium has a backup system, but hasn’t demonstrated that the entire network can use it during a major outage."

Silas folded his arms.

"That’s fair."

Nessa looked slightly uncomfortable.

"We can arrange a test."

"Would it include the loss of the main office and the primary database?"

"Yes."

"Would it include the loss of the technical administrator?"

Nessa frowned.

"That would be more difficult."

"Why?"

"Because the administrator manages the recovery credentials."

Aria looked at the system display.

There it was.

A single person.

Not a factory. Not a road. Not a warehouse.

A person who held the knowledge and access required to restore the backup system.

"Who is the administrator?" she asked.

Nessa glanced at Silas.

He answered.

"His name is Oren. He’s been with us since the beginning."

"Does anyone else know how to perform the recovery?"

"Our technical team understands the process, but Oren handles the final authorization."

"Can the process be documented?"

"Certainly."

"Has it been?"

Nessa did not answer immediately.

Silas looked toward the office.

"Nessa, I think we should review that."

She nodded.

Aria wrote another note.

Technical dependency: recovery authorization concentrated in one administrator.

The consortium had solved one problem.

It had created another.

They left the office shortly before sunset.

Silas accompanied them to the entrance.

"I hope you found the visit useful."

"We did," Aria replied.

"Do you intend to join the consortium?"

"Not yet."

"Why?"

"We need to review the agreement, the data protections, and the continuity arrangements."

Silas smiled.

"I expected nothing less."

He paused.

"There is something I would like to offer."

Aria waited.

"New Beginning could join as a full participant. You would receive access to the shared booking network, reduced coordination fees, and priority consideration during regional disruptions."

Kelme glanced at Aria.

"Priority consideration again."

Silas heard him.

"It’s a useful benefit."

"Does it guarantee a vehicle?" Aria asked.

"No."

"A loading slot?"

"Subject to availability."

"Delivery?"

"No. That depends on the carrier and the route."

"Then what exactly are we receiving?"

"Better access to information and coordination."

Aria considered the offer.

That was not worthless.

In fact, it could be useful.

But she wanted to know what the consortium expected in return.

"What would membership require?"

"Accurate reporting of available transport needs, payment of membership fees, and compliance with the shared coordination rules."

"Would we be required to disclose our customer contracts?"

"No."

"Our production capacity?"

"Only the information necessary to coordinate deliveries."

"Could the consortium claim priority over our existing bookings?"

"Not without your agreement."

"Could you use our participation to claim that New Beginning has consented to regional emergency obligations?"

Silas’s expression became more serious.

"No. Membership in a private consortium does not create a public emergency obligation."

Aria nodded.

"Then put that in writing."

Silas laughed softly.

"You really do prefer everything in writing."

"I prefer knowing what I’ve agreed to."

"Fair enough."

He offered them a draft membership agreement.

Aria accepted it.

As they walked away, Kelme glanced over his shoulder.

"He was polite."

"Yes."

"Reasonable."

"Yes."

"Helpful."

"Somewhat."

Kelme looked at her.

"You’re disappointed."

"Why would I be?"

"Because you came here expecting a villain and found a businessman."

Aria stopped walking.

"I didn’t expect a villain."

"Then what did you expect?"

"Someone who understood the value of controlling a system that everyone else needed."

Kelme considered that.

"And?"

"He does."

The council reviewed the offer the following evening.

Martha read the membership agreement while Lucan explained the financial terms.

The fees were reasonable. The consortium’s delivery records were impressive. The data protections were better than those used by the official exchange in several respects.

But there were concerns.

"Full membership requires us to share transport requirements for every commercial shipment," Martha said.

"Not customer names or contract values," Lucan replied. "Just product category, quantity, destination, and delivery window."

"That’s still commercially sensitive."

"Agreed."

Yara looked at the transport schedule.

"Would membership help with clay deliveries?"

"Potentially. The consortium has access to alternative carriers and warehouses."

"Can it guarantee that our clay arrives?"

"No."

"Can it guarantee that our current carrier isn’t delayed?"

"No."

Yara shrugged.

"Then it’s useful, but it doesn’t solve the problem."

Aria nodded.

"That’s why I’m considering limited membership rather than full participation."

Martha looked up.

"What would that involve?"

"We join the network for specific routes and shipments. We share only the information required for those transactions. We don’t publish general production capacity or customer lists."

"Would they accept that?"

"Silas said they would consider it."

Lucan turned a page.

"There is another issue. The consortium’s fees are lower for full members because they contribute more information and pay an annual membership charge."

"Which means they want the data," Martha said.

"Not necessarily for commercial use. The more accurate their information, the better their coordination."

"Still," Aria said, "we should not give more information than the service requires."

Kelme raised his hand.

"I have a proposal."

Aria sighed.

"Go ahead."

"Can we join the consortium, receive the benefits, and refuse to attend meetings?"

Martha looked at him.

"That’s not a proposal. That’s your personal dream."

"It is a dream worth pursuing."

Aria smiled.

"Unfortunately, we need to understand the system before joining it."

The council voted to authorize negotiations for a limited three-month membership trial.

They would not agree to full membership yet.

They would not share customer identities or general production figures.

They would retain the right to withdraw with thirty days’ notice.

And the consortium would have to provide a clear procedure for accessing records if membership was suspended or terminated.

It was a cautious agreement.

But it was an agreement.

The next morning, Aria received a message from Nessa Corin.

The consortium had scheduled a test of its secondary database.

She invited New Beginning to observe.

Aria accepted.

The test began two days later.

At first, everything worked.

The primary database was disconnected.

The secondary system activated.

Dispatchers logged in from separate locations. Carriers confirmed their vehicles. Warehouses reported available loading capacity.

The process took less than twenty minutes.

Nessa looked pleased.

"Everything is functioning."

Aria studied the display.

"Can you restore a booking that was changed immediately before the outage?"

Nessa checked.

"Yes."

"Can you identify who changed it?"

"Yes."

"Can you restore the original record without overwriting later changes?"

"Yes."

"Can you operate if Oren is unavailable?"

Nessa hesitated.

"We have a technical procedure for that."

"Can we test it?"

Oren, who stood near the back of the room, stepped forward.

"I can demonstrate the recovery process."

Aria looked at him.

"Without using your authorization?"

He frowned.

"The process requires my credentials."

"Then it doesn’t demonstrate that the consortium can operate without you."

Silence.

Oren looked toward Nessa.

Nessa turned to Silas.

Silas, who had attended the test, folded his arms.

"She’s right. We should test the alternative authorization procedure."

Oren seemed uncomfortable.

"It’s not a simple process."

"Then we should know that," Silas replied.

The test continued.

Oren handed over the recovery instructions.

Nessa attempted to follow them.

The first stage worked.

The second required a code that had not been included in the documentation.

Oren supplied it.

The third required a security approval that could only be issued by Oren.

The process stopped.

Nessa stared at the screen.

"We need a second authorized administrator."

"Or a documented emergency authorization procedure," Aria said.

Oren shook his head.

"Giving more people access increases the risk of unauthorized changes."

"Agreed," Aria replied. "But having only one person capable of restoring the system creates a different risk."

Silas watched the screen.

"How long would it take to establish a second authorization process?"

"Several weeks," Oren answered.

"Then we should begin."

Nessa made a note.

The exercise ended with a list of improvements.

The consortium had successfully demonstrated that its secondary database could operate during a primary system outage.

It had not demonstrated that it could recover independently of its primary administrator.

Meret Sol, who had attended as an observer, recorded the result.

Aria read the final statement.

The consortium has achieved technical redundancy but not full operational independence.

She liked that sentence.

It was accurate.

A week later, the consortium sent its revised membership agreement.

It included:

* A limited data-sharing schedule.

* Separate permissions for individual shipments.

* A right to retrieve historical records.

* A defined suspension review.

* A thirty-day withdrawal procedure.

* A commitment to establish a second recovery administrator.

It also included a new clause.

Participating members may be requested to contribute available transport or storage capacity during declared regional disruptions, subject to their existing agreements and the applicable emergency framework.

Aria read it carefully.

Then she circled it.

Martha looked over her shoulder.

"What’s wrong?"

"Nothing yet. But the phrase available capacity is undefined."

"Again?"

"Again."

Lucan took the document.

"We can propose a definition."

Aria nodded.

"Verified capacity, existing commitments, temporary additional capacity, and voluntarily reserved capacity. Four separate categories."

Kelme appeared in the doorway.

"Can we add a fifth category?"

"No."

"Unavailable capacity."

"That would simply be zero."

"Then why does everyone keep pretending zero is a suggestion?"

Aria smiled.

"Because people prefer numbers that make their plans look better."

She returned to the agreement.

This time, however, she noticed something else.

The clause referred to the applicable emergency framework.

That framework was still being drafted by the Regional Authority.

Which meant the consortium was asking its members to agree to a future set of rules that did not yet exist.

Aria placed the document down.

"We cannot sign this version."

Martha frowned.

"Even with the other improvements?"

"The other improvements are good. This clause is not."

"Could we simply remove it?"

"Possibly. But I want to know why it was included."

Lucan looked at the signature page.

"I’ll ask."

The answer arrived the next afternoon.

The consortium’s legal adviser had included the clause because the Regional Authority was considering a new emergency coordination framework.

The Authority had informally discussed whether private logistics networks should be required to participate in regional continuity arrangements if they became sufficiently important.

No final proposal existed.

No law had been changed.

But the possibility was real.

Silas requested another meeting.

Aria agreed.

This time, he came to New Beginning.

He arrived without an entourage, carrying a single folder.

"I understand you’ve objected to the emergency capacity clause."

"Yes."

"It’s intended to protect the region."

"Then it should be written into a clear legal framework, not hidden in a membership agreement."

Silas sat down.

"The Authority may eventually require critical logistics providers to cooperate during declared emergencies."

"Perhaps. But the agreement shouldn’t make private members responsible for obligations that have not yet been defined."

"What would you suggest?"

"Keep the existing voluntary coordination clause. If the law changes, review the agreement then. Members should not consent in advance to undefined duties."

Silas considered this.

"That may create uncertainty for the consortium."

"It creates less uncertainty for its members."

He smiled faintly.

"You have a talent for turning simple agreements into complicated negotiations."

"Only when the simple version hides something important."

For a moment, Silas said nothing.

Then he opened his folder.

"I have another reason for coming."

He placed a document on the table.

It was a proposal from the Regional Authority.

The Authority was considering designating the consortium as a critical regional logistics network.

If approved, the consortium could be required to maintain continuity procedures, report operational disruptions, and cooperate with emergency allocation decisions.

Aria read the document.

"Who submitted this?"

"Director Veyna’s department, with input from the infrastructure review."

"Has the consortium agreed?"

"Not yet."

"Why did you bring it to us?"

"Because your settlement is becoming an important participant in regional supply chains. I thought you should see the proposal before the hearing."

Aria looked up.

"Are you asking us to support the designation?"

"I’m asking you to examine it."

She returned to the document.

The proposed designation was not necessarily unreasonable. The consortium coordinated a significant portion of regional transport and warehouse access. Its failure could affect businesses that had no direct relationship with it.

But the proposal also contained a section allowing the Authority to issue temporary coordination directions during declared emergencies.

The scope was broad.

The criteria were unclear.

The review period was vague.

Aria placed the document beside the membership agreement.

Two systems.

One official, one private.

Both becoming increasingly important.

Both potentially capable of deciding where goods moved.

And both now facing the same question.

Who controlled the controller?

That evening, Aria sat alone in the council room.

The regional map covered the wall.

Northbank.

The Materials Exchange.

The transport consortium.

The warehouses.

The alternative routes.

Every connection represented a relationship, a contract, or a dependency.

She had once believed that independence meant controlling what happened inside New Beginning.

Now she understood that the settlement could retain every internal right and still become vulnerable to decisions made far beyond its borders.

A supplier could stop processing clay.

A carrier could lose access to a route.

A booking system could change its priorities.

A private consortium could suspend a member.

An Authority could issue an emergency direction.

None of those actions required anyone to own New Beginning.

Yet every one of them could affect its future.

Kelme entered quietly.

"You’re still here."

"Yes."

"It’s late."

"I know."

He looked at the documents.

"More agreements?"

"More systems."

He sat opposite her.

"Do you ever think we should simply build a wall around the settlement and refuse to deal with everyone?"

Aria smiled.

"For about five seconds every morning."

"And then?"

"Then I remember that we need clay, tools, roads, merchants, and customers."

"Unfortunate."

"Very."

She pushed the map toward him.

"What do you see?"

Kelme examined it.

"A lot of lines."

"What else?"

"Some lines are thicker than others."

"Why?"

"Because more things depend on them."

Aria nodded.

"Exactly. Those are the connections we need to understand best."

Kelme traced one of the lines.

"And this one?"

"That is the route through the Materials Exchange."

"And this?"

"The consortium’s alternative."

He looked at both.

"They meet here."

His finger rested on a small warehouse marked near the eastern road.

Aria leaned closer.

It was a facility she had barely considered.

The warehouse belonged to a company that stored finished goods before distribution. It served both the official exchange and the private consortium.

It was not a major processing facility.

It did not own transport vehicles.

It did not operate a booking system.

But both networks depended on it.

Aria stared at the map.

The warehouse was a shared point of failure between the two supposedly independent systems.

If it became unavailable, neither network could easily replace its storage capacity.

She checked the ownership record.

The company was controlled by a holding group whose largest investor was...

Silas Veyr.

Aria leaned back.

Kelme watched her expression.

"That’s bad, isn’t it?"

"Not necessarily."

"But it is interesting."

"Yes."

"Do we have another meeting?"

"Probably."

Kelme closed his eyes.

"I knew it."

Aria looked again at the warehouse.

She wasn’t interested in accusing Silas of anything. He had invested in businesses that solved real problems. His companies provided services people needed.

But the region was slowly building its resilience around systems that shared the same financial interests.

The official network and the private alternative were not as independent as they appeared.

And the person who had financed the alternative also had influence over one of the facilities both systems needed.

Aria took a fresh sheet of paper.

At the top, she wrote:

COMMON OWNERSHIP IS NOT THE SAME AS COMMON CONTROL.

Then, beneath it:

BUT IT CAN CREATE COMMON VULNERABILITY.

She put down her pen.

The next hearing would be about the proposed designation of the transport consortium.

But Aria now had a different question to ask.

If the Authority wanted to designate a network as critical infrastructure, would it also examine the financial relationships connecting that network to its supposed alternatives?

Because if it didn’t, the region might spend years building backup systems that all depended on the same few people.

And the day one of those people made a decision the region couldn’t accept, everyone would discover how little independence they actually had.

Reading settings

Reading style
Theme
Scroll settings

Start Auto Scroll to close settings and begin. Touch or scroll to pause.

Text to speech

Uses your browser’s voices.

Jump to chapter

Knowledge Is Power: The Last Reader

202 chapters

View all chapters