numbers 14:9

Jehovah is with us. Do not fear them.​

But you must not rebel against Jehovah, and you must not fear the people of the land, for we will devour them. Their protection has been removed from them, and Jehovah is with us. Do not fear them.

—Num. 14:9.

The full verse is interesting (as is the chapter). Caleb and Joshua are EMPHATICALLY trying to convince their people to relax and trust their God, countering what the other spies reported.

I always miss that they were ‘chieftains’. Numbers 13:2 points out they were heads, or chieftains. So responsible, and capable.

Yet they lacked faith that God would care for them. They were sinking Peters.

They saw the job before them as insurmountable. Too intense.

Yet Caleb and Joshua knew the truth: 1+ Jehovah is a majority in any case.

Whatever your battle is today, you can win it. And tomorrow. And the day after that. You will be scared. You will feel like a failure. But you will succeed.

If faith were the possession of all men… this would be easy. but it is not. On a long enough timeline, the faithful will always succeed. We just have to keep our eyes up and fixed on the future.

If nothing else, it makes currently failures less significant.

Do not fear humans. Do not fear yourself. There is good in you. Jehovah sees our potential, and accepts our state. You and I are masterpieces found at a garage sale.

There’s a reason we remember the names of Joshua and Caleb.

Their protection has been removed, let’s go a-conquering!!!

I had my book club today, and I was passionately, talking and making jokes about the book, and explaining the issues that I found with it. It’s like one of those things where I kind of complain or play it up a little bit and just am generally a very expressive person. This friend is not at all expressive, and she said that I was like really emotional about it, and I kind of felt like I took it as an insult, or like this person thought that I was legitimately mad or upset about this book. I honestly got a little bit defensive, and I reminded them that I’m just doing this kind of for content because I think it’s fun but I really don’t care, I can talk about it in a really bland way and I’m completely OK not talking about it either. But I think it’s just generally more entertaining and fun to be expressive. And I think about how this is a little bit like my general approach to life of trying to keep my energy and enthusiasm up where I can. I feel like I am orbiting my resting state of depression. The more enthusiastic and joking and energetic I am the faster I go, and it stops me from crashing. But if I go too fast, it is also destructive and I lose orbit. And I think this is a fairly good analogy for life. Staying in that sustainable band and orbiting.

My coffee mug gets empty too fast. I don't have enough time to just sit here and type this garbage.

I pack my lunch, and walk to work. I show up on time, and punch the clock. I say, good morning to some, before work begins. Sometimes we chat, and sometimes not. Work begins.

Safety is paramount above all things. I work hard, and I work efficiently. My work is accurate. I help out when asked by my coworkers. I stay calm. I get along. I don't yell. I don't blame, or snitch. I clean as I go. The machine I operate weighs about 4500kg, and can lift pallets down from 8 meters high. It is a lot of responsibility, and requires skill. The task that is assigned to me is dirty, and intense, and has a lot of (at times heavy) lifting involved.

None of that counts for anything.

My worth as an employee is mostly based upon the transactions that go from the scanner on my machine, to the screen on the laptop that my boss stares at all day. Also somewhat whether or not I measure up to the standards of his nepotism (and I mostly don't measure up). A lot of the work I do does not show up on the screen as a transaction. I've pointed that out many times to him, but he a) doesn't like me, and b) I suspect he is going senile.

My worth to my coworkers is mostly based upon whether or not they have to wait for me to deliver the products that they need to assemble orders, and whether or not I'm close by when they need assistance. If I'm on time, and there when they need me; they like me. If I'm not they turn on me in an instant, and won't hesitate to, as they say, 'throw me under the bus'. They expect me to stop 100% of the time, but then also expect me to deliver the products to location on time. They can't see how fucking stupid that is. If I'm doing the one thing, I'm not doing the other. I can't do more than one thing at a time.

It is a toxic and hostile workplace. Sometimes it gets to me, and sometimes it does not. It depends on how well I can drift below the radar. The pay rate when I started there over nine years ago was not too bad, but now it is really not competitive (on top of the sleazy oligarchs vacuuming up the wealth from all things). I know the pay is no longer competitive from looking at job ads.

I think of leaving sometimes. If I left though, I would not get benefits or vacation time for awhile. Possibly never if I ended up being a temp again. The other thing that deters me from leaving is that I would most likely end up doing the same stupid shit anyway. Only it would be in a different building with different people. It could even end up being a more toxic workplace.

I'm out of time. The coffee ran out awhile ago. I have to get ready to go there. I've been doing variations of this more days than not for over 37 years of my life.

It is no wonder I'm so tired.

Long weekend coming.

Less than 30 days to vacation time.

Never a dull moment

How to Survive a Zombie Invasion- Part 1: Infected, Fast, Living “Zombies”

I've always wanted to do a survival guide for zombies but with a twist. None of the bullshit they push in movies about going out on the open road, forming a militarized community... etc. No Walking Dead or Last of Us nonsense. Something realistic a normal human can pull off. We will focus on the United States for a few reasons: 1- I know it. 2- Very high density of guns. 3- A lot of land. Obviously somewhere like Singapore would have a very different strategy, mainly hope the government can figure it out very expediently or you are zombie chow. So the issue is, what is a zombie? There are a few different options:

1) Infection, like rabies but with an impossibly short incubation period. We will use 28 Days Later as a template for this. If you have bodily fluid contact (a bite, blood gets in your eye or a cut, etc) its less than a minute before you are thrown into a terminal homicidal rage. In this case the infection spreads rapidly, but the “zombies” are technically alive so attrition is rapid.

2)True undead: zombies are the corpses of the deceased returned to attack the living, so long as they have somewhat of an intact brain. They are slow, ponderous, but do not tire and are immune to most things that would kill a normal human like suffocation, disease, poison, starvation, dehydration, etc. Basically you need to either destroy their brain or eventually they rot and fall apart. In some lore, they don't rot at all, but I think we will say that eventually the fall apart. So George Romero zombies like in Night of the Living Dead and the OG Dawn of the Dead. Walking Dead mostly had this, but they also said it was an infection... which didn't really make a lot of sense because everyone came back from the dead who died. So we will stick with Romero's logic. It could be an alien asteroid, magical curse, or whatever else... just, the dead are walking.

3)Hybrids and edge cases. There are many stories that fuse the two. New Dawn of the Dead, where they are fast Romero Zombies. Worst of both worlds for survivors. Mutant undead, where they regenerate and/or have powers. Fungal Zombies, like last of us, where they are really part of a larger threat with more variation. Necromorphs, like in Dead Space, where holy shit are you in trouble. Voodoo Zombies, where there is a mystic element to it. Return of the Living Dead zombies, where apparently brains are a culinary delicacy because they are “spicy”, and many many more. I never watched Santa Clarita Diet, but I'm assuming Drew Barrymore is her own class of zombie. Anyway, we are ignoring all of these and are going to focus on the first two. Maybe I'll do posts on the other types later when I feel like it.

So let's start with the Rage Infected zombies. This is arguably the most realistic case, though the incubation time is comical. Nothing would work that fast unless the infected cells were already systemically throughout your body and the bite was just sort of a Manchurian Candidate style activation. But short of that, incubation would probably be hours or days. Still, an infection is a real phenomenon, while returning from the dead is not. So, how would you survive? Here is a guide based more on risk analysis than cinematic heroics. I've decided to write it as if its a government handout for people to consider in the event of a “Rage Zombie” apocalypse. Of course, without any political considerations or government corruption, just if they actually want to give you best advice on how to survive:

---

Surviving Rage Infected Zombies- STAY PUT

ABSTRACT: During a fast-moving infected outbreak, the safest general strategy is to stay where you are unless remaining there is becoming genuinely dangerous. Every trip outside creates immediate exposure to infection, injury, violence, and civil disorder, while a secure person indoors can conserve water, calories, medication, and energy. Because the infected are still biologically human, time should work against them through dehydration, exhaustion, injury, exposure, and eventual starvation.

Do not leave simply because utilities fail, food is running low, or conditions outside appear quiet. Instead, calculate how many days of safe water, food, essential medication, and safe shelter you have remaining. Stay put while those reserves provide a reasonable margin; begin planning when the shortest approaches one week, and treat roughly three days of an essential resource as an urgent resupply threshold. Leave sooner only if the shelter itself becomes unsafe.

The governing principle is simple: do not accept today's extreme outside risk to solve a shortage that may not become critical until next week. Your supplies are buying time, and during a fast-infected outbreak, time is likely your greatest advantage.

PUBLIC SURVIVAL GUIDANCE: FAST-MOVING INFECTED OUTBREAK Shelter-in-Place, Resource Management, and Resupply Decision Guidance

This document applies to an emergency in which an infectious agent causes rapid onset of extreme aggression, loss of normal judgment, and violent pursuit behavior while infected persons remain biologically alive. It assumes that transmission occurs primarily through bites or direct exposure to infected bodily fluids, that onset after exposure may be rapid, and that infected persons retain approximately normal human physical capabilities during the early stages of infection.

Under these conditions, the safest action for most people who are already inside a secure residence will be to remain there. This recommendation may appear counterintuitive when normal government services are failing and infected persons are present in the community. However, the principal objective during the initial phase is not to obtain the largest possible stockpile of supplies. It is to minimize the number of opportunities for infection or serious injury while maintaining enough water, food, medication, sanitation, and environmental protection to remain inside.

The decision to leave shelter should therefore be treated as a risk-management decision. Remaining inside consumes resources gradually. Going outside creates immediate exposure to infected persons, frightened civilians, traffic accidents, fires, hazardous crowds, contaminated bodily fluids, and other dangers at a time when emergency assistance may be unavailable. During the initial phase of the emergency, a household with adequate resources should assume that outside exposure represents the greater risk.

The central question is not, “Would additional supplies be useful?” Additional supplies are always useful. The correct question is, “Will remaining here for another day create more danger than leaving today?”

For households with adequate resources, the answer during the acute phase will usually be no.

Determine Your Shelter Runway Immediately

Every household should calculate its “shelter runway” as soon as it is secure. This is the number of days the household can remain inside before an essential resource approaches a critical level. Four categories should be evaluated separately: safe drinking water, food, essential medication, and habitability. The category with the shortest safe duration determines the household's practical shelter runway.

For example, a household may possess 25 days of food and 20 days of drinking water but only eight days of a medically essential prescription. Its practical runway may therefore be approximately eight days. Another household may possess a month of food, medication, and water but live in an apartment that will become dangerously cold within four days without heat. Its practical runway may be approximately four days.

Recalculate this number at least once each day. Do not rely on estimates such as “we have plenty of food” or “there are several cases of water.” Count the resources and convert them into person-days.

Calculating Drinking-Water Runway

Safe drinking water is normally the most important resource. CDC emergency guidance recommends storing at least one gallon of water per person per day for drinking, cooking, brushing teeth, and other essential uses. Actual requirements may be greater in hot conditions and for children, pregnant persons, people who are ill, and people performing substantial physical activity.

Using one gallon per person per day provides households with a simple conservative planning figure. One person with 12 gallons has approximately 12 planning days. Two people with 12 gallons have approximately six. Four people with 20 gallons have approximately five.

Do not deliberately dehydrate yourself in an attempt to extend this period. Reduced physical activity will generally reduce water needs, but drinking dangerously small quantities creates weakness, confusion, kidney injury, cardiovascular stress, and eventually a medical emergency. A survivor who has conserved water by becoming severely dehydrated has not improved his survival position.

Bathtubs require special consideration. A typical bathtub may hold approximately 40 to 60 gallons, making it extremely useful for emergency water storage. However, bathtub water should not automatically be counted as safe drinking water. CDC emergency materials specifically recommend filling bathtubs for uses such as toilet flushing, while commercially bottled water or water stored in appropriate clean containers is preferable for drinking. If authorities provide instructions for treating available water, follow those instructions. Bathtub water may still preserve potable supplies by supplying water for sanitation and other non-drinking purposes.

If water service is functioning when the emergency begins, fill appropriate clean containers immediately. Do not wait for pressure to fail. Preserve commercially bottled water for drinking when possible and use nonpotable stored water for purposes that do not require potable water.

Loss of running water does not automatically require evacuation. It changes the calculation from an indefinite water supply to a finite one. If two adults possess 20 gallons of safe water after service stops, they have approximately ten planning days at one gallon per person per day. They should begin planning for resupply, but they ordinarily should not enter a dangerous environment immediately if outside conditions are rapidly deteriorating.

Water should not normally be allowed to reach zero before a resupply attempt. Maintain a reserve sufficient to survive an unsuccessful trip or unexpected delay. As a general planning principle, households approaching approximately three days of safe drinking water should regard resupply or relocation as an urgent problem. The purpose of this reserve is not to suggest that death occurs after three days without water; survival without water varies enormously. It is to ensure that a failed attempt does not immediately become fatal.

Extreme real-world survival cases should not be used as rationing targets. In 1979, 18-year-old Andreas Mihavecz survived approximately 18 days after being accidentally left in an Austrian holding cell without normal access to food or water. He was discovered close to death, and reports indicate that he obtained at least some moisture from condensation. His survival demonstrates the variability of human physiology under deprivation, not that 18 days without water is safe or reproducible. A government survival plan should be designed to prevent anyone from approaching such conditions.

Calculating Food Runway

Food should be calculated in approximate calories rather than meals. A household that says it has “one week of food” may actually possess several weeks of survival calories, while another household with a refrigerator full of low-calorie perishable foods may have much less stored energy than expected.

Inventory the entire residence. Include canned foods, cereal, oatmeal, rice, pasta, crackers, bread, nuts, peanut butter, cooking oil, flour, snack foods, shelf-stable beverages, frozen foods, pet food intended for human consumption only as an extreme last resort, and any other safe edible products. Record approximate calories using package labels where available.

Calorie-dense foods are particularly important. A container of cooking oil may not resemble an emergency food supply, but fat contains approximately nine calories per gram. Peanut butter, nuts, oils, chocolate, crackers, rice, pasta, and similar foods can contain large amounts of energy in relatively small volumes.

