top of page
GUARD_Global_Operations_Command_logo_transparent-small.png

TERRAGUARD

TERRAGUARD Logo-transparent-small.png
TERRAGUARD MovesDon "Major Deej" Finger
00:00 / 03:48

Statistics

TERRAGUARD Statistics Dashboard Image.png

HISTORY

The Ground That Holds

TERRAGUARD was born from a hard lesson learned after the Soltan Invasion: winning a war does not mean the world has been saved.

​

When the Soltans struck Earth, the skies burned, oceans became battlefields, cities collapsed, and entire regions were cut off from food, medicine, fuel, transportation, shelter, and command authority. GUARD and the world’s defenders fought across every domain, but the land war revealed a brutal truth. Even when enemy forces were pushed back, people still died in the ruins. Roads were gone. Hospitals were overwhelmed. Water systems failed. Refugees moved by the millions. Supply depots were destroyed or inaccessible. Criminal networks preyed on desperation. Governments struggled to respond, and in many places, help simply did not arrive fast enough.

​

The world had heroes who could fight monsters.

​

It needed a force that could move through dust, fire, rubble, flood, famine, and political chaos to keep people alive after the battle.

​

That force became TERRAGUARD.

​

TERRAGUARD is GUARD’s land-based operations, logistics, disaster-response, engineering-support, convoy, relief, and infrastructure-stabilization command. It exists for the places where survival depends on roads, vehicles, shelters, depots, engineers, fuel, field kitchens, medical staging areas, communications, and the hard discipline of getting help to people who cannot wait.

​

Its mission began with one man’s refusal to accept abandonment as policy.

​

General Nathaniel Elias Stone had already served thirty years as a United States Army officer before TERRAGUARD existed. A West Point-trained commander with deep education in military science, logistics, civil defense doctrine, strategic studies, emergency logistics, multinational operations, and military infrastructure planning, Stone built his career on one belief: logistics are not behind the mission. Logistics are the mission when lives depend on movement.

​

During the Soltan Invasion, that belief became legendary.

​

Where other commanders saw civilians as complications, Stone saw the reason the war was being fought. He built defensive lines around refugee corridors, hospitals, field kitchens, water sources, shelters, and evacuation routes. His command posts became rescue hubs. His supply depots became lifelines. He coordinated military units, engineers, emergency responders, resistance groups, superheroes, and civilian volunteers into operations that moved both people and supplies through environments many considered lost.

​

Stone’s most famous wartime role came during the final battles in China, where Earth’s remaining defenders pushed to destroy one of the last Soltan power towers and bring down a surviving Soltan battleship. The campaign demanded more than firepower. Civilians were still trapped near the combat zone, infrastructure was failing, and the battle could not be won at the cost of the people it was meant to save. Stone helped coordinate assault forces, medical teams, evacuation convoys, engineering units, and relief supply movements as one integrated operation. When the final tower fell and the battleship was destroyed, Stone emerged as a global hero.

​

But the end of the invasion did not end the suffering.

​

Across the world, communities still starved. Families slept in shattered buildings. Children drank unsafe water. Medical systems collapsed under disease and injury. Crops had failed. Transportation routes were destroyed. Entire populations that had survived the Soltans were now being lost to hunger, exposure, infection, and neglect.

​

Stone filed requests to release reserve food, shelter, generators, medicine, and water purification supplies. He filed more. Then emergency petitions. But too many leaders hesitated. They argued jurisdiction, ownership, political consequences, liability, and timing while people waited in ruins.

​

Stone had spent the war saving civilians from alien invaders. He would not watch them die because paperwork moved slower than starvation.

He ordered supplies moved.

​

Military reserve food and shelter stockpiles were sent to devastated communities that had waited too long. The supplies went to families, field hospitals, broken towns, and exposed populations that had been promised help but received delay. To the public, it was mercy. To certain officials, it was insubordination.

​

Stone was reprimanded and decommissioned with honors.

​

The phrase “with honors” softened the announcement, but everyone understood the truth. His military career was over. After thirty years of service, after helping defend Earth, after standing in the final battles of the Soltan Invasion, Stone would never again hold command in the institution he had served most of his life.

