Astraventus Codex

Properties1
tagseventlog, minorevent, frontierscouting, combatdoctrine, demisefacingfrontier, indomitable, threatclassification, manabeast, demonincursion, scoutreporting

Frontier Threat Classification Standard

File Classification

Document Type: Event Log
Event Designation: Frontier Threat Classification Standard
Alternate Designations: Owl Classification Standard, Running Report Standard, Frontier Contact Sorting Procedure
Estimated Date: During Incursion Escalation
Location: Demise-facing frontier survey zone and Indomitable scout relay offices
Associated Factions: Indomitable, frontier scouts, local trail wardens, Indomitable frontier liaison office
Associated Concepts: Mana-Beast, Mana-Mutated Wildlife, Demon Incursion, Mixed Incursion Horde, scout reporting, threat classification
Event Type: Policy Change / Field Doctrine Standardization
Current Status: Confirmed
Historical Weight: Institutional

Summary

Frontier Threat Classification Standard was a scout-reporting procedure developed after a scouting survey near a mana-beast nest turned into a running withdrawal.

Owl Squad had been assigned to survey a suspected mana-beast nesting site near the Demise-facing frontier. The survey became a pursuit when Owl 2 stepped on a particularly loud dry branch and alerted the nest. While retreating from a horde of hostile mana-beasts, the squad continued sending short reports through field relay code.

The reports were messy, incomplete, and sent under panic conditions, but they separated threat category, count, movement direction, behavior, and confirmation level more clearly than many calmer reports from earlier incidents.

After review, Indomitable frontier offices adapted the format into a standard that could be used by scouts while moving, hiding, wounded, or under pursuit.

Event Description

Before the standard was adopted, frontier reports often mixed local vocabulary with battlefield fear. Scouts, farmers, trail wardens, and militia units used terms such as “demon beast,” “mutant animal,” “frontier monster,” and “incursion sign” with little consistency.

This caused serious response problems. A confirmed demon incursion required a different military response from a mana-beast migration, a contaminated wildlife surge, or a mixed horde moving through damaged terrain. Wrong wording could send heavy response teams to the wrong place or delay action against a real breach.

Owl Squad had already been involved in the Demise Trail Confusion, where altered wildlife was initially reported as a demon incursion. That earlier incident showed the need for clearer field language, but the first proposed reporting revisions were too slow and too formal for scouts in danger.

The later nest survey forced the issue.

The squad was sent to confirm whether repeated animal disappearances and soil disturbances near a Demise-facing trail were caused by a single large predator, a mana-beast nest, or early incursion movement. The site appeared quiet during the first approach. The team identified disturbed bedding pits, gnawed bone piles, shed growth plates, and multiple narrow exit routes hidden beneath brush and broken stone.

The survey ended when Owl 2 stepped on a dry branch.

The sound carried through the hollow ground beneath the nest and triggered immediate movement. The squad was pursued by a horde of mana-beasts before they could complete a full survey count.

During the withdrawal, Owl Squad could not send long descriptions. They instead transmitted short classification bursts:

  • threat type
  • certainty level
  • estimated count
  • movement direction
  • observed behavior
  • whether any true demon traits were confirmed
  • whether local wildlife traits were still recognizable
  • whether civilian routes were threatened

The format was crude, but it worked. Command received enough information to avoid declaring a full demon incursion while still treating the horde as an urgent threat.

The resulting response was smaller, faster, and better matched to the situation.

Cause or Trigger

The immediate trigger was the failed quiet survey of a mana-beast nest.

The broader cause was a recurring weakness in frontier reporting. Scouts often saw dangerous altered organisms under poor visibility, while injured, afraid, or moving quickly. Formal classification language existed in laboratory and inspection settings, but it was too slow for field contact.

The nest pursuit proved that a useful report did not need perfect certainty. It needed to separate what was confirmed from what was suspected.

The standard kept that distinction at its center.

A scout did not have to identify every creature correctly while running. They had to report the difference between:

  • confirmed demon traits
  • suspected demon traits
  • confirmed mana-beast traits
  • recognizable local animal traits
  • unknown altered organisms
  • mixed groups
  • direction of movement
  • immediate civilian risk

This allowed command to choose a response without waiting for a complete biological assessment.

Immediate Outcome

Confirmed immediate outcome:

  • Owl Squad survived the pursuit and reached a secondary trail relay point.
  • The suspected site was confirmed as an active mana-beast nesting zone.
  • The threat was classified as a mana-beast horde with no confirmed true demon organisms.
  • Local civilian routes were closed before the horde reached outer farms.
  • Indomitable frontier offices reviewed the squad’s short-form relay messages.
  • The relay format was adapted into a formal field reporting standard.
  • Scouts were trained to report confirmation level before dramatic threat labels.

Later Relevance

Frontier Threat Classification Standard became a practical reporting tool for scouts, trail wardens, and frontier liaison units.

Its value came from speed. The standard could be used in calm surveys, but it was designed for conditions where scouts had only seconds to report before moving again.

The standard discouraged single dramatic labels and required category separation. A report could mark a creature as dangerous without declaring it a demon. It could mark a group as a horde without assuming incursion coordination. It could request urgent response while preserving uncertainty.

Common report fields included:

  • Category: demon, suspected demon, mana-beast, mana-mutated wildlife, ordinary wildlife, mixed, unknown
  • Confidence: confirmed, suspected, unconfirmed
  • Count: exact, estimated, many, horde
  • Behavior: hunting, fleeing, nesting, coordinated, disorganized, territorial, migrating
  • Movement: direction, speed, route, civilian path risk
  • Traits: impossible anatomy, local animal base, mana growths, environmental distortion, speech or command behavior
  • Response Need: observation, containment, evacuation, strike team, incursion response

The standard later appeared in scout manuals as a reminder that a useful report is not the most complete report. It is the report that lets command act correctly before the situation worsens.

List concepts this event demonstrates or supports.

Graph View

Backlinks