A person with 30,000 calories has 15 days of food at 2,000 calories per day, 20 days at 1,500 calories per day, and 30 days at 1,000 calories per day. A person with 45,000 calories has approximately 30 days at 1,500 calories per day.

These numbers are planning examples, not recommended diets. Calorie requirements differ substantially according to age, body size, pregnancy, health, temperature, and activity. Severe calorie restriction is inappropriate for many people and eventually impairs strength, judgment, immune function, and the ability to respond to an emergency.

Nevertheless, healthy adults should understand the difference between hunger and imminent starvation. The human body contains substantial stored energy. Running out of normal meals does not mean that death will occur within days.

An extraordinary medical case illustrates this distinction. Angus Barbieri, a severely obese Scottish man, underwent a medically supervised fast lasting 382 days in 1965–66. He consumed fluids and received vitamins and, during portions of the fast, electrolyte supplementation. Other medically supervised prolonged fasts have lasted weeks or months. These cases are not models for emergency behavior; prolonged fasting can produce serious electrolyte and other medical complications and should ordinarily occur only under medical supervision. They demonstrate only that the human time scale for calorie deprivation is fundamentally different from the time scale for dehydration or traumatic injury.

For emergency planning, a household should reduce unnecessary food consumption but should not attempt extreme fasting. Preserve enough nutrition to maintain clear thinking, body temperature, immune function, and the physical ability to relocate if necessary. The objective is not to make food last as long as biologically possible. It is to make food last longer than the acute phase of the outbreak.

Use Food in the Correct Order

If electrical service becomes unreliable, eat foods according to perishability. Use refrigerated and frozen foods while they remain safe, then transition to shelf-stable foods. Do not repeatedly open refrigerators and freezers simply to inspect them. Government food-safety guidance notes that emergency food should ideally require little or no refrigeration, cooking, or water.

Discard unsafe perishable foods rather than risking foodborne illness. A case of severe vomiting or diarrhea is dangerous during any emergency because it consumes water, causes weakness, and may require medical care that is no longer available.

Do not consume excessively salty foods merely because they are available if drinking water is limited. High salt intake can increase thirst and water requirements.

Medication May Determine Your Real Deadline

Medication should be inventoried on the first day, not when only one or two doses remain. Write down the name of each medication, the prescribed dose, the number of doses remaining, and the number of days the supply will last.

Medication should then be considered according to the medical consequences of interruption. Some medications can be missed with relatively little immediate danger. Others cannot. Insulin and certain medications for seizure disorders, adrenal disorders, cardiovascular disease, severe psychiatric conditions, and other illnesses may create serious risks if interrupted or improperly rationed.

Do not reduce or alter a prescribed dose simply to extend the supply unless qualified medical guidance specifically advises doing so. A person with 30 days of food but only five days of a medically critical medication does not have a 30-day shelter runway.

Seek official information about emergency pharmacy or medical distribution before attempting an independent supply run. Pharmacies, hospitals, and clinics may be high-exposure locations during the acute phase because injured and potentially infected persons are likely to concentrate there. If medication will become critical within several days, begin identifying options while doses remain rather than waiting until the final dose has been taken.

Refrigerated medication creates an additional concern during power failure. CDC guidance notes that some medications lose strength if improperly stored and provides specific emergency guidance for insulin. Medication labels and official emergency medical instructions should be followed whenever available.

Electricity Is Not Itself an Evacuation Trigger

Loss of electrical power should be evaluated according to its consequences rather than treated automatically as a reason to leave.

If outside temperatures are moderate, safe water remains available, food can be eaten without electrical cooking, no occupant depends on powered medical equipment, and the building remains secure, a power failure may substantially reduce comfort without substantially reducing immediate survivability.

In other circumstances, the same outage can determine the household's shelter runway. A high-rise building may lose water pressure when pumps stop. An electrically controlled heating system may fail during winter. Extreme summer temperatures may make upper-floor apartments dangerously hot. Refrigerated medications may become compromised. Sewage or sump pumps may stop. Elevators may fail, creating serious problems for residents with limited mobility.

Ask what the electricity was doing for you. If its functions can be replaced or temporarily abandoned, remain sheltered. If loss of electricity will make the residence medically or environmentally dangerous within a predictable period, that period becomes part of the shelter-runway calculation.

Do not use grills, charcoal devices, generators, or other combustion equipment indoors. Carbon monoxide poisoning can kill occupants without warning.

Loss of television, internet access, cellular service, lighting, entertainment, or ordinary appliances is not by itself a reason to evacuate.

Understand Why Waiting Changes the Risk

Sheltering works particularly well against fast infected persons because the household and the infected population are consuming resources at very different rates.

A sheltered person can minimize movement, drink deliberately, eat deliberately, sleep, remain dry, regulate temperature, clean wounds, and avoid unnecessary injury. A violently infected person may spend substantial periods running, fighting, shouting, wandering outdoors, and sustaining untreated injuries. If infected persons remain biologically human, none of these activities is free.

The infected still require water. Their muscles still produce heat. Their feet develop injuries. Tendons can tear. Bones can fracture. Wounds can become infected. They can bleed. They can develop hypothermia or heat illness. They require sleep and calories even if the infection prevents normal behavior.

Most importantly, an infected person does not need to be dead to cease being a serious fast-moving threat. A severely dehydrated person may still be alive but incapable of sustained pursuit. The same is true of someone with a fractured ankle, substantial blood loss, severe infection, heat illness, or profound exhaustion.

The relevant population is therefore not the number of infected persons who remain biologically alive. It is the number who remain capable of finding, pursuing, and overpowering survivors.

The first generation of infected may be the most dangerous. A person infected at 9:00 a.m. on the first morning may have eaten breakfast, slept normally, consumed adequate water, and begun the day physically healthy. A person infected on Day 8 may have spent the preceding week hiding, walking, missing meals, drinking inadequately, sleeping poorly, and sustaining minor injuries. Infection does not restore those reserves. Later generations may therefore enter the infected population in progressively poorer physical condition.

This produces a powerful reason to wait.

Expect the Outbreak to Have a Peak

During the initial phase, the number of infected persons may rise extraordinarily quickly because each infected person encounters many susceptible people. Crowded workplaces, schools, hospitals, supermarkets, transit systems, evacuation centers, and traffic jams may accelerate transmission.

That situation eventually changes. Survivors disappear from public spaces. Doors are locked. Roads empty. Organized groups establish barriers. Authorities learn how the infection operates. Easily accessible victims become scarce. Meanwhile, existing infected persons continue becoming incapacitated.

Eventually the number of infected persons being removed through death or physical incapacity exceeds the number of newly infected persons. The dangerous infected population then begins to contract.

If, purely as a planning illustration, the physically capable infected population declined by half every three days after reaching its peak, approximately half would remain after three days, one quarter after six, one eighth after nine, roughly six percent after twelve, roughly three percent after fifteen, and less than one percent after approximately three weeks.

Actual rates cannot be predicted in advance. The important point is that declining populations can fall very rapidly. Waiting five additional days may therefore produce a much larger reduction in external danger than the household experiences in internal resource loss.

This is why stored supplies have unusual value during a rapidly declining outbreak. They purchase time.

Do Not Mistake the Initial Decline for Safety

The period immediately after the most visible collapse may remain exceptionally dangerous. Streets may become quiet because most uninfected people are hiding and many infected persons have moved elsewhere or become incapacitated. The infected persons who remain mobile may still be among the physically strongest. They may travel farther in response to isolated sounds or movement because easily accessible victims have disappeared.

At the same time, other survivors may begin emerging because they also believe the emergency is ending. Supply locations may suddenly attract people. Fires, alarms, emergency vehicles, generators, and government operations may attract additional movement.

For planning purposes, treat the first apparent quiet period as a possible extinction burst rather than proof of safety. Continue observing. A single hour without visible infected persons does not establish that a neighborhood is clear.

Use a Three-Level Resource Status

Households can simplify daily decisions by assigning each essential resource a status.

GREEN means more than approximately 14 days remain. A household with green water, food, medication, and habitability should ordinarily remain sheltered. Do not conduct supply runs merely to increase an already adequate reserve.

YELLOW means approximately 7 to 14 days remain. Begin planning. Identify potential supply sources, alternate sources, possible routes, official distribution information, and conditions that would cause you to leave. Continue sheltering if outside danger remains high and appears to be declining.

RED means fewer than approximately 7 days remain. Resupply or relocation has become an active problem. Gather reliable information and prepare to act when the balance of risk is favorable. Do not interpret red status as an instruction to leave immediately. Five days of remaining resources may still justify waiting another day if external danger is falling rapidly.

Approximately three days of safe drinking water or medically critical supplies should normally be treated as an urgent threshold. At this point the household needs a workable resupply or relocation plan because an unsuccessful first attempt must not result immediately in exhaustion of the resource.

The shortest resource determines the household's overall status.

Conduct a Daily Stay-or-Go Assessment

At least once every 24 hours, determine the number of days remaining for drinking water, food, critical medication, and safe habitation. Then assess whether the residence itself remains physically secure.

If every essential category has more than 14 days remaining and the shelter is safe, remain inside.

If the shortest category has 7 to 14 days remaining, remain inside if conditions outside are dangerous or improving, but develop a resupply plan.

If the shortest category has fewer than 7 days remaining, begin active preparation for resupply or relocation and seek reliable information about the safest opportunity.

If the shortest category is approaching approximately 3 days, the margin for simply waiting is becoming small. Act before resources are completely exhausted unless reliable information strongly indicates that a short additional delay will substantially improve safety.

Leave sooner if the building is burning, structurally unsafe, contaminated, penetrated by infected persons, becoming dangerously hot or cold, or unable to support a medically vulnerable occupant.

This approach deliberately preserves a reserve. The first supply source may be inaccessible. The route may be blocked. A vehicle may fail. Supplies may already have been removed. The household must retain enough resources to return home and attempt another plan.

Do Not Solve a Future Shortage With a Present Danger

This is the most important decision rule in this guidance.

A household with 18 days of water does not have a water emergency because the water will eventually run out. A person with 12 days of food does not need to enter a supermarket today because food will eventually become scarce. A resident whose medication will last three weeks does not need to visit a pharmacy during the most violent phase of the outbreak simply because additional medication would be useful.

Every day safely spent inside converts stored resources into time. If the outside hazard is declining faster than the household's resources are approaching critical levels, waiting improves the household's overall survival position.

Consider a person with ten days of essential supplies who believes a supply trip today carries substantial danger. Waiting one day reduces the supply reserve to nine days. But if the active infected population also falls substantially during that day, the person's overall position may have improved. The same comparison should be repeated the following day.

The purpose is not to wait as long as physically possible. It is to move the unavoidable exposure as far as reasonably possible toward the period of lower external risk.

Rural, Suburban, and Urban Guidance

Rural residents generally begin with the strongest position. Low population density reduces the likely number of infected persons, while wells, septic systems, stored food, independent heating, agricultural supplies, and detached buildings can provide considerable self-sufficiency. Rural households with adequate resources should be particularly reluctant to travel into towns for nonessential supplies. A trip to a supermarket or fuel station exchanges a low-density environment for a location where people and infected persons may concentrate.

Suburban residents are also generally well positioned to shelter. Detached houses provide substantial physical separation and often contain garages, basements, water heaters, food storage, multiple exits, and outdoor space. Do not create unnecessary neighborhood gatherings during the acute phase. Communicate remotely or at a distance when possible. A secure suburban house with adequate supplies is normally preferable to a theoretically safer rural destination that requires travel through populated roads.

Urban residents face the shortest average infrastructure runway but should not assume this makes immediate evacuation preferable. During the first hours and days, streets, stairwells, lobbies, transit stations, bridges, tunnels, highways, hospitals, and stores may represent the highest-risk environments. An apartment several floors above street level may provide excellent temporary protection. Store water immediately, understand the building's emergency exits, avoid dependence on elevators, and determine how long water, temperature, sanitation, and medication can remain viable without normal utilities.

Urban residents should relocate when the building is becoming unsafe, not simply because the city outside appears frightening.

Supply Runs Should Have a Defined Purpose

When a supply run finally becomes necessary, identify the exact resource that requires replenishment and obtain enough of it to materially extend the shelter runway. Avoid browsing or collecting nonessential goods.

A successful trip that provides only two additional days of supplies may expose the household to almost as much danger as one that provides two weeks. Repeated trips compound exposure. Even if an individual trip appears likely to succeed, repeatedly entering a hazardous environment progressively reduces the probability that every trip will end safely.

Do not assume that supermarkets are automatically the best destination. Depending on circumstances, an official distribution point, known nearby residence, workplace, community facility, or other identified source may provide needed resources with less travel and less human contact. Follow reliable government instructions when organized distribution becomes available.

Before leaving, retain enough resources to survive a failed attempt. Never construct a plan that requires the first destination to be accessible.

Final Guidance

The purpose of sheltering during a fast-moving infected outbreak is not to hide indefinitely. It is to allow two clocks to run simultaneously.

Inside the shelter, water, food, medicine, temperature, and sanitation determine how long occupants can remain safely isolated. These resources should be counted, converted into days, conserved intelligently, and reassessed every day.

Outside the shelter, infected persons are also operating on a clock. If they remain biologically human, they are consuming water, calories, physical reserves, body temperature, and functional mobility while accumulating injuries and exposure. Their population may initially grow explosively, reach a peak, and then decline as new infections become less frequent and existing infected persons become incapacitated.

Your objective is to make the first clock run more slowly than the second.

Maintain safe drinking water. Count calories rather than meals. Inventory medication before it becomes scarce. Treat power failure according to its consequences rather than the inconvenience it causes. Preserve a reserve for failed plans. Avoid repeated exposure. Do not leave because you are frightened, bored, hungry, curious, or uncomfortable.

Leave when an essential resource or the shelter itself is approaching a genuine safety limit and the risk of remaining has become greater than the risk of moving.

Until that point, every day you remain safely sheltered is another day in which you have conserved your physical resources while the outbreak has consumed its own.

In a fast-moving outbreak involving biologically living infected persons, that difference may be the principal survival advantage available to you.

---

And that's it. Stay put, and consume resources. I'll end with an analysis of someone in a worst case scenario staying put versus someone in a better position foraging for supplies:

