WELCOME

Home of the Steel Wolves Squadron

The Steel Wolves Squadron is a Pack. A pack of commanders participating in system building, background simulation, exploring, combat (winged combat zones or bounty hunting), minining, pirate hunting, engineering and protecting the bubble from thargoids is our passion. The Pack enjoys the journey as well as the destination. And the entire Pack will Howl when we get there! We welcome all commanders from early, mid and end game experiences. Join The Pack and tackle the galaxy with everything it has to offer. Let's build the Federation to new heights and never look back. Feel free to join our Discord and fly dangerous!

ARTICLES OF CONFEDERATION

Article:

Article I: Membership

Section 1a: Definition of Membership

  1. Membership in the Confederacy of Federal Systems (ConFed) grants each member participation to a defensive pact and permits the squadron to make request of the Council for offensive actions against non-member squadrons.
  2. Membership in ConFed allows for one member of a squadron\’s command staff to have a seat on the Council for voting rights.
  3. Pledges in ConFed are granted participation to a defensive pact, but are not granted voting rights until the squadron is ratified to membership in Section 1c.

Section 1b: Independence

  1. Each member reserves the right to remain a Sovereign Federal Faction
  2. Members agree to maintain open communications with all ConFed members in order to send or receive Reinforcement Request, Distress Calls, and other Diplomatic Transmissions.
  3. Members reserve the right to deny request if all respective forces are preoccupied in other engagements.
  4. Members reserve the right of Command over any and all of their respective forces in times of Joint Operations.
  5. Members reserve the right for individual KoS orders.

Section 1c: New Members and Pledges

  1. It is the responsibility of the Council to evaluate the candidacy of all interested parties to ensure that all membership or pledge requirements are properly met, or likely to be met within a reasonable and appropriate amount of time.
  2. All members and pledges must be voted on in the affirmative by 2/3 of the Council.
  3. Incoming parties must spend a minimum of (2) weeks provisionally as a Pledge.
  4. Only Federation aligned squadrons may merit full membership status within ConFed. Factions must not be banned or designated as traitors. (Gankers, griefers, Fed aligned but supporting Imperial or Independent Factions)
  5. Federation supporting squadrons (independent aligned) may merit pledge status only within ConFed. Factions must not have supported or be an enemy in the last 6 months. Members must maintain a total of (10) pilots to retain membership status

Article II: Membership

Section 2a: Council

  1. Participating member-factions will receive no more than (1) vote in the Council regardless of relative size and power
  2. Member to Member merges will result in the loss of the merging party\’s seat on the Council.
  3. Council shall mediate any and all cases of dispute between any combination of Members and Pledges through a 2/3s voting process. The resolution will be binding on both parties and enforced by the entirety of ConFed.

Section 2b: Tribunal Court

  1. Voting on placing of sanctions defined in Article VI.
  2. Members may appeal membership status or sanctions in a case where new information has become available.

Article III: Communications

Section 3a: Shared Intelligence

  1. ConFed offers and expects shared tactical intelligence data regarding alien threats, enemy movements, Federal operations, and joint squadron missions to flow between members of the coalition.

Section 3b: Requests for Aid

  1. Members and Pledges can request aid from ConFed in the forms of BGS assistance, security forces, anti-xeno operations, or joint federal operations.
  2. Members may request Priority Assistance. An agreed fiscal payment among the participating squadrons for a guaranteed amount of assistance achieved during an operation. Priority Assistance provides the ability to pull forces for help over other objectives. This agreement is mutual between all parties in the coalition.
  3. Members reserve the right to remain neutral and/or refuse to participate in requests or wars. Due to the nature of this coalition, a reason for refusal may be requested of any member.
  4. ConFed reserves the right to operate on behalf of the Federation.
  5. Any Federal conflict shall not be ignored by ConFed forces unless preoccupied in other conflicts.

Section 3c: Federal Defense

  1. ConFed offers a mutual defense pact from both enemies both foreign or domestic.
  2. Members reserve the right to deny an attack on another federal faction if deemed unappropriate.

Section 3d: Embassies

  1. Members shall maintain an active embassy within ConFed to allow communications among member factions

Section 3e: Pilot Exchange Program

  1. ConFed offers a mutual pilot exchange program. This allows all members to send pilots who don’t meet the individual squadron requirements to other members within the coalition before being dismissed from ConFed.

Article IV: Reverence for Life