​

His response became one of the most repeated statements in TERRAGUARD history:

“If feeding starving people ends my career, then my career ended doing its job.”

​

What was intended as a punishment became the beginning of something larger.

​

Months later, GUARD approached Stone with a mission no one else wanted. The organization needed a global land-based support command capable of moving personnel, vehicles, supplies, field shelters, fuel, engineers, emergency infrastructure, communications, and relief operations across every continent. It needed to operate through national politics, collapsed cities, destroyed roads, hostile zones, refugee movements, criminal interference, natural disasters, post-war instability, and every practical problem that keeps aid from reaching people.

​

The proposed command was considered too expensive, too difficult, too politically dangerous, and too complex to build quickly.

​

Stone accepted the challenge, but only on his terms.

​

TERRAGUARD would not be ceremonial. It would not be a paper command. It would not abandon civilians because of diplomatic hesitation. It would not exist merely to support battles and then leave the recovery to someone else. It would be mobile, disciplined, accountable, global, and built around one unbreakable doctrine:

Security, logistics, and humanitarian restoration are one mission.

​

From that doctrine, TERRAGUARD began.

​

What followed became one of the greatest organizational achievements in GUARD history. In five years, General Stone built what many believed would take twenty. TERRAGUARD established hardened depots, regional staging bases, convoy corridors, vehicle maintenance centers, mobile relief columns, shelter systems, disaster-response groups, engineering support teams, field communications networks, emergency supply chains, and ground infrastructure stabilization units.

​

Ground Zero Facility, TERRAGUARD’s headquarters in the Nevada desert, became the heart of this growing command. Built as a hardened base, airfield, logistics fortress, underground operations hub, and global coordination center, Ground Zero was designed to survive attacks and keep TERRAGUARD moving when other systems failed. Its flight lines support F-35 fighters, V-22 Osprey tilt-rotor aircraft, large cargo planes, transport vehicles, armored relief trucks, all-terrain convoys, engineering vehicles, and the equipment needed to move help across broken terrain.

​

But TERRAGUARD was never only a base.

​

It became a worldwide network.

​

Personnel came from every corner of the world: soldiers, engineers, medics, mechanics, drivers, construction specialists, emergency managers, logisticians, communications experts, translators, security personnel, pilots, planners, and Soltan Invasion survivors who understood what abandonment felt like. Some joined because they admired Stone. Others joined because TERRAGUARD offered a way to fight for people after the war was over. Many joined because they had once waited for help and wanted to become the ones who arrived.

​

Businesses rallied to the effort. Governments that had doubted the command began cooperating after seeing TERRAGUARD convoys restore order faster than committees could debate it. Relief agencies found in TERRAGUARD a partner capable of protecting routes, building camps, moving supplies, and restoring access. GUARD divisions came to rely on TERRAGUARD as the organization’s ground backbone: the force that could establish staging areas, support field teams, move personnel, supply disaster zones, secure logistics corridors, and restore the physical conditions needed for survival.

​

TERRAGUARD became known for its convoys.

​

The sight of TERRAGUARD vehicles rolling through dust, smoke, snow, floodwater, or ruined streets became a symbol recognized across the world. A TERRAGUARD convoy meant food was coming. Water was coming. Shelters were coming. Engineers were coming. Medical support was coming. Communications were coming. Protection was coming. More importantly, it meant someone had not forgotten.

​

That success created enemies.

​

Where TERRAGUARD delivered food, black-market profiteers lost control. Where it restored roads, corrupt powers lost leverage over isolated communities. Where its investigators tracked missing supplies, criminal networks lost hidden revenue. Where Stone built secure convoy routes, smugglers and traffickers lost territory. TERRAGUARD did not merely bring relief; it disrupted entire criminal ecosystems built on disaster and desperation.

​

Threats followed.

​

Convoys were ambushed. Supply manifests were falsified. Contractors were compromised. Routes were sabotaged. Depots were targeted. Assassins came for General Stone himself, including killers tied to the Death Legion’s wider criminal networks. The threats became so serious that Stone began wearing additional armored chest and back protection as part of his standard field command uniform.