Case Study 1: The Underprepared Urban Resident

A 25-year-old woman works for an advertising firm in a major American city. She reaches her apartment shortly before the outbreak reaches its most violent phase. She lives alone several floors above street level and has made essentially no preparations for an emergency. Her refrigerator is nearly empty, and after searching the apartment she estimates that snacks, condiments, and miscellaneous pantry items contain only about 3,000 calories. She has no medically essential prescriptions. Water service is still functioning when she arrives, so she immediately fills every clean container she can find, obtaining approximately 20 to 25 liters of drinking water, and fills her bathtub for sanitation and possible emergency treatment. She locks the door and decides not to leave unless remaining in the apartment becomes genuinely dangerous.

Despite her poor preparation, her immediate survival prospects are good. Her estimated probability of surviving the first 24 hours is approximately 98 percent, falling to about 95 percent after three days and 90 percent after one week. These figures may seem surprisingly high given her lack of food, but food is not her immediate survival constraint. She will consume her 3,000 calories quickly and then begin fasting, but an otherwise healthy adult with adequate water does not ordinarily die after several days without food. Hunger, weakness, poor concentration, and loss of physical capacity will become progressively important, but they develop much more slowly than the consequences of severe dehydration, traumatic injury, or infection. During the period when the streets are most dangerous, she is hungry but protected by a locked apartment.

Water therefore determines her first real deadline. If she has obtained approximately 21 liters of safe drinking water, she has roughly seven days at an allocation of three liters per day. She may have additional liquids elsewhere in the apartment, and her bathtub supply may preserve potable water by covering sanitation or potentially provide additional drinking water if it can be made safe. Nevertheless, she should not attempt to extend her shelter period by becoming severely dehydrated. By approximately Day 5 or 6, she should be gathering whatever reliable information remains available and identifying possible sources of water, even though she continues to stay inside.

Her estimated survival probability is approximately 84 percent at Day 10 and 76 percent at Day 14. Much of this decline reflects the likelihood that she will eventually have to interact with the outside environment. If she makes a carefully planned water and food run around Day 8, after the most explosive period of transmission has passed, the probability of returning alive and uninfected might reasonably be modeled at approximately 85 to 90 percent under the assumptions used in this guide. The same trip during the first 24 hours might have had only a 40 to 60 percent probability of success. Waiting has therefore exchanged several days of hunger and consumed water for a potentially enormous reduction in exposure risk.

If she successfully obtains water and food or reaches an organized distribution point, her position improves considerably. If she does not, prolonged fasting, sanitation problems, dehydration, building conditions, and declining physical strength progressively increase her risk. Under the severe outbreak assumptions used here, her cumulative probability of being alive at three weeks is approximately 69 percent and at one month approximately 62 percent. These figures would improve substantially if she discovered even a modest additional supply of food or potable water. Conversely, they would deteriorate rapidly if water became unavailable earlier than expected.

The important feature of this case is that her survival probability declines relatively slowly during the most violent part of the outbreak. She is objectively poorly prepared, but almost none of the danger outside can reach her while she remains behind a secure door. If she instead panics on the first day because her refrigerator is empty and goes looking for groceries, she exchanges a future nutritional problem for an immediate infection and injury problem at precisely the worst possible time.

Her behavior demonstrates the central principle of this guidance. An individual does not need enough supplies to survive indefinitely for sheltering to be worthwhile. She needs enough resources to outlast the period in which outside exposure is most dangerous. Even a badly underprepared person may have enough water and stored body energy to accomplish that. Her empty refrigerator is a serious problem, but it is a problem that develops over days and weeks. The outbreak outside is capable of killing her in minutes. By recognizing the difference, she gives herself a substantially better chance of surviving both.

Case Study 2: The Well-Prepared Suburban Resident

A father of three lives with his family in a detached suburban home. He is physically fit, an experienced outdoorsman, owns more than 50 firearms, is highly proficient with them, and has extensive camping and emergency equipment. His heavily modified four-wheel-drive truck has recovery equipment, additional carrying capacity, and excellent off-road capability. His refrigerator, freezer, and pantry contain approximately 10 to 14 days of ordinary household food, water service is still functioning, and his home contains the tools and supplies expected in a well-equipped suburban household. Two capable friends live nearby. In almost every conventional measure of emergency preparedness, he begins the outbreak in an excellent position.

During the first day, however, he decides that supplies will soon disappear and that he should obtain additional food, fuel, water, and medicine while stores remain accessible. He contacts his two friends, loads the truck, and the three men leave heavily armed for a nearby commercial district. At the moment he leaves his driveway, his probability of surviving is obviously 100 percent. Within three hours, under the severe early-outbreak assumptions used in this guide, his estimated probability of still being alive falls to approximately 90 percent, while the probability that the mission has produced no infection or serious injury is only about 72 percent. By six hours, his personal survival probability is approximately 82 percent and the probability of an entirely clean mission approximately 55 percent. His probability of returning home alive within roughly 12 hours is approximately 76 percent, while the probability that all three men complete the mission without infection, serious injury, separation, vehicle loss, or another major failure is only about 40 to 45 percent.

The infected are only part of the problem. The group must successfully navigate disrupted roads, abandoned or crashed vehicles, frightened civilians, fires, police activity, crowds, and unpredictable conditions at whatever supply location they select. Commercial areas containing food, medicine, fuel, and water are precisely the locations where other survivors are most likely to converge. Many of those survivors may also be armed. Three heavily armed men arriving together in a modified truck know that they are responsible citizens trying to protect their families; a frightened store owner, police officer, homeowner, security guard, or another armed group does not know that. Both sides may have only seconds to interpret the other's intentions. A lethal confrontation can therefore occur without either party having originally intended to harm anyone.

For purposes of this scenario, roughly one-third of the serious mission danger can be attributed primarily to infected encounters, approximately another third to encounters with other people and mistaken threat identification, and the remainder to transportation failures, accidents, separation, fires, blocked routes, and related hazards. These categories overlap and should not be treated as independent probabilities. A blocked road may force the group into an infected crowd; gunfire during an infected encounter may attract other people; an armed confrontation may disable the vehicle or separate the group.

His weapons significantly improve his chances in certain encounters but cannot eliminate the need to have those encounters. The same is true of the truck. Four-wheel drive and recovery equipment are extremely valuable when terrain is the limiting problem. They provide much less advantage when twenty abandoned vehicles block an intersection or when a commercial parking lot contains frightened civilians and infected persons. Equipment reduces particular risks. It does not make an unnecessary exposure necessary.

The consequences continue even if the father survives the trip. His estimated probability of being alive after the first 24 hours is approximately 72 percent, falling to about 65 percent at three days, 60 percent at one week, 56 percent at two weeks, and approximately 51 percent at one month under this scenario. A wound, uncertain bodily-fluid exposure, lost vehicle, injured companion, or infected friend can continue affecting the household long after the initial trip. Returning home after an unrecognized exposure also creates a new danger for the wife and three children who had previously been isolated from the outbreak.

The appropriate comparison is not with the underprepared urban resident but with what happens if this same man uses his preparedness differently. If he remains home on Day 1, fills water containers, secures the house, inventories food and medication, monitors conditions, and uses his equipment to maintain the shelter rather than immediately venturing outside, his estimated personal survival probability is approximately 98 percent after 24 hours, 96 percent after three days, 93 percent after one week, 88 percent after two weeks, and roughly 80 to 85 percent after one month. His preparations have given him one of the strongest starting positions available to an ordinary civilian.

Waiting does not make his equipment irrelevant. It makes that equipment more valuable. If dwindling resources eventually require a supply run on Day 7 or Day 10, he remains fit, armed, mobile, experienced, and equipped with an unusually capable vehicle. But he may now be operating in an environment containing far fewer active infected persons, fewer panicked civilians simultaneously competing for supplies, less traffic, and substantially more information about which locations and routes are safe. A mission with only about a 40 to 45 percent probability of completely clean success during the opening phase might plausibly become an 80 to 90 percent proposition after the acute phase has substantially declined.

This case illustrates a less obvious danger of preparedness: equipment can create confidence that encourages unnecessary exposure. The father's firearms, truck, outdoor experience, and physical fitness genuinely improve his survival prospects, but their greatest initial value is that they allow him to remain safely at home without needing outside assistance. When he interprets those advantages as reasons to enter the outbreak, he voluntarily gives away much of the protection they provided.

Preparedness should increase a person's ability to avoid risk, not increase his willingness to accept it. Had this father remained home, he would have begun the outbreak with substantially better survival prospects than the underprepared urban resident. By conducting an unnecessary supply run during the most dangerous phase, he can temporarily make himself less likely to survive than she is. His mistake is not being armed, owning a capable vehicle, or preparing for emergencies. His mistake is using those resources to solve a problem that has not yet become urgent.

Starcraft Co. 22- Return to Moria

By the time StarCraft Co. returned to Moria, the emergency command no longer resembled the improvised coalition that had formed after Citadel. Months of constant fighting had turned it into something approaching a real military. Surviving UIC fleets had been reorganized into functional commands rather than left attached to whatever bureaucratic structures happened to survive the Council. Independent planetary forces were folded into regional defense groups. Mercenary companies that accepted unified command were assigned standardized communications equipment, ammunition contracts and supply schedules. Officers were promoted based increasingly on battlefield performance rather than seniority. Units that had spent years guarding static installations were retrained for mobile warfare. StarCraft Co.'s intelligence network became the skeleton around which the entire force operated, feeding information from governors, scouts, captured renegade communications, Protoss contacts and civilian shipping into a single operational picture. It was still politically untidy. Some formations answered to StarCraft Co. enthusiastically, others grudgingly, and several regional commands made a point of reminding everyone that the arrangement was temporary. Militarily, however, the transformation was unmistakable. The Terran forces that had nearly disintegrated after Citadel were becoming organized, mutually supporting and increasingly lethal.

They were also losing a war of arithmetic. The renegades did not need to defeat StarCraft Co. decisively if they could continue replacing losses faster than the Terrans did. Zerg attacks were becoming larger rather than smaller. New broods appeared on worlds that had never previously reported infestations. Renegade commanders increasingly treated biological forces as expendable ammunition, throwing tens of thousands of organisms into defensive lines simply to force StarCraft Co. to spend shells, missiles, personnel and reactor hours destroying them. A Terran battlecruiser damaged by scourge might require months of repair. A dead veteran commando required years of training and augmentation to replace. A thousand dead zerglings required biomass. That imbalance had existed throughout the war, but the expanding renegade breeding network was making it strategically fatal. StarCraft Co. could improve tactics indefinitely and still lose if every victory merely exchanged irreplaceable Terran resources for organisms the enemy could regrow.

Moria sat at the center of the problem. The world StarCraft Co. had once been paid to evacuate had not been abandoned after the fall of the UIC leadership. The renegades understood its value better than the Council ever had. Moria's enormous open-pit mines, mineral seams and vespene deposits had survived the original invasion largely intact, and the same industrial infrastructure the UIC had sacrificed millions to preserve was now serving the enemy. Renegade mining teams operated restored excavators beneath Zerg protection. Drones harvested exposed mineral fields in areas too dangerous for Terran workers. Captured processing facilities refined strategic metals for armor, reactors and starship construction. Intelligence indicated that entire shipments left Moria every week for renegade shipyards and brood worlds. The enemy had effectively converted one of the richest planets in Terran space into a combined mine, breeding ground and logistics depot.

Some inside the emergency government objected when StarCraft Co. proposed retaking it. Moria had become politically toxic. The old Council's decision to protect its wealth while abandoning other worlds remained one of the clearest symbols of its corruption. Returning with a large military force, then reopening the mines under StarCraft Co. administration, would be easy to portray as proof that nothing had changed except who collected the revenue. The commander rejected that reasoning immediately. If they left Moria because they were afraid of how it looked, the renegades would keep the minerals, build more ships, breed more Zerg and eventually kill people who had never cared who owned a mine. When an aide pointed out that the operation would inevitably make StarCraft Co. extraordinarily wealthy, the commander agreed without embarrassment and added that they intended to spend that wealth on the war. Moria was not a prize. It was an enemy ammunition dump that happened to be buried under a planet.

That distinction became formal policy before the first ship departed. Mineral revenue from the campaign would be placed into a dedicated war account, audited by representatives from multiple Terran governments and used for fleet expansion, reconstruction and military supply. StarCraft Co. would administer the operation because it possessed the machinery to do so, but it would not claim Moria as corporate property. More importantly, the commander made clear that the resources would not be reserved exclusively for Terran forces. If the war was going to end with a genuine offensive into renegade space, StarCraft Co. would need every serious ally it possessed operating at full strength, and that included the Ara.

The strategic case was stronger than the political objections anyway. Destroying the renegade presence on Moria would accomplish three things simultaneously: remove one of their largest resource sources, eliminate a major Zerg breeding complex and give the Terran coalition enough material to expand rather than merely replace losses. Without that expansion, there could be no final offensive. StarCraft Co. could hold territory indefinitely and eventually die doing it. To end the war, the balance of production had to change, and Moria was the first place where it could be changed dramatically enough to matter.

There would be no subtlety to the invasion. Reconnaissance identified two enormous renegade military-industrial complexes and more than thirty major Zerg hive concentrations spread across the mineral-rich hemisphere, with dozens of smaller nests between them. The terrain remained the same nightmare it had been during the evacuation: strip mines kilometers across, artificial ravines carved by generations of excavation, abandoned industrial pits, fractured mountain ranges and deep canyons where sensors performed poorly. The renegades had used those features intelligently. Missile batteries occupied high ridges. Siege tanks controlled major transit corridors. Zerg colonies filled abandoned pits where creep could spread unseen beneath overhangs. Hidden spires produced mutalisks and scourge from locations too dispersed to eliminate with one orbital strike.

