Overview

Vanguard Unit

AX.GM.07.03

The Vanguard Unit is a classified special operations element operating under a Defense Intelligence designation that places it outside normal military command structure. Where the BUA investigates, the Vanguard acts. Its mandate is direct: identify, engage, and neutralize supernatural threats assessed as presenting immediate danger to civilian populations, national security assets, or personnel with classified knowledge of the hidden world.

The Vanguard does not make detailed records. It does not cultivate sources or build cases. It receives threat assessments, deploys, and resolves situations. The resolution tends to be terminal.

Within the hidden world, the Vanguard has a specific reputation: it is effective, it is fast, and it does not distinguish well between threats and bystanders once it is on-site. Hidden-world communities that have had Vanguard contact, most of the older ones have, at some point, maintain the kind of wariness toward the organization that comes from knowing it views them as potentially relevant to a threat assessment rather than as parties with their own standing.

The Vanguard is, by design, not a place for nuance. Operators who develop significant investment in the complexity of the hidden world tend to leave or to become problems for their command structure.

History

The Vanguard was assembled in the mid-1980s as the government's understanding of the hidden world's more dangerous elements exceeded what federal law enforcement, specifically the BUA, was designed to handle. The founding cases are classified, but the pattern of incidents in the late 1970s that preceded the Vanguard's establishment included several events where BUA investigators were killed by entities they were attempting to document rather than neutralize.

The early Vanguard was a small experimental element within a classified special operations program. It drew on existing special forces training and added what its first commanders called "threat-specific protocol development", field-tested approaches to entities that did not respond to conventional engagement methods. The early operators learned what worked through experience that was expensive in personnel.

Current doctrine is more developed. The Vanguard has accumulated sixty years of operational data on threat categories, engagement approaches, and the specific material and technique requirements for permanent resolution. It does not share this doctrine freely, but elements of it have leaked into hunter community practice over decades.

The Vanguard's current size and organizational structure are classified. What is known to outside parties is that it exists, that it responds to threat designations, and that its operational tempo has increased significantly over the past decade.

Structure

The Vanguard operates in teams, small, specialized units designed for specific threat categories. Teams are not publicly identified; operators use designation numbers rather than names in official communications.

Team Structure:

• Team Lead, senior operator; tactical authority in-field; answers to command only
• Operators, four to six per team; cross-trained in threat-specific engagement
• Specialist, attached per mission; tradition access or specific technical capacity
• Support, logistics, medical, exfil; not combat-rated but field-experienced

Command Structure:

• Program Director, political/military appointee; strategic oversight, not operational
• Operations Chief, manages team deployment and threat assessment intake
• Intelligence Cell, receives threat assessments from BUA and other sources; produces targeting packages
• Doctrine Section, updates engagement protocols based on operational feedback

The Vanguard does not have a public-facing structure, a congressional oversight relationship, or a budget line that appears in any document accessible through normal channels.

Operations

Vanguard operations follow a targeting-and-deployment model: threat assessment comes in (from the BUA, from internal intelligence, or from other sources), operations staff evaluates and generates a targeting package, a team is assigned and briefed, the team deploys and resolves.

Engagement doctrine: Vanguard operators are trained for lethal engagement with nonhuman threats. The doctrine prioritizes rapid resolution over documentation. Evidence is collected when practical and eliminated when documentation presents a security risk. Civilian witnesses are managed through a dedicated support function that has more in common with BUA procedure than operators generally acknowledge.

Threat-specific material: The Vanguard maintains stockpiles of materials that don't appear in standard military logistics: silver-core ammunition in several calibers, blessed ordnance, cold iron-edged close combat weapons, salt canisters in dispersal-round and hand-charge configurations, consecrated items from several religious traditions. Specialists with tradition access are attached to teams as tactical assets for engagements where material approaches are insufficient.

Extraction and cleanup: The Vanguard has a dedicated support element whose job is to make sure there is no verifiable record of what happened at an engagement site. This element has a significant degree of operational latitude and is not always in sync with what the field team determined actually needed to happen. Operators who have worked with the cleanup element develop opinions about institutional priorities.

Relations

Bureau of Unusual Affairs: The institutional relationship is formally cooperative and practically adversarial. The BUA wants cases documented; the Vanguard wants cases resolved. When both agencies respond to the same incident, jurisdiction is the first fight and methodology is the ongoing argument. Individual operators and agents sometimes work well together. The organizations do not.

Order of the Warden's Flame: The Vanguard has contracted with the Order for specialist support on engagements involving Shadow entities. The relationship is transactional and managed with care, the Order has its own operational standards and will not participate in engagements it assesses as disproportionate. The Vanguard finds this constraint frustrating. The Order finds the Vanguard's casualty tolerance for hidden-world bystanders troubling.

Obsidian Solutions: The Vanguard uses Obsidian for threat assessment intelligence and occasionally for logistics support in areas where federal infrastructure is impractical. Obsidian knows the Vanguard's capabilities well enough to be a useful partner and uncomfortable if it chooses to be. The relationship is maintained carefully from both sides.

The Bloodline Courts, The Hollow Market: The Vanguard has a file on both. Neither is currently a primary threat designation, but both are classified as organizationally monitored. Members of either organization who find themselves in proximity to a Vanguard operation should consider what their threat profile looks like from an external assessment.

The Compact of Lines, The Threshold Society, The Sovereign Circle: The Vanguard has files on all three. The Compact is monitored as the primary governance structure for a lineage the Vanguard regularly deploys against and alongside, its Skinchanger operator population makes the Compact's politics operationally relevant. The Threshold Society is monitored as an inter-faction arbitration body whose reach into Vanguard-relevant conflicts the program has not fully mapped. The Sovereign Circle is monitored with particular attention: an organized community of Shadow-Bound Marked practitioners whose relationship with their compact sources is managed rather than reactive presents a different operational variable than isolated Marked individuals. None of the three is currently a primary threat designation.

Secrets

The Vanguard's doctrine section maintains engagement protocols for every significant threat category in its operational history. It also maintains protocols for several categories that have not been activated, threat types assessed as possible future concerns. One of those protocols covers organized Dhampir political structures. Another covers what happens when a Light-Bound Marked entity is assessed as a threat.

The Vanguard has lost operators to hidden-world recruitment. Not many, the screening is designed to prevent it, but some. Operators who go native, as it is internally described, are not pursued aggressively unless they take classified knowledge with them. The ones who left quietly are left quiet.

The current Operations Chief has a personal assessment, not part of any official document, that the Vanguard's operational tempo increase over the past decade is not evidence of a worsening threat environment. It is evidence of something else. The assessment is four pages, written by hand, and kept in a location that is not accessible through normal Vanguard records systems.

Plot Hooks

• A Vanguard team has gone dark on a mission. The Operations Chief wants the situation resolved before anyone outside the program notices. The resolution may require finding out what the team found.
• An operator has filed an abort report citing "bystander assessment inconsistent with threat designation." The Operations Chief's review of the abort report is currently pending. The operator is not currently assigned to active missions.
• The Vanguard's doctrine section has flagged an emerging pattern: three separate incidents in the past six months share a signature that matches no existing threat category. The targeting package hasn't been built yet because the category doesn't exist in the system.
• A retired Vanguard operator has begun providing tactical support to a hidden-world community the Vanguard has classified as organizationally monitored. The operator took classified knowledge with them. The Vanguard has noticed.