​

But Stone remained mobile.

​

He refused to become a commander who led from safety while others faced the field. He continued inspecting motor pools, walking convoy lines, boarding cargo aircraft, entering underground corridors, briefing relief teams, visiting disaster zones, and standing beside TERRAGUARD personnel wherever the mission required. His constant movement made him difficult to target and even harder to intimidate.

​

This field presence shaped TERRAGUARD’s culture.

​

TERRAGUARD personnel are expected to be disciplined, practical, adaptable, and morally clear. They are trained to understand that every supply crate has value, every route must be protected, every shelter matters, and every delay can become a death sentence. They are not simply ground troops. They are responders, builders, convoy operators, protectors, engineers, logisticians, field coordinators, and guardians of recovery.

​

General Stone teaches that a battle is not finished when an enemy retreats. A battle is finished when the injured are treated, the hungry are fed, the exposed are sheltered, the roads reopen, the water runs clean, and people can begin living again.

​

That belief has made TERRAGUARD one of GUARD’s most respected and essential commands.

​

Today, TERRAGUARD operates wherever land-based crisis support is needed. It supports disaster zones, post-war regions, refugee corridors, damaged cities, rural collapse areas, emergency construction sites, major evacuation routes, supply-chain recovery missions, and GUARD-wide operations requiring large-scale ground coordination. It works alongside Aeroguard, Seaguard, Astroguard, Moonguard, Portalguard, Mystiguard, Guardian Corps, GUARD Medical, GUARD Resources, and Global Operations Command whenever the mission demands unified action.

​

Its headquarters at Ground Zero Facility stands as both fortress and promise. It is a hardened command center, vehicle hub, airfield, underground operations site, logistics engine, and symbol of the TERRAGUARD creed: the ground must hold.

​

TERRAGUARD was not created because the world needed another military branch.

​

It was created because the world needed a force that could do what others called impossible: bring order without arrogance, strength without abandonment, security without cruelty, and relief without delay.

​

It was created because General Stone understood something the Soltan Invasion proved beyond argument.

​

People do not only need saving from the enemy.

​

They need saving from hunger, exposure, disease, isolation, corruption, and the silence that follows when the world decides the emergency is over.

​

TERRAGUARD exists to break that silence.

​

When cities fall, TERRAGUARD moves.

When roads vanish, TERRAGUARD builds.

When supplies are stolen, TERRAGUARD hunts the chain.

When civilians are trapped, TERRAGUARD opens the corridor.

When the battle ends and the world looks away, TERRAGUARD arrives.

​

Its mission is not glory.

​

Its mission is survival.

​

And wherever its convoys roll, General Stone’s promise rolls with them:

We fight to protect people. If they die after the battle because we did nothing, then we protected an idea, not a life.

​

ORG CHART

TERRAGUARD Org Chart Image.png

OPERATIONS

OPERATIONS

TERRAGUARD is GUARD’s global land-based operations, logistics, transportation, disaster-response, engineering-support, convoy, relief, and infrastructure-stabilization command. Headquartered at Ground Zero Facility in the Nevada desert, TERRAGUARD exists to move help across the ground when roads are broken, governments are overwhelmed, supply chains are failing, and civilian survival depends on organized action.

​

TERRAGUARD does not simply arrive after a crisis. It builds the routes, protects the convoys, restores the access points, supports the shelters, moves the supplies, and holds the ground until communities can stand again.

​

Mission Statement

TERRAGUARD’s mission is to provide GUARD with a disciplined, mobile, land-based global response force capable of moving personnel, vehicles, supplies, engineering support, emergency shelters, food, water, medicine, fuel, communications, and protection into crisis areas anywhere on Earth.

​

TERRAGUARD supports military-defense operations, disaster relief, refugee movement, post-war recovery, infrastructure restoration, convoy security, emergency distribution, and long-term stabilization in coordination with GUARD commands, national governments, relief agencies, and local authorities.

​

Its guiding principle is simple:

The mission is not complete until people can live again.

​

Core Operational Responsibilities