StarCraft Co. chose not to begin with the mines. The first commando landings went into the ravines. Dropships entered during a planet-wide electrical storm deliberately chosen because the atmospheric interference made conventional navigation miserable. StarCraft Co. navigators flew terrain-following routes using inertial maps compiled from old mining surveys rather than active sensors. Several craft passed within kilometers of renegade detection stations without appearing as anything more than transient weather artifacts. They deposited commando companies deep inside canyon systems surrounding the intended landing region. The commandos did not attack immediately. For almost six hours they moved through abandoned service tunnels, collapsed excavation galleries and drainage culverts left behind by mining operations decades earlier, planting passive sensors and marking Zerg positions without transmitting anything.

When the attack finally began, the orbital fleet did not fire at the hive itself. Battlecruisers struck the canyon mouths around it, collapsing two major exits and burying a third beneath thousands of tons of rock. The commandos attacked through the remaining routes at the same moment. Zerg organisms surged toward the only open approaches and compressed themselves into firing lanes selected hours earlier. Remote demolition charges brought down ledges behind the first waves, separating them from reinforcements. Fireteams armed with heavier versions of the company's Gauss weapons killed hydralisks from elevated shelves while grenades and flamethrowers shredded zerglings below. The operation was less an assault than engineered extermination, and by the time the hive understood that its escape routes had become kill zones, StarCraft Co. dropships were already descending into the cleared basin.

The first base went up in twelve hours. SCVs erected prefabricated bunkers before permanent structures. Siege tanks were dropped directly onto reinforced platforms assembled from mining equipment. Goliaths formed an air-defense ring. Science vessels hovered above the perimeter using continuous detection sweeps rather than waiting for suspected burrowing. Instead of constructing one large fortified base, StarCraft Co. built dozens of smaller hardened nodes linked by armored supply routes. Each possessed enough firepower to survive temporary isolation. Command posts were buried beneath old mining infrastructure wherever possible. Fuel, ammunition and medical supplies were distributed between multiple depots so that a single Zerg strike could not cripple the entire campaign, and within days the first mining crews were operating behind the expanding perimeter.

That pattern defined the campaign. Clear a hive, fortify the ground, reopen the mineral fields and use the extracted resources to support the next advance. The commander called it incrementalism. Some officers called it eating Moria one bite at a time. Either description was accurate. StarCraft Co. had no intention of launching a grand offensive across half a continent and hoping its supply lines survived. Every kilometer taken became part of the machine supporting the next kilometer. The first mineral pit reopened five days after landing. Automated excavators were repaired by SCVs while combat engineers inspected processing equipment for sabotage. The first shipments did not leave the planet. They went directly into local fabrication. Damaged Goliath components were recast. Bunker plating was manufactured on site. Siege-tank ammunition came off restored production lines. Prefabricated turrets began appearing along supply corridors faster than the renegades could destroy them. Moria's value became visible almost immediately: each captured mine reduced the amount of war matériel that had to be transported from somewhere else.

The Zerg fought every expansion. Hive clusters occupied terrain that would have been almost impossible for conventional infantry to assault directly, so StarCraft Co. increasingly stopped assaulting them directly. Siege tanks established firing positions beyond biological defense range while science vessels painted targets through terrain scans. Rather than bombard a colony continuously, tanks fired in timed sequences designed to provoke Zerg counterattacks. When the organisms charged, the tanks withdrew behind prepared chokepoints where Goliaths, bunkers and commandos were waiting. Once the defenders had exhausted themselves against those positions, the artillery moved forward again. Several hives were dismantled over days without StarCraft Co. ever attempting a single decisive assault.

A new tactic emerged around the largest ravines. Engineers installed enormous retractable blast gates originally designed to isolate mine collapses. Zerg swarms were deliberately allowed to enter the canyons before the gates closed behind them. Siege tanks positioned on upper terraces then fired downward while commandos blocked side passages. The first time it worked, nearly four thousand organisms entered a mining corridor expecting to overwhelm an apparently retreating Terran force. Fewer than a hundred reached the far end. The gates reopened after the artillery stopped, SCVs pushed the bodies aside with industrial loaders, and the same trap was used again three days later. The tactic was so effective that the renegades eventually began sacrificing drones simply to test whether a canyon had been prepared as a kill box before committing real forces.

They adapted elsewhere as well, particularly in the air. Moria contained more spires than reconnaissance had identified, many concealed inside abandoned excavation shafts or deep mountain valleys. Mutalisk attacks became almost continuous. They struck convoys, isolated SCV teams and artillery positions. Scourge waited until transports or science vessels committed to an operation and then appeared from directions nobody had expected. Destroy one rookery and another seemed to become active fifty kilometers away. StarCraft Co. responded by turning its supply network into bait. Convoys began moving with intentionally visible signatures. Some carried cargo. Others carried nothing but armor plating, automated turrets and tracking beacons. Mutalisks attacking a convoy frequently discovered that the trucks beneath them were empty and that cloaked Wraiths had been following several kilometers behind. Valkyries would then descend from altitude while the Wraiths attacked from below, and science vessels irradiated the densest surviving formations. The first successful ambush destroyed almost an entire mutalisk flock. After that, the Zerg became more cautious, which accomplished almost as much as killing them.

The scourge required another solution. Science vessels were too valuable to risk repeatedly as bait, so StarCraft Co. modified old mining drones into false aerial targets carrying reactor signatures that resembled small support ships. They were cheap, ugly and barely controllable, but scourge did not care. Entire clusters detonated against unmanned machinery before Valkyries swept through the organisms following behind them. The drones became known as “candles” among the pilots because, as one Valkyrie commander put it, you lit one before somebody died. The joke spread quickly, but the tactic survived because it worked.

The commandos were used differently than at Callisto's Reach. They were too valuable to waste holding ordinary ground. Instead they became the connective tissue protecting the campaign's vulnerable points. When a convoy vanished from sensors, commandos arrived by dropship. When a spire appeared behind the line, commandos hunted it. When renegade infiltrators cut a rail connection, commandos followed them into the mountains. Their enhancements allowed units to operate for days away from the main force with minimal support, and their mobility made them one of the few assets capable of responding before a localized problem became a strategic one. Medics increasingly deployed with them on missions that had little resemblance to conventional battlefield medicine. One such operation began after researchers discovered that overlord coordination could be degraded without killing the organism outright. Modified aerosol compounds designed to damage exposed sensory tissue were dispersed along known flight paths while commandos infiltrated beneath the creatures under cloaked Wraith cover. Blinded overlords drifted unpredictably, disrupting local Zerg coordination long enough for Wraiths to eliminate the remaining functional overseers and withdraw before mutalisks could concentrate. It was unpleasant, unreliable and extraordinarily effective in the right terrain.

The first renegade base fell during the second month. It occupied an enormous mining complex built into the side of a terraced pit, protected by siege tanks on multiple elevations, bunkers dug into old processing buildings and enough missile turrets to make a conventional air assault extremely expensive. StarCraft Co. spent almost a week appearing to prepare exactly that assault. Wraith patrols probed the air defenses. Battlecruisers moved into visible orbital positions. Artillery concentrations formed on the eastern approaches. Renegade commanders responded rationally, shifting tanks toward the expected ground corridors and reinforcing anti-air positions around the central facility. The actual attack came from below.

Old geological records showed that the original mining operation had bored horizontal extraction tunnels beneath the base decades earlier before abandoning them when the mineral seam changed direction. Most had collapsed. One had not. SCVs spent four days quietly enlarging it while siege operations above provided enough vibration to conceal the work. Commandos entered first, followed by infantry and compact engineering teams. Instead of emerging outside the defenses, they surfaced inside a disused refinery building less than five hundred meters from the renegade command center. The first explosion destroyed the communications array and the second killed the backup generator. The commandos immediately attacked outward rather than deeper into the facility. Tanks on the perimeter discovered that their guns were pointed away from the enemy. Bunkers designed to fire into the mine approaches had almost no visibility toward their own rear. The renegades attempted to turn their defenses inward just as StarCraft Co.'s apparent diversion became real. Siege tanks on the eastern ridge opened fire, battlecruisers descended into atmospheric support range and Valkyries struck the Wraith squadrons trying to lift from the base. The entire complex went from prepared defense to simultaneous attack from two directions in less than three minutes.

The renegades fought hard. Their infantry understood that there was nowhere useful to retreat. Several tanks managed to undeploy and fire directly into their own industrial district to stop the commandos. Goliaths formed improvised barriers across internal roads. A counterattack briefly isolated one commando platoon inside a smelting facility, forcing them to fight room by room until relief arrived. None of it changed the larger situation. StarCraft Co. had concentrated overwhelming force at the exact moment the base's defenses were least capable of responding to it. The command center fell after ninety minutes and organized resistance ended before nightfall. Engineers arrived before most of the wounded had been evacuated, and the processing lines restarted six days later.

The second renegade base learned from the first. Its commanders collapsed every abandoned tunnel beneath their position, moved command facilities into hardened bunkers and established overlapping patrols far beyond the perimeter. They also concentrated much of Moria's remaining air power around the complex. StarCraft Co. did not attempt to repeat itself. Instead it isolated the base for nearly three weeks. Every surrounding hive cluster was eliminated first. Every mineral route was cut. Wraiths destroyed couriers. Battlecruisers struck fuel depots whenever they appeared. Science vessels irradiated Zerg formations attempting to reinforce the position. One road was deliberately left open, and the renegades eventually began moving supplies through it at night under heavy escort.

StarCraft Co. attacked some of those convoys and allowed others through. After several days, the defenders concluded that the route was dangerous but viable and committed more resources to protecting it. Then StarCraft Co. stopped attacking the convoys entirely. The reason became apparent when the final supply column entered the base carrying fuel containers that had been quietly replaced several hundred kilometers away. Commandos had intercepted the convoy, killed its escort without allowing a distress transmission and substituted containers fitted with tracking devices and shaped charges. The vehicles arrived normally. Crews moved them into underground storage. StarCraft Co. waited until reconnaissance confirmed that the fuel had been distributed through the depot complex, then detonated the charges.

The base did not explode spectacularly. That was not the objective. Fires spread through multiple storage areas simultaneously. Suppression systems failed. Power was rerouted. Emergency crews abandoned defensive positions. Wraith pilots scrambled before refueling operations became impossible. At precisely that moment, StarCraft Co. attacked from every direction. Siege tanks opened against the outer defenses. Commandos struck the command bunkers. Battlecruisers bombarded artillery positions. Valkyries intercepted the Wraiths climbing through smoke. Science vessels placed defensive matrices over the first Goliath formations crossing the perimeter. The renegades had built a fortress designed to resist siege. StarCraft Co. attacked while the fortress was fighting itself. It lasted longer than the first base, but it did not survive the day.

After that, organized renegade resistance on Moria began collapsing. Individual units continued fighting. Zerg hives remained active across remote regions. Hidden spires still generated fliers. But there was no longer a central force capable of coordinating the planet's defense. StarCraft Co.'s network of forward bases expanded steadily across the mineral hemisphere. Every captured field became a depot. Every reopened refinery supplied the offensive. Rail lines were repaired behind the troops. Air-defense corridors linked the mines. Science vessels mapped remaining creep concentrations while commandos hunted brood-control installations.

The campaign lasted months because StarCraft Co. refused to confuse speed with progress. There were setbacks. A scourge attack destroyed three transports in a single afternoon. One forward base was overrun after an underground Zerg tunnel emerged inside the perimeter, forcing a temporary evacuation and orbital bombardment. A mutalisk swarm found an inadequately protected rail hub and killed hundreds of workers before Valkyries arrived. A renegade guerrilla force hid inside abandoned mining settlements for weeks and repeatedly attacked extraction crews until commandos finally cornered it. Moria extracted payment for every assumption, but the direction never reversed. By the fourth month StarCraft Co. controlled most major mineral fields. By the fifth, the remaining Zerg colonies had been divided into isolated pockets. By the sixth, the last significant spire complex was discovered beneath an abandoned mountain-processing facility and destroyed after a three-day air battle. Mutalisk attacks diminished from constant to occasional, then stopped. Reconnaissance teams continued finding individual nests for weeks afterward, but they were no longer part of a planetary defense system.

Once the major fighting ended, StarCraft Co. made the decision that generated almost as much controversy as the invasion itself. Ara representatives were invited to Moria and offered access to designated mineral fields and vespene deposits under the same broad wartime framework governing Terran extraction. They would provide their own workers, security and transport. StarCraft Co. would retain control of the overall planetary defense network and guarantee access to the designated zones. In return, the Ara would commit the material directly to restoration and expansion of their fleet for the coming offensive. StarCraft Co. was not gifting them Moria and was not transferring ownership of Terran territory. It was purchasing future military power with resources that were currently sitting in the ground.

The reaction was immediate. Several governors objected that Terrans had died retaking Moria only to watch Protoss mining ships descend onto it. Former UIC industrial interests accused StarCraft Co. of giving alien powers access to strategic resources. One admiral reportedly asked whether the commander intended to “finance a Protoss navy with Terran minerals.” The answer was yes, with one correction: StarCraft Co. intended to finance an allied Protoss navy with minerals that would otherwise sit unused while the war continued. The commander made the argument personally at an emergency council session. “We can leave those fields in the ground because the flag over them matters more to us than the war, or we can turn them into carriers, arbiters, dragoons and warships that arrive with us when we go after the renegades. I know which one I need.”

The Ara themselves were initially more cautious than their Terran critics expected. They did not want the arrangement interpreted as payment for loyalty, nor did they want to appear to be taking advantage of a weakened Terran government. Their leadership requested formal terms, defined extraction boundaries and explicit recognition that the mineral rights were temporary wartime concessions rather than territorial claims. StarCraft Co. agreed to all of it. The resulting accord was deliberately transactional. The Ara would mine defined sectors, retain the extracted resources and devote the overwhelming majority to fleet construction and war production. In exchange, they committed to deploy a major expeditionary force when StarCraft Co. began the final offensive. Neither side used the phrase publicly, but inside StarCraft Co. command the agreement quickly acquired a simpler name: the down payment.

The first Ara mining flotillas arrived within weeks. Their technology altered the landscape almost as dramatically as the Terran reclamation had. Protoss extraction systems operated differently from SCV-driven mining, and their support craft could work mineral seams StarCraft Co. considered inconvenient or uneconomical. Ara engineers established crystalline processing nodes beside Terran refineries. Terran Goliaths guarded Protoss workers from remnant Zerg organisms. Protoss Scouts patrolled air corridors alongside Valkyries. The arrangement was awkward, politically inflammatory and strategically excellent. Every transport leaving Moria carried either Terran war matériel or the raw material that would become Ara warships.