Section 1:

  1. ConFed condemns the unnecessary destruction of life and property.
  2. Members reserve the right to treat unidentified pilots in their respective space at their discretion.
  3. Any negative action or potential war brought on said squadron can be brought to the Council under Article III, Section 3b.
  4. Unidentified pilots can be interdicted and instructed to leave if found in ConFed or Federation space.
  5. Non-combatant ships will be given fair warning in advanced to prevent any unneeded bloodshed, ill-planned, under-prepared, or non-staged conflict that may result in negative actions.

Article V: Agreements

Section 5a: Trade Agreements

  1. Members reserve the right to form and maintain healthy trade relationships with non-ConFed squadrons.

Section 5b: Alliances

  1. Members reserve the right to form independent alliances with other squadrons as long as they don’t violate Article 1, Section 1c.
  2. ConFed is not responsible or liable to honor alliance agreements made among individual member squadrons and non-ConFed squadrons.
  3. In the event of ConFed formed alliances, the alliance has to be ratified with a 2/3 vote of the Council.

Article VI: Sanctions

Section 6a: Non-Permissible Behaviors

  1. Members shall not declare collaborative wars with out a valid reason as definite in Article VII.
  2. Members shall not conduct offensive operations against another squadron from Private Group or Solo game modes.

STEEL WOLVES AEGIS TACTICAL LORE

Chapter:

CHAPTER 1: Backstory of the Legion

In the year 3303, following the increase of border confrontations and political strife between the Federal and Imperial factions, a group of soldiers and support personnel deserted the Federal Navy. These men and women were disillusioned with the events within the Federation and chose to navigate the stars into the Alliance controlled systems in the hopes of establishing a new home where the Federation ideals could prosper without the corruption of power, they had witness. At their head. Admiral Ferox Worgen along with a pool of talented officers formed their comrades into a cohesive unit and family. The Steel Wolves Legion was decided on as a name and Khernidjal system as a potential new home.

Khernidjal system started off as an ideal home for the Legion. Having formed as a paramilitary organization, the Legion began to gain influence among the other governments within the system. Over the course of a year, the men and women of the Legion integrated into the population. They soon took control of the system’s political establishments in an election against the Alioth Independents.

The Legion’s life in Khernidjal was short lived. With the seizing control of the system, they had brought the attention of the Alioth Council. The Alioth Council was the ruling body in the sector of space and having a system come under federal influence alarmed them, especially being so close to the seats of power within Alliance space. The Alioth Council began operations to drive the Legion out of Alliance controlled space. With the number of resources deployed against them, Ferox made the hard choice of uprooting his people. This of course was a massive undertaking with the fact the Legion had integrated into the local population.

Chapter 2: Formation of the Steel Wolves Aegis Tactical

Year 3304

Once again turning to a wandering society, the Legion turned to selling its services as both a military unit and using its small fleet of carriers to help retrofit local ships in the systems they passed through. Both ventures in turn helped fill the Legion’s coffers and keep the fleet going. Many local governments though were hesitant to use the Legion’s services, being naturally distrustful of a wandering Federal fleet with no official standing within the Federation.

With the increase in border tensions amongst the superpowers as well as incidents with the Thargoids, the Galactic Council saw an opportunity in offering their military expertise and precision in retrofitting local faction and independent ships as well as transportation and security services. Thus, the Steel Wolves Aegis Tactical corporation was born. Samuel Gilmore was appointed director while Ferox Worgen took on the role of CEO. Samuel was responsible for handling the corporation’s business operations and Ferox continued directing the paramilitary arm.

Several of the fleet’s carriers were retrofitted for the new corporation’s use, allowing the Steel Wolves to deploy the carriers along the fleet’s progression. This allowed the local systems to acclimate to the Steel Wolves presence before the fleet arrived. As the business grew, it became clear that the Steel Wolves needed to find a base of operations. They needed to have larger facilities for manufacturing goods for the shipyards as well as retrofit facilities.

Chapter 3: Founding of a Home System

Year 3305

The Steel Wolves first tried to establish a headquarters in the Binar system. The system’s industrial sector was weak, allowing the purchase of facilities to run on the cheaper side. It was also a prime location being in a contested region between the Federation and Imperials. Unfortunately, with the turmoil among the major factions, the Steel Wolves couldn’t incorporate within the local governments.

Year 3306