TERRAGUARD operations include:

  • Ground transportation and convoy operations

  • Disaster-response logistics

  • Emergency supply distribution

  • Refugee and civilian evacuation support

  • Field shelter deployment

  • Mobile food, water, and medical supply support

  • Ground vehicle fleet readiness

  • Engineering and infrastructure restoration

  • Route clearance and access recovery

  • Tactical ground security for relief corridors

  • Post-war stabilization support

  • Humanitarian-security integration

  • National and international logistics coordination

  • Support for GUARD-wide field missions

  • Forward staging for multi-division operations

​

TERRAGUARD is often the first GUARD command to establish durable land access into a crisis zone and one of the last to leave after basic survival systems are restored.

​

Global Operational Areas

TERRAGUARD operates through a worldwide network of major transportation, distribution, staging, engineering, and international coordination hubs. These hubs support regional convoys, cargo transfer, aircraft loading, emergency warehousing, multinational operations, and rapid deployment into crisis zones.

​

North America

  1. Ground Zero Facility — Nevada, United States
    TERRAGUARD headquarters, primary command center, hardened logistics base, airfield, underground operations hub, and global coordination site.

  2. Boston GUARD Support Corridor — Massachusetts, United States
    Coordination route supporting Aegis Tower, GUARD headquarters functions, and eastern emergency response.

  3. Denver Mountain Logistics Hub — Colorado, United States
    High-altitude staging, mountain convoy training, winter mobility, and interior continental distribution.

  4. Houston Gulf Response Hub — Texas, United States
    Gulf disaster response, fuel logistics, flood operations, and coastal evacuation support.

  5. Los Angeles Pacific Distribution Hub — California, United States
    Pacific cargo transfer, port-linked supply movement, wildfire response, and western convoy dispatch.

  6. Seattle Cascadia Staging Hub — Washington, United States
    Earthquake response, mountain corridor support, port access, and northern Pacific operations.

  7. Anchorage Arctic Gateway Hub — Alaska, United States
    Arctic terrain operations, cold-weather logistics, remote community supply, and northern emergency support.

  8. Toronto Great Lakes Hub — Canada
    Cross-border coordination, winter response, Great Lakes logistics, and northern industrial support.

  9. Mexico City Central Coordination Hub — Mexico
    Regional planning, earthquake response, mountain-city logistics, and Latin American convoy linkage.

  10. Panama Intercontinental Transfer Hub — Panama
    North/South American cargo transfer, canal-linked logistics, and rapid movement between hemispheres.

​

South America

  1. Bogotá Andean Operations Hub — Colombia
    Mountain logistics, regional relief coordination, and northern South American staging.

  2. Lima Pacific Relief Hub — Peru
    Coastal earthquake response, Andean access, and Pacific-side supply distribution.

  3. Santiago Southern Corridor Hub — Chile
    Long-range convoy operations, mountain passes, wildfire response, and southern regional staging.

  4. Buenos Aires Atlantic Distribution Hub — Argentina
    Atlantic cargo transfer, agricultural supply movement, and southern relief operations.

  5. São Paulo Industrial Support Hub — Brazil
    Heavy equipment coordination, industrial supply integration, and major urban response support.

  6. Manaus Amazon Access Hub — Brazil
    Jungle-edge logistics, river-to-road transition support, and remote community sustainment.

  7. Quito High-Elevation Response Hub — Ecuador
    Volcanic disaster response, highland mobility, and western Andean emergency support.

  8. Georgetown Caribbean-South America Link Hub — Guyana
    Coastal relief staging, Caribbean support linkage, and northern Atlantic supply transfer.

​

Europe

  1. London Western Europe Coordination Hub — United Kingdom
    Regional liaison, port-linked distribution, and strategic planning support.

  2. Paris Continental Relief Hub — France
    Western European convoy coordination, rail-road supply integration, and urban crisis response.

  3. Berlin Central Logistics Hub — Germany
    Continental ground movement, heavy vehicle maintenance, and multinational coordination.

  4. Warsaw Eastern Corridor Hub — Poland
    Eastern European relief routes, refugee movement support, and frontier logistics.

  5. Rome Mediterranean Support Hub — Italy
    Southern European staging, Mediterranean disaster response, and coastal logistics.

  6. Madrid Iberian Response Hub — Spain
    Wildfire response, western Mediterranean staging, and North Africa transfer support.

  7. Oslo Northern Resilience Hub — Norway
    Arctic-adjacent logistics, tunnel operations, cold-weather mobility, and northern infrastructure support.

  8. Athens Balkan-Mediterranean Hub — Greece
    Earthquake response, island support coordination, and southeastern European staging.