The numbers that followed were enormous. Mineral shipments began leaving the planet around the clock. Vespene production exceeded prewar projections because StarCraft Co. repaired wells the old UIC administration had considered uneconomical. Captured renegade stockpiles added to the total. The dedicated war account filled faster than procurement officers could initially spend it. New Wraith squadrons were ordered. Replacement Valkyries entered production. Minotaur construction accelerated. Commandos received new armor and weapons programs that had previously existed only on paper. UIC shipyards that had been operating below capacity because they lacked strategic materials returned to full production. At the same time, Ara construction yards began expanding carrier groups, replacing ships lost on Aiur and preparing vessels that had spent years in reserve because their tribe lacked the resources to modernize them.

StarCraft Co.'s own financial position improved enormously as well. That was unavoidable. It administered the mining contracts, provided much of the equipment and received payment for the military operation. Its treasurers reported balances that would once have seemed ridiculous for a mercenary company. The commander barely reacted. Every projection on his screen converted the money immediately into ships, ammunition, replacements, reactors, medical infrastructure, reserves and allied tonnage. Moria's purpose had never been to make StarCraft Co. rich. Wealth was simply what military capacity looked like before somebody turned it into weapons.

The effect on the renegades was the opposite. Their mineral shipments vanished. Ship construction slowed. Several brood worlds began competing for resources that Moria had previously supplied in abundance. Captured intelligence showed renegade commanders rationing replacement armor and delaying expansion of breeding facilities. Their Zerg numbers were still immense, but they were no longer growing at the same rate. For the first time in the war, the economic curve had begun bending in StarCraft Co.'s direction.

General Voss visited Moria shortly after the last major hive was destroyed. From the observation deck of a restored processing station, he could see mining machines crawling across a pit so large that the far wall disappeared into atmospheric haze. Terran transports lifted refined materials from loading pads while Valkyries patrolled overhead, and farther away an Ara mining vessel descended toward one of the sectors assigned under the new agreement. Voss watched it for several seconds before speaking. “This is what the Council wanted to save.” The commander replied that the Council had wanted to save it for themselves. Voss nodded toward the Protoss ship and asked whether giving part of it away made StarCraft Co. different. The commander corrected him. “We're not giving them anything. We're buying a fleet.”

“With Moria.”

“With part of Moria's production.”

Voss kept looking through the glass. “People are going to hate that distinction.”

“They can hate it while Ara carriers are killing renegade battlecruisers.”

That ended the argument more effectively than a policy paper would have.

For years the renegades had possessed an advantage StarCraft Co. could never completely overcome with tactics. They could lose more organisms, more equipment and more territory and still return with another army. Moria changed that. The Terran coalition now possessed secure resources, expanding industry and a military that was growing instead of merely surviving. Their most important Protoss ally was rebuilding at the same time. The renegades had lost the planet that had helped sustain their expansion and thousands of kilometers of breeding infrastructure with it.

When the commander returned to headquarters, a new strategic map was waiting for him. For months, most planning had revolved around defense: which worlds could be held, which attacks could be blunted, which supply routes had to remain open. That map was gone. Intelligence officers had replaced it with renegade territory, supply systems, brood worlds, fleet concentrations, command nodes and the routes leading inward. One of the senior officers remarked that they could finally afford the offensive. The commander studied the first cluster of systems between Moria and the renegade core and answered that they could afford to start it.

For the first time since the war began, StarCraft Co. was no longer asking how to survive the next enemy offensive. It was deciding where its own would begin.

Test post for Sturgis.nz

This review originally appeared at Grimdark Magazine on August 15, 2026.

Cormac Mac Art: Isle of Swords

By Matthew John – Titan Books – July 28, 2026

Review by Robin Marx

As Isle of Swords begins, Gaelic reaver Cormac Mac Art awakens on the shore of a corpse-strewn beach, greeted by the sound of his Danish comrade Wulfere (appropriately nicknamed the “Skull-splitter”) braining shipwrecked Saxons with a rock. The two are the only survivors of a raiding crew swept away along with their Saxon foemen by a rogue wave during a bloody boarding action. Upon realizing that they have washed up on their original destination, the Isle of Swords, rumored to house a lost trove of Roman gold guarded by hostile Pictish tribesfolk, the pair elect to press on with the search for the treasure despite the overwhelming odds against them. In addition to brutal Saxons and baleful Picts, before long Cormac and Wulfere encounter menacing sorcery and the uncanny influence of a tribal icon called the Dark Man.

Cormac Mac Art: Isle of Swords is part of Titan Books’ HEROIC LEGENDS line of digital short stories featuring the characters of Weird Tales veteran pulp author and Conan the Barbarian creator Robert E. Howard. While Conan himself has inevitably received the lion’s share of attention given his name recognition, HEROIC LEGENDS has also allowed modern authors to revive some of the lesser-known heroes from Howard’s body of work. Cormac Mac Art is one such character, having only appeared in a pair of finished stories and two further incomplete fragments, none of which were published during Howard’s lifetime. Indeed, Cormac Mac Art remains somewhat of a Howard “deep cut” character even today, with only a handful of pastiche fiction and comic appearances. Despite being the 24th installment in the line, Isle of Swords is the first HEROIC LEGENDS story dedicated to Cormac.

While this is (occasional Grimdark Magazine contributor) Matthew John’s first piece involving Cormac Mac Art, he is no stranger to the realms of Robert E. Howard and Sword & Sorcery fantasy in general. In addition to extensive work on Monolith Board Games’ Conan tabletop and roleplaying games, John has penned stories starring the barbarian for The Savage Sword of Conan. Readers familiar with his previous fiction, either through his Conan work or To Walk on Worlds, have a good idea of what to expect from Cormac Mac Art: Isle of Swords: muscular, kinetic prose and bone-crunching violence. John keeps the pace brisk and the bodies dropping. Unlike John’s previous work, however, the supernatural elements of the story are kept low-key; eerie, but with an air of plausible deniability about them. While readers accustomed to Conan and King Kull may miss the lack of fireworks and monsters, this restraint is wholly appropriate for Cormac Mac Art, whose original exploits as related by Howard (barring one) were grounded historical adventures. On the other hand, the true identity of the Dark Man is a fun Easter egg sure to be appreciated by fans of Howard’s more sorcery-infused stories.

Cormac Mac Art: Isle of Swords is a fast-paced and gritty adventure involving one of Robert E. Howard’s more underutilized characters. Readers in the mood for monsters and magical mayhem are better directed to other entries in the HEROIC LEGENDS line, but grimdark fans in particular are likely to appreciate the mud-caked melees and dirty tactics Matthew John delivers.

#ReviewArchive #BookReview #Fantasy #SwordAndSorcery #HeroicLegends #CormacMacArt #CormacMacArtIsleOfSwords #MatthewJohn #GrimdarkMagazine #GdM

Describo todo lo que puedo percibir, intento ordenarlo, darle un lugar, allá en el mundo y en mí: letanías, hombres robustos con camisas blancas, formas redondas de color azul, deformaciones, palabras que fueron pronunciadas de forma diferente, nuevo gris del cielo. Describí a las personas del bus de las 7.00 AM: diecisiete mujeres, trece hombres, dos niñas, cada uno con sus gestos, sus zapatos. La esquina de la casa rosa con bugambilias donde hay un perro con un juguete de color rojo en el hocico. El señor de la tienda que barre la acera y usa un gorro ridículo de navidad en agosto. Quise incluir recuerdos o ideas del pasado pero no hay memoria, al final opté por describir y hablar sobre las ventanas, de cómo se crearon para ver.

En la noche describí mi cuerpo, veinte dedos, lunar en la espalda, orejas un poco rojas, ojos aún oscuros, cabello un poco más largo, los dolores habituales y las mismas cicatrices. Soy yo. Conté los libros y están dispuestos: blanco, blanco, café, rojo, azul, blanco, negro. Suena una olla en el fogón, un par de televisores y ambulancias. El olor terroso de la cúrcuma se acentúa con el calor y la luna llena.

La imagen se presenta como una alucinación, natural y santa. Los cuerpos, incluso los inertes, son límites inquebrantables. Solo los insectos tienen hambre y beben fruta podrida durante el verano. Los sonidos se enredan a mis ruidos biológicos y no logro conocer sus orígenes. Las nubes caen, no se deslizan. ¿cómo hablar acerca del rumor de esta hora? Todo se arrastra.

No existe forma en la que pueda entrar. No existe forma en la que pueda memorizar o cuidar. El cuerpo inútil. El cuerpo incapaz. El cuerpo desbordado. Susurro y anoto lo ínfimo, cada detalle, sea alucinación o no, sea dolor o no, me pertenezca o no. Este registro descriptivo me permite reconocer las simulaciones, los objetos puestos y los vaticinios que susurra el enfermo desde la casa del frente. Escribí sobre el jarrón de barro que alguien puso a mitad de la cama y contenía todos los ríos con sus millones de muertos; las estrepitosas corrientes de agua por tres largas noches. Escribí también sobre los días de lluvia y sobre una mujer que caminaba un sábado en la tarde.

La mesa vieja que sostiene el plato de lentejas humeante a la altura de mi ojos es mi vínculo con lo real. Yo sé que no eres real y solo has llegado para servirme el café con su cuncho maldito en donde leerás mi mala suerte. Yo sé que no eres real, pero estás desenterrando mis árboles. Yo sé que no eres real y vienes a dormir conmigo.

The hillside above Adavivaram has been stripped to red earth and cut into terraces, a staircase of raw laterite climbing away from the coast. Reuters journalists who walked the site in early August found work proceeding at full pace, earthmovers reshaping a slope that until recently was green. Below the cut, roughly 120 metres away according to the Human Rights Forum, sits the Mudasarlova reservoir, one of the water bodies that keeps Visakhapatnam's taps running. Within a kilometre in the other direction lies the Kambalakonda Wildlife Sanctuary, home to leopards and pangolins, and, in the assessment Reuters reported, only 860 metres from the construction site itself.

In the city below, activists and children have marched with banners reading “We cannot drink DATA”, some painting handcuffs on to the Google logo. On the Sunday before the Reuters visit, campaigners met to plan door-to-door awareness drives and beach protests. It is not the reception a 15 billion dollar investment usually gets.

This is Google's largest AI infrastructure project outside the United States: a gigawatt-scale campus, built with the Adani Group and Bharti Airtel, announced in October 2025 and intended to make Visakhapatnam a landing point for subsea cables and a node in the global machinery of artificial intelligence. Andhra Pradesh's chief minister, Nara Chandrababu Naidu, laid the foundation stone in April 2026, targeting completion by September 2028. The state calls it historic and transformational.

It is also being built in a city that does not have enough water. By the state's own accounting, cited by Reuters, Visakhapatnam receives about 410 million litres a day against a requirement of 480 million. Rationing is routine for a population of roughly 2.5 million. Mongabay India reported that Visakhapatnam district holds the lowest volume of available groundwater of any district in Andhra Pradesh, 2.12 thousand million cubic feet as of 1 April 2026. Into this basin, the state has promised the project guaranteed water for twenty years.

The question that raises is not simply whether Visakhapatnam can spare the water. It is a question about the shape of the AI economy: what it means that the physical substrate of a technology consumed overwhelmingly in wealthy countries is being poured, literally, into the ground of places that cannot afford it, and what anyone in those places is entitled to demand in return.

Why Andhra Said Yes

Start with the strongest possible version of the case for building it.

India is not a bystander in the AI economy. Mongabay India reported that the country hosts something like 20 per cent of the world's data while holding around 3 per cent of global data centre capacity. That asymmetry is not neutral. Indian data sits on foreign soil, under foreign jurisdiction, and the value generated by processing it accrues elsewhere. Every argument European governments have made for digital sovereignty applies to India with more force, because India has more to lose.

Andhra Pradesh wants to change that, pursuing roughly 6.5 gigawatts of compute capacity. India's total stood at about 1.5 gigawatts at the end of 2025, up from around 375 megawatts in 2020, with Deloitte forecasting 8 to 10 gigawatts by 2030. Visakhapatnam, with its coastline, port, subsea cable potential and engineering colleges, is the obvious place for a large slice of it.

The economics offered are considerable. State officials have put job creation at up to 188,000 across the project's ecosystem. Google has committed to new transmission lines, clean energy generation and storage, and says it is building its own renewable generation without state or central incentives. The Tribune reported the allotment of 480 acres across Visakhapatnam and Anakapalli districts. Land has been discounted, stamp duty waived, electricity and water tariffs reduced and tax reimbursed during construction, a package the News Minute totalled at around 22,000 crore rupees.

Then there is the moral argument, which deserves to be taken seriously rather than waved away. Western commentators objecting to a data centre in India are objecting to infrastructure of a kind their own countries have built freely for twenty years. Northern Virginia hosts more capacity than most nations; Ireland's grid has been reshaped around it. To insist the footprint is acceptable in Loudoun County but not in Anakapalli requires justification, and “we got there first” is not one. Refusing the Global South the compute the Global North takes for granted, in the name of protecting it, entrenches precisely the dependency that sovereign AI programmes exist to break.

So the case is real. The problem is that almost none of it survives contact with the specifics.

The Arithmetic of Thirst

Water numbers in the data centre debate are unusually slippery, and the slipperiness is not accidental.

The first distinction is between withdrawal and consumption. A facility that withdraws a million litres, passes it through a heat exchanger and returns it a few degrees warmer has consumed almost nothing, though it has still altered the river. A facility that evaporates the same million litres through a cooling tower has consumed all of it. The water is not destroyed, but it has left the basin, and for the people downstream that is the only definition of loss that counts. Headline figures routinely conflate the two.

The second distinction is between on-site and off-site water: what the cooling system uses, versus what was consumed generating the electricity the facility draws. For most of the world's grids, the second dwarfs the first. The third problem is opacity. Nobody outside the companies knows the real figures, because until very recently nobody published them.