The decision to dispatch long range scouts was made to find a system both suitable for the civilian population and had the infrastructure to support growth of the corporation. The HIP 27986 system was discovered on the outer rim of colonized space. The local region was more ideal for the Steel Wolves’ needs with a lot of industrial, extraction, and refinery economies. The system also had the added appeal of being away from the political shenanigans and largely loosely organized groups of independent factions.

By the time the fleet was able to arrive in HIP 27986, the Steel Wolves’ coffers were well stocked having continued business as they traveled the 190 lightyears from Binar. With the surplus of credits, the corporation aspect of the Steel Wolves began investing or buying facilities to establish the corporation’s headquarters while the fleet’s personnel integrated into the local population. It didn’t take long for Samuel to establish himself in the political circles within HIP 27986. With the backing of Ferox and the rest of the paramilitary arm, the Steel Wolves were able to establish control over the primary assets within the system as well control of HIP 27986 itself.

Chapter 4: Year 3307-Present

With the growth of the corporation and its popularity within the political spheres, the Steel Wolves began to expand their reach into neighboring systems. The process was a slow one as the corporation invested in various local industries before establishing a branch office in the new system. Once the branch office was established, then the political advisors began inserting themselves into each systems’ political spheres. With the wealth and security forces that the Steel Wolves brought with them, the systems’ economic and security prospered. The federal ideals without the political machinations also appealed to the largely independent civilian populations.

Systems fell under the Steel Wolves control rapidly as the corporation continued to grow. It wasn’t until they expanded operations into the Hyades Sector HW-W d1-64 system that the Steel Wolves met solid resistance. The d1-64 system was under control of a confederacy of pilots known as the Brazilian League of Pilots. The first confrontation between the Steel Wolves paramilitary and the Brazilian’s pilots made it clear that a direct conflict would not turn out in favor of the corporation.

Instead of choosing a long-drawn-out conflict that would cost lives and resources, the ambassadors traveled to Njorog. Weeks after establishing an embassy on Njorog, the Steel Wolves’ ambassadors were able to form a non-aggression treaty with the Brazilian League of Pilots that also established borders between their much larger faction and the Steel Wolves growing faction.

Near the end of 3307, the Steel Wolves hit their first major expansion milestone with the establishment of the branch office in Senocidi.

Year 3308

Year 3308 saw the Steel Wolves continuing to expand the reach of their influence to other systems. The year was rather peaceful until the events in HIP 22460. With the release of the Proteus Wave, Thargoids began ramping up their attacks on populated systems. Also deep space research stations began picking up multiple anomalies heading for the Bubble. It wasn’t till near the end when the Thargoid motherships landed, with Taranis being right on the doorstep of Steel Wolves space. The Thargoid fleets that came from Taranis instantly overran the Steel Wolves security forces in 5 Mu Leaporis and Popongo systems. The initial ferocity of the Thargoid attacks put the Steel Wolves on the defensive and was the start of a bloody war.

Year 3309

This was a bloody year for the Steel Wolves. The Thargoids were constantly assaulting systems within Wolves space, though the only systems to fall were the original two during the initial onslaught. While the Steel Wolves were able to defend their systems, it wasn’t until the middle of the year that an agreement was reached with the Anti-Xeno Initiative. The arrival of AXI’s megaship into HIP 27986 signaled a change in the tides against the Thargoids coming from Taranis. With the additional manpower provided by AXI, the Steel Wolves were able to adjust their focus from defense to assault. This change in focus led to the Steel Wolves being able to liberate other systems.

Year 3310

It was early in the year 3310 that the threat of Taranis was finally extinguished. With the destruction of the Titan, the Steel Wolves turned to humanitarian efforts in rebuilding the devastated systems surrounding Wolves Space. Their efforts lent to the increase of Wolves space as system governments chose to fall under the administration capabilities of the Steel Wolves. The culmination of the Steel Wolves efforts came in the liberation of Gliese 3258, one of the last bastions of the Federation on the rim of the Bubble. During this year, the Steel Wolves helped transform the loosely organized Orion Spur Federation Association (OSFA). The partnerships formed amongst the other organizations that made up the OSFA proved to form a potent coalition. This was shown in the defense of b2 Carinae against the combined might of Imperial encroachment. The battle for control of the system had OSFA and their Federation allies hand the Imperial forces a crushing defeat. After four consecutive days of intense fighting, the Federation moves forward in "Victory".