​

Africa

  1. Cairo North Africa Command Hub — Egypt
    Desert logistics, regional coordination, canal-linked distribution, and North/East Africa staging.

  2. Casablanca Atlantic Africa Hub — Morocco
    Western North Africa relief movement, Atlantic cargo transfer, and desert-edge operations.

  3. Lagos West Africa Distribution Hub — Nigeria
    Dense urban response, port logistics, regional supply distribution, and emergency relief staging.

  4. Nairobi East Africa Operations Hub — Kenya
    Regional humanitarian support, inland convoy coordination, and disaster-response staging.

  5. Addis Ababa Horn Coordination Hub — Ethiopia
    Mountain and highland logistics, multinational relief liaison, and famine-response coordination.

  6. Kinshasa Central Africa Access Hub — Democratic Republic of the Congo
    Interior access, jungle-edge logistics, remote transport coordination, and field engineering support.

  7. Johannesburg Southern Africa Hub — South Africa
    Heavy equipment staging, industrial support, regional convoy operations, and southern crisis response.

  8. Dakar Atlantic Relief Hub — Senegal
    Western coastal response, trans-Sahel supply routes, and international relief transfer.

​

Asia

  1. New Delhi South Asia Command Hub — India
    Regional command coordination, mass evacuation planning, monsoon response, and inland logistics.

  2. Mumbai Western India Distribution Hub — India
    Port-linked supply movement, industrial cargo transfer, and coastal disaster response.

  3. Bangkok Southeast Asia Relief Hub — Thailand
    Flood response, jungle-edge logistics, regional relief staging, and ASEAN coordination.

  4. Singapore Strategic Transfer Hub — Singapore
    High-efficiency cargo transfer, maritime-to-land supply coordination, and multinational logistics.

  5. Jakarta Archipelago Support Hub — Indonesia
    Earthquake, tsunami, volcanic response, and island-to-land staging coordination.

  6. Manila Pacific Disaster Hub — Philippines
    Typhoon response, island relief transfer, and Pacific humanitarian staging.

  7. Seoul Northeast Asia Coordination Hub — South Korea
    Regional readiness, technology support, and high-density urban operations.

  8. Tokyo Resilience Hub — Japan
    Earthquake preparedness, advanced logistics coordination, and urban infrastructure recovery.

  9. Beijing Northern Asia Liaison Hub — China
    Large-scale coordination, inland distribution support, and continental response planning.

  10. Chengdu Western China Relief Hub — China
    Mountain access, interior supply movement, and post-Soltan reconstruction corridor support.

  11. Almaty Central Asia Route Hub — Kazakhstan
    Long-range overland supply movement, rail-road transfer, and Eurasian interior logistics.

  12. Dubai Middle East Logistics Hub — United Arab Emirates
    Desert convoy operations, air-cargo transfer, fuel coordination, and regional relief staging.

  13. Istanbul Eurasian Gateway Hub — Türkiye
    Europe-Asia transfer point, earthquake response, and multi-region convoy coordination.

​

Oceania and Polar Support

  1. Sydney Oceania Operations Hub — Australia
    Regional disaster response, Pacific coordination, wildfire support, and southern logistics.

  2. Darwin Northern Australia Staging Hub — Australia
    Tropical operations, expeditionary staging, and Southeast Asia/Pacific support.

  3. Christchurch Antarctic Support Hub — New Zealand
    Cold-weather logistics, Antarctic research-support coordination, and southern emergency staging.

​

Command Structure

TERRAGUARD is led by General Nathaniel Elias Stone, founding Commander of TERRAGUARD. From Ground Zero Facility, Stone oversees global land operations through a layered command structure designed for rapid deployment, regional autonomy, and disciplined accountability.