Consider what the Visakhapatnam project has declared. According to the News Minute's reporting on the clearance documents, the special purpose vehicles behind the campuses declared a combined water requirement of 501 kilolitres a day, of which 446 would be fresh and 55 recycled. That is roughly half a million litres a day. Set against a city deficit of 70 million litres a day, it sounds trivial.

Now set it against the other numbers in the same documents. The declared power requirement is 1,626 megawatts, plus 971.5 megawatts of diesel backup. A facility drawing more than one and a half gigawatts while consuming half a million litres a day would be, by a wide margin, the most water-efficient large computing installation on Earth. It is not impossible; fully air-cooled designs approach that profile. But it sits uneasily beside estimates from the other direction. Raja Rama Mohan Roy, founder of the non-profit Green Visakha and author of a widely circulated analysis in Countercurrents, puts the cluster's likely freshwater requirement at 55 to 70 million litres a day.

The gap between half a million litres and seventy million is not a rounding error. It is two orders of magnitude, and it exists because there is no mandatory, audited disclosure of data centre water use in India, or almost anywhere else. Mongabay India found that of the fifteen Indian states with dedicated data centre policies, most set no performance standards at all for power or water usage effectiveness, and that a national policy drafted by the electronics and IT ministry has sat unfinalised since 2020. A community cannot argue about a number nobody is required to produce.

The Water You Cannot See

Even if the on-site figure turns out to be genuinely small, the off-site figure will not be.

India's electricity still comes predominantly from coal, and thermal generation is intensely water-hungry because steam turbines require cooling. Under India's Environment (Protection) Amendment Rules, plants commissioned after 1 January 2017 may consume up to three cubic metres of water per megawatt-hour, a limit itself diluted from a stricter 2.5, and one the Centre for Science and Environment has repeatedly documented the sector failing to meet.

Do the arithmetic. A facility drawing one gigawatt continuously for a year consumes roughly 8.76 terawatt-hours. At three cubic metres per megawatt-hour, the embedded water in that electricity is on the order of 26 million cubic metres a year, around 72 million litres a day. That is a back-of-envelope figure, and the real number depends on the generation mix, on how much load is genuinely matched to wind and solar, and on whether the thermal plants use once-through or closed-cycle cooling. But the order of magnitude is the point. The water embedded in the electricity is plausibly a hundred times the water declared for the cooling system.

Google's commitment to build its own renewable generation matters, and in the right direction: solar and wind consume almost no water in operation. But grid-scale matching is an accounting exercise, not a physical one. A data centre running at three in the morning draws electrons from whatever is spinning, and in Andhra Pradesh that is largely coal. The declared diesel backup is a further reminder that keeping a gigawatt of silicon alive on an imperfect grid does not resemble the press release.

This is the analytical heart of the question, and it appears in neither the sustainability report nor the protest banner. The relevant footprint is the pipe entering the building, plus the river cooling the power station, plus the reservoir behind the pumped storage plant that firms the renewables. Count only the first and a gigawatt of compute consumes less water than a mid-sized hotel.

Air Cooling and Its Bill

Google's stated answer is air cooling, and this is a material concession rather than a public relations gesture.

On 3 June 2026 the company published water stewardship commitments that go further than any comparable operator. Google said it would only consider water cooling where local resources are healthy and resilient, and that where a source is at high risk it would choose air cooling or recycled water. It committed to replenishing more water than it consumes across its sites by 2030, a broadening of the 120 per cent replenishment target it had previously set, and put figures behind it: 165 water stewardship projects across 97 watersheds, expected to replenish more than 19 billion gallons a year, more than double what the company consumed in 2024, supported by more than 500 million dollars for water and reuse infrastructure. It also committed to reporting data centre water use by location, the first major cloud provider to do so. Its 2026 environmental report, published on 30 June, stated the company replenished approximately 7.7 billion gallons in 2025, roughly 78 per cent of its freshwater consumption. Google has cited a new Indian data centre as a site where watershed assessment pushed it towards air cooling, and told Reuters the Visakhapatnam project would use advanced air cooling to protect vital local water resources.

Take that at face value and it is a win for the campaigners, and it is also the direct result of pressure. Google did not adopt a watershed risk screen in a vacuum. It adopted one after Querétaro, after Santiago, after years of local resistance in exactly the places where communities had the standing to make trouble.

But air cooling is not free, and the bill lands on the other side of the ledger. Removing heat with air rather than evaporating water requires more fans and airflow, typically around ten per cent more electricity for equivalent cooling. On a coal-heavy grid, that means roughly ten per cent more embedded water consumed at the power station, plus the associated emissions. The net effect can be to move water consumption from one basin to another rather than eliminate it. It is a real improvement for Mudasarlova. Whether it is one for Andhra Pradesh depends on arithmetic nobody has published.

Replenishment carries a similar asterisk. Restoring a wetland in one watershed does not put water back into a different one, and a pledge to return more water than the company consumes is portfolio-wide arithmetic. Nineteen billion gallons replenished across ninety-seven watersheds is a global ratio, and a global ratio says nothing whatever about any particular basin, including the one above Mudasarlova. The commitment means something only if it is basin-specific, same-year and independently verified, and it has not yet been tested in Visakhapatnam.

Nine Days in April

If the water numbers are contested, the process that approved them is not. It is documented, and it is remarkable.

According to the News Minute's account of the clearance record, two special purpose vehicles owned by Adani Infra applied online for environmental clearance on 9 April 2026. The State Level Expert Appraisal Committee met on 10 April. Clearances were granted on 18 April. The foundation stone was laid on 28 April. Nine days elapsed between application and approval for one of the largest industrial developments in the state's history.

The mechanism was a classification decision. The projects were appraised as Category B2 building and construction projects under Schedule 8(a) of the Environment Impact Assessment Notification of 2006, a category requiring neither union government appraisal nor a public hearing. Schedule 8(a) defines it as covering built-up areas below 1.5 lakh square metres. Each of the two Visakhapatnam parks declared a built-up area of roughly 149,000 square metres. E.A.S. Sarma, a retired Indian Administrative Service officer who served as secretary to the Government of India in the power ministry and who lives in Visakhapatnam, has written repeatedly to the environment ministry arguing that the clearances were rushed, leaving little time for meaningful appraisal, and that states sometimes use Category B precisely to avoid central scrutiny. He has asked for them to be revoked.

The deeper problem is structural, and the government has confirmed it in Parliament. Kirti Vardhan Singh, minister of state for environment, forest and climate change, told the Rajya Sabha on 2 April 2026 that AI data centres do not, as such, require environmental clearance under the 2006 notification, and the government restated the position in Parliament in August 2026 with the thresholds spelled out. A data centre needs clearance only if it forms part of a building and construction project with a built-up area above 20,000 square metres, or a township or area development project covering fifty hectares or more, or one with a built-up area of 150,000 square metres or more. India's assessment regime has no category for a facility whose defining impacts are electricity demand, water demand and heat rejection. It regulates the shed, not the machine inside it. A structure is assessed on its square metreage; the gigawatt it draws and the aquifer it taps are, formally, somebody else's department.

The consequences are predictable. The Human Rights Forum has objected that the forest department granted a no objection certificate for a 160-acre site adjacent to Kambalakonda and its notified eco-sensitive zone, and that nearly 90 per cent of the Tarluvada site overlaps the Pedda Chukka Konda reserve forest. Sarma argues that construction is blocking natural water inflows into Mudasarlova. The Forum has filed three cases at the National Green Tribunal. Bolisetti Satyanarayana, national convener of the water conservation network Jal Biradari, has a public interest litigation before the Andhra Pradesh High Court asking it to determine whether statutory environmental and wildlife clearances were required at all for data centre projects near Kambalakonda, and to protect the natural streams and drinking water sources below them. That case was listed for 2 September. The High Court advanced it to 24 August after an application alleging that land levelling, tree felling and other construction activity were continuing on the slopes of the Simhachalam hill range, and directed the respondents to file their answers before the earlier date. A court moving its own timetable forward because the building is outrunning the case is a precise measure of the difficulty: once the participatory channels are closed, litigation is the only instrument left, and litigation moves more slowly than an earthmover. The state denies the project was fast-tracked, and says no water intended for rural or residential use will be diverted, and that the nearby reservoir will not be drawn upon.

Notice what is missing. At no point was there a statutory public hearing. The people of Adavivaram, Tarluvada and Rambilli were not asked. They are litigating because litigation was the only channel left open to them.

The Sovereignty Trilemma

Visakhapatnam is a specific place with specific hills and a specific reservoir. It is also an instance of a pattern that has now been mapped.

In July 2026 a team led by Muntaser Syed, with Marius C. Silaghi, Sheikh Abujar, Sharun Akter Khushbu and Amal El Ahmad, published a study on arXiv titled “The Environmental Cost of Digital Sovereignty: Water, Energy, and Emissions Impacts of Sovereign AI Infrastructure in the Global South”. Nations across the Global South have committed over 200 billion dollars to sovereign AI development, it notes, and the environmental consequences have gone almost entirely unexamined.

The headline finding is stark. Of 52 developing countries with active sovereign AI programmes, roughly 70.6 per cent face high overall water risk according to the World Resources Institute's Aqueduct atlas. The overlap between where sovereign compute is being built and where water is already scarce is close to total. The paper models four cases: the United Arab Emirates, Bangladesh, India and Kenya. A hypothetical 1,024-GPU cluster using evaporative cooling in the UAE would require over 30 million litres a year. Bangladesh's plans, the authors found, contain no siting strategy at all, in a country where more than a fifth of the land floods in an average year and as much as 70 per cent of it in an extreme one.

The authors name the bind precisely, calling it a sovereignty-sustainability trilemma: the difficulty of simultaneously achieving AI sovereignty, environmental responsibility and affordable resources for citizens. Pick any two. A country can have sovereign compute and cheap water if it is prepared to wreck its basins. It can have environmental responsibility and affordable resources if it is prepared to rent its compute from Virginia.

India's position sharpens the point. The World Resources Institute ranks India thirteenth among countries facing extremely high baseline water stress, a group in which agriculture, industry and municipalities withdraw more than 80 per cent of available supply in an average year. This is the country in which the world's largest overseas AI campus is being built.

The global demand curve makes local decisions cumulative. Pengfei Li, Jianyi Yang, Mohammad A. Islam and Shaolei Ren, in the paper that first forced water into the AI conversation, projected that global AI demand would account for 4.2 to 6.6 billion cubic metres of water withdrawal in 2027. The error bars are wide, and its authors say so. But no plausible version of it is small, and every cubic metre lands somewhere specific. Pedram Bakhtiarifard, Pınar Tözün, Christian Igel and Raghavendra Selvan, in a position paper accepted for ICML 2026, argue that treating sustainability as an emissions question alone obscures the tension between expanding access and expanding resource use.

Who Gets To Be Consulted

In July 2026, at the annual session of the United Nations Expert Mechanism on the Rights of Indigenous Peoples, data centres appeared substantially on the agenda for the first time.

Maren Storslett, a member of the Sámi Parliament in Norway, told the meeting that AI is resource-intensive and requires vast amounts of energy, and that in Sápmi large data centres already put immense pressure on their territories. She added a formulation since widely quoted: that the world must not only ask what AI can do, but what it should do, and that respect for the rights of Indigenous peoples must apply. Cheyenna Morgan, an enrolled member of the Keetoowah Band of Cherokee and coalition coordinator for Stop Data Colonialism, put it plainest: these impacts will be felt by regular people who did not ask to have these facilities in their neighbourhoods.

The demand was specific. Delegates called for data centre projects to comply with free, prior and informed consent, for in-depth impact studies before permitting rather than after, and for participation across a project's whole lifecycle. Roberto Anacé, a leader of the Anacé people of northeastern Brazil, described how a ten billion dollar facility proposed near his community had divided it; his people filed a formal complaint in 2025 alleging their consultation rights had been violated. Delegates cited precedents where consent regimes had bitten: a Google data centre in Santiago suspended by a Chilean environmental tribunal in 2024 over an inadequate impact assessment, construction moratoriums adopted by the Seminole Nation of Oklahoma and the Eastern Band of Cherokee Indians, and a 650-megawatt project in Alberta in which the Woodland Cree First Nation holds a 51 per cent stake.

Transpose that framework to Andhra Pradesh and it stops working. India does not accept that the international category of Indigenous peoples applies within its borders. It has not ratified ILO Convention 169, and it voted for the UN Declaration on the Rights of Indigenous Peoples while maintaining that all Indians are indigenous and the declaration is therefore not applicable domestically. What India has instead is a constitutional category, Scheduled Tribes, and a domestic architecture: the Fifth Schedule, designating Scheduled Areas; the Panchayats (Extension to Scheduled Areas) Act of 1996, requiring consultation with the gram sabha before land there is acquired; and the Forest Rights Act of 2006, requiring gram sabha consent for diverting forest land. On paper this is not weaker than free, prior and informed consent. In practice it is chronically under-implemented: Andhra Pradesh published PESA rules in 2011, fifteen years after the Act, and awareness among the communities it protects remains minimal.

Here is what gets lost in the framing. The three campuses are not in Scheduled Areas. Adavivaram, Tarluvada and Rambilli sit in the coastal belt, not the Fifth Schedule agency tracts of the hills, and the people fighting the project in the High Court are urban environmentalists, retired civil servants and residents worried about their taps. Presenting Visakhapatnam as a straightforward story of Indigenous dispossession would be inaccurate. The Adivasi dimension is real, but it is one step upstream, in the electricity.

The Power Comes From the Hills

A gigawatt-scale campus needs firm power, and firm power in a renewables-heavy system needs storage. Andhra Pradesh's answer has been pumped storage hydro, and its pumped storage projects are overwhelmingly located in the Fifth Schedule agency areas of the north of the state.

