Incident Resolution Team
Overview
An Incident Resolution Team — referred to in operational shorthand as an IRT — is a corporate covert deployment unit that arrives at belt stations under the guise of a TSRA Oversight and Safety Authority field inspection. On the surface, the cover is procedurally convincing: TOSA field deployments are legitimate instruments of belt safety governance, authorized whenever a station reports a recordable incident. An IRT exploits that authorization framework by assuming a TOSA field-unit designation, presenting genuine-seeming TOSA authorization codes, and arriving in a transport equipped for sustained operations rather than routine administrative review.
The IRT exists at the intersection of corporate liability management and deniable enforcement. When an incident produces evidence, witnesses, or data that a safety inquiry would expose rather than contain, an IRT is the instrument dispatched to close the gap between what happened and what will be recorded. Its personnel are not safety inspectors. They do not write reports.
Details
IRTs deploy in a standard six-person configuration — the minimum headcount capable of covering docking access, internal corridors, communications infrastructure, and key personnel simultaneously, and the maximum that can be credibly carried on a TV-class transport while maintaining the fiction of a lean inspection team. The transport itself runs large: rated for ten at pressure, carrying six, with the remaining capacity filled by equipment listed on the manifest only as “inspection instrumentation.” By contrast, routine TOSA field deployments use two or three personnel. Anyone with experience reading military transit manifests will recognize the configuration immediately.
IRT deployments are unannounced. They do not appear in TOSA’s scheduled inspection calendar, file no advance notice with station management, and transmit no pre-arrival coordination. Their first communication with a station is the docking request itself — a marked departure from standard TOSA protocol, which schedules inspections weeks in advance. The authorization codes embedded in the corporate relay header pass automated verification against TOSA’s public schema, but originate from corporate-issued credentials rather than TOSA’s own dispatch system. This discrepancy is visible in the approach display data to anyone who knows what standard credentials look like.
IRT personnel carry no unit patches, rank identifiers, or corporate insignia beyond the TOSA field-unit designation required for docking. Their individual identities, if traceable at all, resolve through several layers of contract security firms before reaching anything directly attributable to a corporation. The team’s operational scope is bounded by the station and the specific liability event it was dispatched to close: once docked, the corporation’s posture has shifted from inquiry to resolution — a distinction with significant practical consequences for anyone present at the station.
Significance
Within the corporations, IRTs are a recognized instrument of the liability management apparatus, but their existence appears in no document accessible to contract workers, station personnel, or Terran regulatory bodies. They represent a tier of corporate enforcement above standard security field units, deployed specifically when ordinary investigation and embargo have failed to contain a situation. An IRT is not dispatched in response to a safety incident — it is dispatched in response to a liability event: one where the preliminary phase has already concluded that normal channels cannot resolve what the incident produced.
The IRT carries meaningful limitations. Its cover provides docking authorization, not invisibility — station personnel will notice that a six-person team moving with operational economy does not behave like an inspection unit. Its TOSA designation authorizes access relevant to the reported incident, not arbitrary station lockdown or pursuit of personnel who have already departed. If the authorization discrepancy is identified, logged, and transmitted to a party outside corporate reach, the team loses its operational legitimacy entirely. And if the material it was dispatched to contain has already left the station, the IRT cannot follow — pursuit into open space requires different instruments and a different phase of corporate response altogether.
The IRT’s existence signals something larger about how the corporations operate across the belt. They maintain instruments specifically designed to resolve situations that cleverness and patience have already failed to contain — not bureaucratic antagonists to be outmaneuvered, but organizations capable of moving from inquiry to closure with very little warning.