​

Primary Command Elements

TERRAGUARD Headquarters Command
Directs global planning, mission authorization, command policy, international coordination, and major crisis-response oversight from Ground Zero Facility.

​

Ground Zero Operations Center
Maintains real-time operational tracking of active convoys, personnel movements, disaster zones, supply routes, field teams, aircraft loading, and emergency distribution networks.

​

Regional Operations Commands
Coordinate continent-based hub networks, national liaisons, convoy routes, staging bases, and regional mission readiness.

​

Convoy and Transportation Command
Manages land transport vehicles, armored relief trucks, fuel carriers, mobile shelters, all-terrain vehicles, road convoys, and vehicle deployment cycles.

​

Disaster Response and Relief Command
Coordinates food, water, shelter, medical supplies, emergency power, field kitchens, temporary camps, and civilian support distribution.

​

Engineering and Infrastructure Command
Supports route clearance, bridge repair, field construction, emergency power, water systems, temporary shelters, and infrastructure stabilization.

​

Fleet and Motor Pool Command
Maintains TERRAGUARD vehicles, aircraft support equipment, repair facilities, spare parts, field maintenance units, and readiness inspections.

​

Security and Route Protection Command
Secures relief corridors, staging sites, supply depots, convoy routes, and personnel operating in unstable or hostile environments.

​

International Liaison and Civil Coordination Office
Works with national governments, local authorities, relief agencies, GUARD divisions, military partners, and civilian organizations.

​

Training and Readiness

TERRAGUARD personnel are trained to operate in crisis environments where normal systems have failed. Every member is expected to understand the connection between logistics, security, humanitarian relief, and public survival.

​

Core Training Areas

  • Convoy operations and route discipline

  • Vehicle loading, staging, and movement control

  • Disaster-zone safety

  • Emergency supply distribution

  • Field shelter setup

  • Civilian evacuation support

  • Relief corridor security

  • Basic engineering support

  • Communications and field reporting

  • Hostile-environment awareness

  • Anti-corruption supply-chain practices

  • Joint GUARD operations

  • National and international coordination

  • Field ethics and civilian protection

  • Post-war recovery support

​

Readiness Standards

TERRAGUARD maintains high readiness through:

  • Regular convoy exercises

  • Vehicle fleet inspections

  • Rapid deployment drills

  • Emergency loading exercises

  • Multi-hub logistics simulations

  • Field communications testing

  • Disaster-response rehearsals

  • Engineering-response scenarios

  • Joint exercises with other GUARD commands

  • After-action reviews following every major operation

​

TERRAGUARD’s readiness model is built around General Stone’s belief that a delayed convoy can become a lost community.

​

Operational Philosophy

TERRAGUARD’s operational philosophy is built on General Stone’s core principle:

War is not won when the enemy stops firing. War is won when people can live again.

​

This philosophy shapes every TERRAGUARD mission. The command does not treat logistics as a background function or humanitarian relief as a secondary task. TERRAGUARD sees food, water, shelter, medicine, transportation, roads, power, and communications as survival systems that must be protected and restored.

​

TERRAGUARD personnel are trained to move with urgency, act with discipline, and remember that every crate, vehicle, route, bridge, and shelter represents lives depending on them.

​

TERRAGUARD Operating Beliefs

  • Civilian survival is part of the mission.

  • Relief must move even when politics delays.

  • A convoy is a promise.

  • Supplies are useless if they do not reach people.

  • Security without restoration is incomplete.

  • Corruption in a relief chain is stolen survival.

  • Field commanders must see conditions firsthand.

  • The ground must hold.

​

TERRAGUARD exists for the moment after the explosion, after the flood, after the invasion, after the collapse, and after the world begins to look away.

​

When people are trapped, TERRAGUARD opens the route.

When communities are cut off, TERRAGUARD moves the convoy.

When systems fail, TERRAGUARD builds the support.

When the battle ends, TERRAGUARD keeps going.

​

UNIFORMS

GUARD UNIFORMS - TERRAGUARD-small.jpg

FACILITIES

TERRAGUARD HQ - Ground Zero Facility, Nevada USA

bottom of page