Reporting by The Wire documented five such projects allocated to private developers, with a combined capacity of 6,600 megawatts across around 2,260 acres in Parvathipuram Manyam and Alluri Sitharama Raju districts, ranging from Karrivalasa at 1,000 megawatts to Pedakota at 1,800. G. Rohit, state secretary of the Human Rights Forum in Andhra Pradesh, said the organisation was shocked at the brazen manner in which the projects had been granted in open contempt of the law, and that no information had been conveyed, no discussion had taken place and there had been no transparency. Ramarao Dora, convenor of the Andhra Pradesh Adivasi Joint Action Committee, said Adivasis in the scheduled areas oppose the projects because they rightly perceive them as harmful. The alleged breaches are specific: Section 5 of PESA, Section 6 of the Forest Rights Act, and the absence of the statutorily required consultation with the Tribal Advisory Council.

These projects predate the Google announcement and are not formally attached to it. That is exactly why they matter. The energy system that will make gigawatt-scale compute viable on India's east coast is being assembled in Adivasi territory, under a consent regime the communities concerned say is being ignored, and no clearance for a campus in Anakapalli will ever ask about it. The impact assessment stops at the fence line. The supply chain does not.

This is the governance gap in its purest form. Consent, where it applies at all, applies to the project on the land. The AI build-out is not a project on a piece of land. It is a system: a campus, a substation, a transmission corridor, a reservoir in the hills, a coal plant burning through a river's cooling capacity. Consent granted or withheld at any single node cannot govern the whole.

Counting the Jobs

The economic case deserves the same scrutiny, and it does not emerge unscathed.

The most careful recent evidence comes from Dany Bahar and Greg Wright, whose analysis of data centre employment effects was published by Brookings in May 2026 and updated on 10 August. Their finding is two-sided. Labour markets receiving their first large data centre see employment in data processing rise by 56 per cent over the first decade, with telecommunications gains of 43 per cent, an effect larger for hyperscale facilities than for colocation providers. But wages remain flat, home prices rise by two to five per cent, and the facilities themselves generate roughly 100 to 200 local jobs each. The authors' summary is that data centres do create jobs, but fewer than industry advocates claim.

Hold that against 188,000. The figure is an ecosystem projection covering construction, indirect and induced employment across a multi-year build-out, not a headcount of people who will work at the campus. Construction employment is genuine, substantial and temporary. Permanent operational staffing is measured in hundreds, because the facilities are automated by design.

That does not make the investment worthless. Subsea cable landings, transmission upgrades and low-latency compute are genuine public goods, and hyperscalers attract other hyperscalers. But it changes how the trade should be evaluated. If the state is discounting land, waiving stamp duty, cutting electricity tariffs for fifteen years and reimbursing tax up to 2,245 crore rupees, the public is buying something and should be told accurately what. Guaranteeing water for twenty years in a city with a 70 million litre daily deficit is itself a subsidy, and it is the one that has not been priced.

What Protection Would Actually Look Like

The gap between what communities in Visakhapatnam can demand and what communities in Santiago or Oklahoma have secured is not one of moral entitlement. It is a gap in legal machinery, and machinery can be built. Six changes would close most of it.

First, make data centres a distinct category under India's Environment Impact Assessment Notification, triggered by connected load and water demand rather than floor area, with mandatory public hearings above a threshold. A facility drawing 1,626 megawatts should not be appraised as a building. The government's own answer to Parliament establishes that it currently is.

Second, require cumulative, basin-level assessment. Visakhapatnam is not receiving one data centre but a cluster, with other operators also planning capacity in the region. Assessing each special purpose vehicle in isolation guarantees the aggregate impact is never examined by anyone.

Third, mandate full water accounting, disclosed publicly per site, independently audited, covering withdrawal and consumption separately and including the embedded water of purchased electricity. Google's per-location reporting is the right template and should be a licence condition rather than a voluntary pledge, applied to every operator. A two-order-of-magnitude gap between declared and estimated consumption should not be possible in a regulated industry.

Fourth, extend consent obligations along the supply chain. If a data centre's firm power depends on pumped storage in a Fifth Schedule area, the gram sabha consent requirements of PESA and the Forest Rights Act should attach to the offtaker as well as the generator. This is not exotic; it is the logic already governing due diligence for conflict minerals and forced labour.

Fifth, price and contract the water properly. Twenty-year guaranteed supply in a deficit basin should carry a full-cost tariff, a hard volumetric cap, automatic curtailment ahead of domestic and agricultural users during declared scarcity, and same-basin replenishment verified annually by an independent body. Credits earned in another watershed should not count.

Sixth, negotiate a binding community benefit agreement rather than relying on corporate social responsibility. The Alberta precedent, where a First Nation holds a majority stake in a 650-megawatt facility, shows the alternative to exclusion is not obstruction but ownership. Equity, local hiring guarantees, funded municipal water infrastructure and an enforceable grievance mechanism turn a community from an obstacle into a counterparty.

None of this requires India to accept a category of Indigenous peoples it has rejected for four decades. Every item is achievable inside its existing constitutional framework. They require only that the framework be applied.

Answering the Question From the Hillside

So what does it mean when the technology powering artificial intelligence in wealthier nations is fuelled by water drawn from a set of countries composed, almost entirely, of countries that cannot spare it? Of the 52 developing nations with active sovereign AI programmes, 70.6 per cent already face high water risk. That is not a claim about the developing world in general. It is a claim about the particular list of countries that have decided to build their own compute, and that list is made up, very nearly without exception, of places where the water has already run short.

It means, first, that the transaction is not what it appears. The exchange offered to Visakhapatnam is not water for prosperity. It is water, land, forest, forgone revenue, discounted power and twenty years of guaranteed supply, in return for a few hundred permanent jobs, a modest ecosystem effect, and a claim on digital sovereignty that will be exercised mainly by a company headquartered in Mountain View. That may still be a trade worth making. It is not the trade that was described.

It means, second, that the injustice is procedural before it is environmental. Nine days is not enough time to appraise anything, and a classification that avoids a public hearing is not a technicality; it is the whole ballgame. The people of Adavivaram did not lose an argument about water. They were never given the argument. Everything that has followed, the marches, the banners, the tribunal cases, the litigation the High Court pulled forward to keep pace with the diggers, is the sound of a community using the only instruments left after the participatory ones were bypassed.

It means, third, that the exported thirst is invisible even to the people exporting it. The user in London generating a summary cannot know that the marginal electron came from a coal plant in Andhra Pradesh, that the plant consumed three cubic metres of water per megawatt-hour, or that the reservoir firming the renewables sits on land an Adivasi gram sabha was never asked about. The trilemma identified by Syed and colleagues is invisible from the prompt box by design.

And what protections should exist? Not a veto exercised from abroad. The paternalism objection is right that the Global South should not be denied infrastructure the Global North built without asking anyone. But it cuts the other way, and harder. Communities in Chile, in Oklahoma and in Ireland have won moratoriums, suspensions, disclosure requirements and equity stakes, because they had standing, hearings, tribunals that would listen, and in some cases treaty rights. The paternalistic act is not insisting that Visakhapatnam gets protections. It is building at Visakhapatnam precisely because it will not.

The protections that should exist are the ones that already exist elsewhere: a statutory right to be heard before the earth is cut, audited disclosure of what will be consumed, consent obligations that follow the electricity to its source, and a share of the equity rather than a plaque on a wall. There is nothing in that list Google could not accept tomorrow and still make money, and nothing Andhra Pradesh lacks the power to require.

Work on the hillside above Mudasarlova continues. The terraces are cut, the red earth is exposed, and the monsoon runoff that used to feed the reservoir now finds a different path down. The High Court's hearing is listed for this week, the matter live before it as this goes to press. Whatever it decides, and whenever, the more consequential question was settled by default in nine days in April, by a form that classified a gigawatt of artificial intelligence as a building. The water will follow the law. The only thing still undecided is whose law it is.

Sources and References

1. Reuters, “Google's $15 billion India data centre project battles water, wildlife concerns”, 6 August 2026, syndicated by The Kathmandu Post. https://kathmandupost.com/world/2026/08/06/google-s-15-billion-india-data-centre-project-battles-water-wildlife-concerns
2. edie, “Google's $15bn India data centre project faces water and environmental challenges”, August 2026. https://www.edie.net/googles-15bn-india-data-centre-project-faces-water-and-environmental-challenges/
3. Google, “Our first AI hub in India, powered by a $15 billion investment”, Google India Blog, 14 October 2025. https://blog.google/intl/en-in/company-news/our-first-ai-hub-in-india-powered-by-a-15-billion-investment/
4. The Tribune (India), “Andhra govt allots 480 acres for Adani-Google AI data Centre in Visakhapatnam”. https://www.tribuneindia.com/news/business/andhra-govt-allots-480-acres-for-adani-google-ai-data-centre-in-visakhapatnam/
5. Data Center Dynamics, “Google confirms $15bn data center project in Andhra Pradesh, India”. https://www.datacenterdynamics.com/en/news/google-confirms-15bn-data-center-project-in-andhra-pradesh-india/
6. The News Minute, “Inside the subsidies for Google's Vizag data centre amid Andhra-Karnataka spar”. https://www.thenewsminute.com/andhra-pradesh/inside-the-subsidies-for-googles-vizag-data-centre-amid-andhra-karnataka-spar
7. The News Minute, “Vizag Google Adani AI data centre: State govt rushed environmental clearance, activists allege”. https://www.thenewsminute.com/andhra-pradesh/vizag-google-adani-ai-data-centre-state-govt-rushed-environmental-clearance-activists-allege
8. The News Minute, “HRF challenges legality of Adani-Google Vizag data centre, demands immediate stop”. https://www.thenewsminute.com/andhra-pradesh/hrf-challenges-legality-of-adani-google-vizag-data-centre-demands-immediate-stop
9. Mongabay India, “India bets on data centres even as water, energy-use concerns mount”, May 2026. https://india.mongabay.com/2026/05/india-bets-on-data-centres-even-as-water-energy-use-concerns-mount/
10. Mongabay, “Indigenous advocates push for rights protections around AI data centers”, July 2026. https://news.mongabay.com/2026/07/indigenous-advocates-push-for-rights-protections-around-ai-data-centers/
11. Business & Human Rights Resource Centre, “Global: Indigenous leaders call for data centres projects to comply with their right to free, prior and informed consent during UN meeting”, July 2026. https://www.business-humanrights.org/en/latest-news/global-indigenous-leaders-call-for-data-centres-projects-to-comply-with-their-right-to-free-prior-and-informed-consent-during-un-meeting/
12. Raja Rama Mohan Roy, “The Hidden Environmental Cost of AI: Can Visakhapatnam Afford Giant Data Centres?“, Countercurrents, July 2026. https://countercurrents.org/2026/07/the-hidden-environmental-cost-of-ai-can-visakhapatnam-afford-giant-data-centres/
13. Countercurrents, “AI Data Centres and Environmental Justice: E.A.S. Sarma Urges Scrutiny of Projects Amid Ecological and Human Rights Concerns”, June 2026. https://countercurrents.org/2026/06/ai-data-centres-and-environmental-justice-e-a-s-sarma-urges-scrutiny-of-projects-amid-ecological-and-human-rights-concerns/
14. Countercurrents, “HRF Demands Halt to Vizag Hyperscale Data Center Over Alleged Environmental Violations”, May 2026. https://countercurrents.org/2026/05/hrf-demands-halt-to-vizag-hyperscale-data-center-over-alleged-environmental-violations/
15. Deccan Chronicle, “High Court Advances Hearing Over Data Centres Near Kambalakonda Sanctuary”. https://www.deccanchronicle.com/southern-states/andhra-pradesh/high-court-advances-hearing-over-data-centres-near-kambalakonda-sanctuary-1976576
16. Muntaser Syed, Marius C. Silaghi, Sheikh Abujar, Sharun Akter Khushbu and Amal El Ahmad, “The Environmental Cost of Digital Sovereignty: Water, Energy, and Emissions Impacts of Sovereign AI Infrastructure in the Global South”, arXiv:2607.13443, 15 July 2026. https://arxiv.org/abs/2607.13443
17. Pengfei Li, Jianyi Yang, Mohammad A. Islam and Shaolei Ren, “Making AI Less 'Thirsty': Uncovering and Addressing the Secret Water Footprint of AI Models”, arXiv:2304.03271. https://arxiv.org/abs/2304.03271
18. Pedram Bakhtiarifard, Pınar Tözün, Christian Igel and Raghavendra Selvan, “Position: Neglecting the Sustainability of AI is Fuelling a Global AI Arms Race”, arXiv:2502.20016, accepted at ICML 2026. https://arxiv.org/abs/2502.20016
19. World Resources Institute, “25 Countries, Housing One-quarter of the Population, Face Extremely High Water Stress”, Aqueduct Water Risk Atlas. https://www.wri.org/insights/highest-water-stressed-countries
20. Google, “Google's water stewardship commitments for local communities”, 3 June 2026. https://blog.google/company-news/outreach-and-initiatives/sustainability/new-water-stewardship-commitments/
21. Google, “Read Google's 2026 Environmental Report”, 30 June 2026. https://blog.google/company-news/outreach-and-initiatives/sustainability/2026-environmental-report/
22. Down To Earth, “As told to Parliament (April 2, 2026): Centre acknowledges AI's energy and water footprint while key facilities remain beyond EIA mandate”. https://www.downtoearth.org.in/environment/as-told-to-parliament-april-2-2026-centre-acknowledges-ais-energy-and-water-footprint-while-key-facilities-remain-beyond-eia-mandate
23. The Print, “AI data centres do not need environment clearance, Centre tells Parliament”, August 2026. https://theprint.in/environment/ai-data-centres-environment-clearance-centre-parliament/3007640/
24. The Wire, “Andhra Pradesh: Pumped Storage Projects Spark Concerns over Tribal Displacement and Environmental Harm”, 6 December 2024. https://m.thewire.in/article/environment/andhra-pradesh-pumped-storage-projects-spark-concerns-over-tribal-displacement-and-environmental-harm
25. Dany Bahar and Greg Wright, “New evidence on data center employment effects”, Brookings Institution, published 4 May 2026, updated 10 August 2026. https://www.brookings.edu/articles/new-evidence-on-data-center-employment-effects/

---

Tim Green UK-based Systems Theorist & Independent Technology Writer

Tim explores the intersections of artificial intelligence, decentralised cognition, and posthuman ethics. His work, published at smarterarticles.co.uk, challenges dominant narratives of technological progress while proposing interdisciplinary frameworks for collective intelligence and digital stewardship.

His writing has been featured on Ground News and shared by independent researchers across both academic and technological communities.

ORCID: 0009-0002-0156-9795 Email: tim@smarterarticles.co.uk

Listen to the free weekly SmarterArticles Podcast

My wife has been interested in Russian literature for a long time now. She’s also been interested in their language. Recently she just read a book called “Dead Souls” by Gogol. She’s been interested in the serf life in Russia so just started reading “Four Russian Serf Narratives” compiled by John MacKay.

We’ve talked on and off through many years about slavery, serfdom, freemen, lords, and more. What I believe is that as history looks back at this time they will not think it much superior to the past ages. Most think of themselves as free people. I don’t think we are anything close. Maybe close to what people called freemen or “free tenant” (see here, here, and here for the basics) were but maybe not even as free as many of them were.

I haven’t heard of people asking for reparations for serfdom or indentured servitude, but it’s not all that much better than slavery. In my view serfdom is a sort of slavery tied to an area of land. There is a lord or master over that area and a lot of your labors are funneled away with the head of that property selling that effort or paying their dues to keep the land in the master’s possession. With slavery you could sell the person and it isn’t associated with the land, the person (slave) and the property are separate entities. With serfdom the person (serf) is tied to the land. In Russia they seemed to blend the two to an extend. And they were late to the game, it seems they were just copying Europe. So it came and went quickly in Russia where in Europe it built up very slowly and stuck around a lot longer before emancipation of serfs and later slaves.

Today people are in a state of freeman or lord over their own life and possessions. But that doesn’t mean they are truly free or a sovereign over their life. Above them they have masters called mayors, governors, congressmen, senators, vice presidents, presidents, and countless agency members and law enforcement agents pressing their rules and regulations upon their subjects. The musical chair game makes it more palatable because those rulers seem to be in a temporary position and the most naive people seem to think they could even gain such a position – which gives the illusion of equality of sorts.

But seriously. What would it be to be truly free? In the past the idea was that you could keep the fruits of your labor. So what percentage of your earnings do you keep? Consider what goes out to your basic living conditions. For most people much less than 35% of the earnings stay at home (see here). The rest goes out to food, mortgage, cars, car insurance, healthcare, life insurance, clothes, other odds and ends. And people want those things, but isn’t that a form of servitude? You are a servant to the food industry, housing industry, car industry, insurance industry, healthcare industry, clothing/textile industry, and other odds-and-ends industries. And after all of that you are very lucky to keep even close to 30%. And what do people do with that… Well most invest it so they are servants to the banking industry, investing industry, and many markets that they think worthwhile to dump excess into.

So are we free? Perhaps we are just “freemen” or maybe just mobile serfs. Maybe nothing has really changed. Maybe things are just as bad, worse, or slightly better but the rulers have become much better at pulling the wool over our eyes. Maybe we are better at deluding ourselves and feeding on the lies. Maybe we want to be free so badly, that we just have become masters at pretending that we don’t have masters.

Sometimes, the only person you need to escape from, is yourself.

The day unfolded as a restless, rain-flecked wander through Porto—beginning with an early escape to the tide pools and a spellbinding conversation about octopuses and the ocean, followed by an impulsive train ride into the city in search of reclaimed tiles and small treasures that mostly stayed just out of reach. It became a long, uphill ramble marked by coughing fits, missed shops, narrow alleys, sudden beauty, and the quiet pleasure of getting lost, ducking into galleries, weighing gifts, and thinking of everyone back home. As evening settled in, rain returned, wine waited at home, health worries hovered, and the city glowed with holiday lights—leaving the day feeling like Porto itself: generous, disorienting, a little exhausting. A place full of moments of feeling more than for what was accomplished.

[waves crashing] Oh, my God. This is a beautiful place. I escaped my captors.

Most everyone was still asleep, though L was wide awake. She’d fallen in love with the ocean here, and it was easy to see why. She’s intelligent, curious, and loves to talk, especially about the tide pools. She showed videos for nearly twenty minutes of the octopuses she finds there — strange, beautiful little creatures shifting color and texture as they move.

I went out that morning around 8:30 because the tide was low, hoping to see some for myself, but I didn’t find any. Laurie had seen one that was apparently enormous, though she said most of them are tiny, only a couple of inches long. Even secondhand, it was fascinating. Inches? I don’t know. There’s, uh... It’s hard for me to tell, ‘cause I didn’t take the video. I don’t know what the scale of these things is, but they were just incredible. Watching... watching them change, uh, change colors, you know, and textures. They change textures. Ah, just incredible. Portuguese octopuses are amazing. So these sea slugs and she had all this stuff about the... I mean, this lady is right in anyone’s wheelhouse who craves going deep on subjects. I was fascinated. I really enjoyed the conversation.

Uh, she loves Jehovah. She loves the truth. She loves people. She’s so broken up about her friends in India. The Germans. They get to go home. But her friends, her Indian friends, because they are gonna go to jail for a long time.

I jumped on the train and rushed into the city, trying to reach a shop I’d heard about. It specializes in reclaimed materials from old buildings — tiles, bricks, textiles, furniture, and other architectural pieces that would otherwise be thrown away. Instead, they clean and resell them, which makes the place useful for anyone restoring an old property or trying to match missing details from an existing building.

I was especially interested in the tiles. In a city like Porto, where so many buildings are covered in beautiful tilework, the idea of a place preserving those fragments felt worth seeing.

Unfortunately, I got there just before closing, and they had already locked up early. This VERY Europe. 'There was no getting in. No amount of wanting it was going to change that.

There were a few charming little things tucked into the shopfronts, enough to make me stop and look more closely. I paused to take a picture, thinking I might have found a treasure, but after a second look it didn’t quite feel right.

I kept walking, half-following the route and half-letting the city choose for me. At one point I had to decide whether to turn left or keep going straight, and I went straight. The street opened into one of those scenes that makes you want to stop everything, pull out a sketchbook, and paint it before the light changes.

I lost my train of thought for a moment, probably because I was still running on the energy of the city. I had jumped on the train and hurried down to reach the place before it closed at five, but even though I arrived around 4:30, it was already locked up tight. I had thought it was a shop, but from the outside it looked more like a museum, so it may not have worked out anyway.

The whole walk from Bento Station had been uphill, and I had pushed harder than I should have. By the time I got there, my lungs were reminding me that running two and a half kilometers uphill is not exactly ideal for sport-induced asthma. So I turned around and started the slower walk back down, coughing a little and laughing at the fact that my next best option was apparently right back near the train station where I started.

I turned and found this gorgeous picturesque street. THIS is a European street: narrow, old, and full of texture.

I tried to take a picture, but I didn’t like the way it was coming out. So I turned around and, lo and behold, there they were: beautiful tiny little shops. The street wasn’t even eight feet wide. It was basically an alley.

Blurry. Of course.

So I tried again. Maybe that one worked. But then I looked at it and thought, oh, that looks fake. Wild. It looked like a composite — It was so well lit and the alley behind me was so dark.

Then it started raining again. Someone had loaned me a raincoat, which was exactly what I should have had to begin with. It didn’t breathe at all, so I got warm pretty fast. I checked my route again, trying to figure out whether I was still headed the right way.

I was still on the right route. Good.

I just needed to get to the bottom of the hill, and then I probably needed to buy an umbrella. Honestly, I should have bought one right then. I should have brought one with me in the first place, but I didn’t.

I figured I’d be out in the open soon enough and could buy one for probably twenty euros.

On a sunny day, it would have cost me two.

Supply and demand, baby. Supply and demand.

Anyway, it was Saturday night, our last night in Porto. Tomorrow night would be somewhere else, and I still had three bottles of wine to either drink or give away. Robert and Lauri were probably going to inherit them.

We thought we’d drink more during the week, but we didn’t. Mostly because I was working and Angie had been getting sick. Which was a shame, because the sparkling brut was delicious. Delicious. And it was only five euros a bottle.

I still couldn’t get over how cheap the wine was there. Even the bottle of red we bought — delivered through Uber Eats, no less — was only about eleven dollars. Pretty crazy. Back in the States, that easily would have felt like a hundred dollars worth of wine.

So it’s not the end of the world, you know, if you don’t get to drink it, other than I would really have enjoyed drinking it, especially that brut. It’s so good. I think I’m gonna drink a bottle of that tonight.

I kept thinking I should buy an umbrella. Why wasn’t I buying an umbrella? I had already walked past two umbrella stands and somehow managed not to buy one at either.

Don’t be a fool!

So I decided I’d go to the little store first and then decide about the umbrella. I crossed the street and worked my way past the tourist area, where everything started to look vaguely familiar and completely confusing at the same time. I was pretty sure I’d been to most of those places already. We had covered a lot of ground.

Then I got lost again, naturally.

The recording kept stopping every time I checked the map, so whole chunks of my wandering disappeared. One of the missing bits was a small diatribe on gold. I had stopped at a little gold shop and just marveled at the prices. Beautiful stuff, incredible craftsmanship, but everything seemed to start around two thousand euros and climb from there. They say filigree is a uniquely Portuguese gift, and I could see why. It was delicate, intricate, and gorgeous.

Also at 2500 euros, wildly out of budget.

That was the thing about gold: beautiful, but not exactly built for broke poets. If I had been a wealthier man, I probably wouldn’t have stayed one for long. I would have blown it all on pretty things, because that is apparently what I do.

Then I came across an art store — or maybe a gallery. It had these beautiful black-and-white prints in the window, the kind of thing that makes you stop even when you’re supposed to be going somewhere else. The store name was bold, to put it mildly: “I’m The F’ing Artist,” except they were considerably more frank about the word “F.”

I laughed when I realized they signed everything, “I’m The F*&#@g Artist.” It was a bold statement, and definitely not something anyone would forget.

The gallery had sketchbooks too, including one with that same brash artist name printed on the front. It would have been funny, maybe even useful, except not exactly ideal for carrying around with my particular crowd. They were fifteen euros, which felt suspiciously like thirty dollars once my brain got involved. Besides, I had already bought a sketchbook, so I passed.

Then I saw the scarves.

Ooh. Scarves.

Pintura paintings. Pintura original acrylic paint on canvas, €1,000. Scarves, €23. Hm, textiles are a good gift. Maybe a scarf.

Hm, they have such pretty ones. They have orange, orange. And blue. And Pink!

I should just get a magnet.

I’ve already stopped twice. I seem unable to reach my destination.

Ooh, there was a great sticker. I wanted to see if I could get that one.

Nope. It had already been peeled and failed. But I’m a professional sticker remover, so I wanted to see if I could succeed where others had failed.

Could the artist succeed?

He was succeeding so far.

When peeling stickers off round cylinders, it could be tough because the angles were strange. You had to get a straight side peeled off vertically and then peel across, because if you tried to peel from top to bottom, it tore every single time.

I was totally lost there. I think I was supposed to turn back there.

I got my mom a rock from the sidewalk, so she’d really like that. Too bad it will be stuck with our luggage in Germany for months and month and months!

And then I was going home, which was by Marino. I smelled marijuana.

They smoked marijuana there?

Mm.

Those kids.

[sniffs] [sighs]

Back at Robert and Laurie’s place, there was a huge painting in the guest room where we were staying. I hadn’t looked at it closely, but it was all gray-blue and oceanic, a massive moody thing that probably cost five or eight thousand dollars. Laurie told me the story of how they got it, which seemed to involve the natural social orbit of expats. They run around together, these little crews of transplanted people, finding each other in foreign cities and collecting stories along the way.

It’s funny because I don’t think Laurie wants us to leave, I think Angie wants to leave. I think she wants to go relax in a hotel, have her own space and sleep until noon, which I don’t blame her. We’ll see. They’ll work it out.

That was the thing about not having an opinion: I was fine either way. Angie had an opinion, so I let the girls work it out.

I didn’t know. He had a stomach bug, and Angie had sinus trouble. I didn’t think they were related. I thought she was just worried he was going to catch her sinus infection. I hoped we didn’t end up having to cut the trip short.

Traffic was light that night. There weren’t a ton of people out over there. The trees were still wrapped for the holidays. Obviously Christmas wasn’t until—what was it? Wednesday or Thursday or something.

It was just very beautiful. Lots of lights.

It had rained a little bit, but I was wearing someone’s raincoat that they had loaned me, so I stayed dry that time, except for my hair, which was extremely absorbent.

I didn’t know if you’ve been to Portugal reader, or France, or London, or Switzerland, or Italy. but you should DEF go to Portugal.

As I’m reflecting on my advice, good readers, I notice I have been lazy and ignored the crosswalk. it occurred to me what a scofflaw I am/was. A bad man.

I hoped the trip would give me an opportunity to see enough of Europe to adjust my viewpoint. Joy Division had talked about choosing self-preservation against people who were really only worried about themselves, and I could identify with that. I could identify with a lot of what was in those songs.

Music and travel have an effect on the soul. It’s uncomfortable in the best possible way.

In Summary: * Have hust tuned into 105.3 The Fan, DFW's #1 Sports Station, ready to hear tonight's Rangers Pregame Show, then the radio call of tonight's MLB game between the Rangers and the A's. Go Rangers!

Prayers, etc.: * I have a daily prayer regimen I try to follow throughout the day from early morning, as soon as I roll out of bed, until head hits pillow at night.

Health Metrics: * bw= 224.87 lbs. * bp= 152/66 (66)

Exercise: * morning stretches, balance exercises, kegel pelvic floor exercises, half squats, calf raises, wall push-ups, BP breathing exercises, pilates

Diet: * 05:25 – 1 banana * 06:20 – 1 slice of lemon meringue pie * 07:40 – cottage cheese * 12:10 – 1 barbacoa taco, steak, 1 tangerine

Activities, Chores, etc.: * 04:15 – listen to local news talk radio * 05:00 – bank accounts activity monitored . * 05:30 – read, write, pray, follow news reports from various sources, surf the socials, listen to musc, nap * 12:10 to 13:20 – watch old game shows and eat lunch at home with Sylvia * 14:30 – following news reports from various sources

Chess: * 14:00 – moved in all pending CC games