Ash Corridor
Ash Corridor
Embedded Files
A Korriban command-accountability story about casualties, delayed action, disputed coordination, and responsibility that remains unresolved.
Ash Corridor is an active Imperial accountability story centered on a failed Army operation on Korriban in 3621 BBY.
The surviving record establishes casualties and serious failures involving coordination, communications, response timing, casualty handling, and evidence custody. Medical reconstruction also identifies losses that were preventable or potentially preventable. What the evidence does not yet establish is one uncontested operational sequence or one person who can absorb responsibility for the entire failure.
That uncertainty is central to the story. Ash Corridor asks how Imperial command should distinguish individual error from defective systems, how earlier misconduct should affect judgment of a later disputed incident, and whether commanders can correct serious weaknesses while remaining responsible for personnel and infrastructure that still have to function around them.
Status — Active
Story Type — Military Accountability / Investigative Story Arc
Participation — Coordinate First
Historical Event — 3621 BBY
Primary Setting — Korriban, particularly Army-administered security, movement, casualty, logistics, communications, and command infrastructure
Information Access — Restricted. This page is player-facing; detailed casualty findings, disciplinary conditions, command records, medical evidence, and investigative conclusions are not automatic in-character knowledge
The Ash Corridor Incident
The Ash Corridor Incident
Ash Corridor failed during an Imperial Army operation on Korriban in 3621 BBY.
The surviving evidence points to several interacting failures rather than one established cause. Coordination broke down. Communications and reporting became unreliable or contradictory. Authorization and casualty response did not occur when later reviewers concluded they should have. Parts of the surviving evidence also passed through damaged, incomplete, or contested custody.
Medical reconstruction established a narrower but consequential finding: some casualties were preventable or potentially preventable.
That finding does not by itself establish who was responsible.
A casualty may remain medically salvageable while transport is unavailable. An order may exist but arrive after its useful decision window has narrowed. A communications failure may prevent one command from knowing what another has already decided. A restriction intended to prevent reckless escalation may become dangerous when circumstances change faster than authorization can be verified.
The investigation therefore has to reconstruct more than the final outcome. It must determine what information, authority, resources, and useful decision time each participant actually possessed when action was required.
The Earlier Escalation Failure
The Earlier Escalation Failure
Ash Corridor did not begin with a clean institutional history.
In 3622 BBY, Captain Maxir Korden exceeded the authority of an ambiguously bounded contingency order before receiving required confirmation. Preventable casualties followed. Maxir was formally censured and subjected to tighter limits on escalation, while Major Tarika Kenau was reprimanded for failing to define the delegated authority and its controls adequately.
Ash Corridor created the opposite danger.
The earlier incident demonstrated what could happen when a subordinate acted beyond verified authority. Ash Corridor forced the same command structure to confront what could happen when verification, authorization, coordination, or evacuation took too long.
The earlier failure therefore matters as part of the command environment. It does not predetermine who was responsible for Ash Corridor or prove that the same mistake caused both incidents.
The Accountability Review
The Accountability Review
Major Sara Kenau leads much of the operational reconstruction. Her review compares orders, communications, convoy and movement records, casualty routing, readiness information, and other Army evidence to determine what each command knew, what authority it possessed, and when useful action remained possible.
Sara's own personnel and reporting were part of the incident, so her position is not that of a completely detached observer. Her relationship with Tarika adds another complication: they are twin sisters. Independent safeguards are therefore necessary where family connection and investigative responsibility overlap.
Neither relationship proves bias. Both make evidentiary discipline more important.
PX-21 supports the reconstruction by authenticating surviving Army records, comparing versions, preserving contradictory evidence, and documenting chains of custody.
Authentication answers limited but important questions. A genuine order establishes that the order existed; it does not prove the order was correct. A preserved transmission may establish when something was sent without proving when every intended recipient actually received or understood it. A damaged custody chain can reduce confidence in evidence without proving deliberate suppression.
PX-21's value lies in preserving those distinctions rather than turning authentication into a verdict.
Imperial Medical Corps Lieutenant Gavin Rin reconstructs treatment, evacuation, survivability, medical-supply conditions, and clinically significant delay.
His review can establish when a casualty remained medically recoverable, when an intervention ceased to be viable, and whether an operational explanation is consistent with the surviving clinical record.
It cannot independently determine command culpability.
Ash Corridor therefore treats mortality evidence as consequential evidence without asking medical findings to answer questions outside medical authority.
Major Tarika Kenau remains one of the principal command subjects of the review.
The 3622 escalation failure established that her delegation controls had been inadequate. During Ash Corridor she faced a different problem: unreliable information and overlapping authority led her to seek increasingly complete verification before committing to action. Subsequent review found that this insistence on fuller confirmation worsened the delay, even though conditions outside her control also materially constrained the response.
The unresolved question is not simply whether she waited. Investigators still have to determine how much that delay changed the outcome, what alternatives were actually available, and where responsibility belongs among verification, communications, authorization, containment, evacuation, and other failures.
Captain Maxir Korden entered Ash Corridor already carrying the consequences of the 3622 escalation failure.
His conduct, company reporting, and use of restricted authority during the later emergency remain disputed. The earlier censure makes his decisions especially consequential, but it does not answer the Ash Corridor investigation in advance.
The review must still establish what Maxir knew, which restrictions applied at each stage, what his company actually did, and whether his actions fell inside or outside the authority then available to him.
Colonel Veyra Dren carries formation-level responsibility for commands involved in the review. Decisions to retain, restrict, correct, reassign, or remove subordinate commanders therefore make her part of the accountability system as well as one of its authorities.
Darth Zylia Vashara provides a separate layer of scrutiny through a limited military-compliance mandate authorized through Darth Krovos's command.
Ash Corridor and the Grey Ledger
Ash Corridor and the Grey Ledger
Ash Corridor and the Grey Ledger intersect, but they are not the same investigation.
Authorized comparison of Ash Corridor casualty, convoy, procurement, communications, readiness, and custody records exposed discrepancies that became more significant when compared with evidence preserved for other purposes. Some of those comparisons contributed to the broader pattern now called the Grey Ledger.
That overlap does not establish that Ash Corridor was part of one unified Grey Ledger operation, that every discrepancy shares a common cause, or that contradictory evidence was deliberately falsified.
The wider investigation may eventually explain some Ash Corridor inconsistencies. It may instead demonstrate that damaged systems, compartmentalization, local misconduct, ordinary administrative failure, conflicting institutional priorities, and unrelated acts of concealment produced superficially similar problems for different reasons.
Ash Corridor retains its own accountability questions regardless of what the Grey Ledger ultimately becomes.
What Characters Can Know
What Characters Can Know
This page records player-facing continuity. The complete Ash Corridor investigation is not common knowledge within the Empire.
Ordinary personnel may know that a serious operational failure occurred without knowing detailed casualty findings, disciplinary conditions, or the disputed chronology.
Medical findings establish clinical consequences; they do not automatically establish command guilt.
An authenticated record establishes only what that evidence can support. Authenticity does not make every statement or judgment contained within it correct.
A character who experienced Ash Corridor may know one part of the incident accurately while misunderstanding events elsewhere.
Restricted command findings, custody problems, medical evidence, and retention conditions should become in-character knowledge through believable access, assignment, testimony, investigation, disclosure, or roleplay.
Knowledge of Ash Corridor does not automatically provide knowledge of wider Grey Ledger correlations.
Contradictory evidence does not by itself prove deliberate falsification, and disproving one accepted sequence does not automatically establish a replacement.
For broader expectations concerning player knowledge, character knowledge, coordination, and contested outcomes, see Roleplay Guidelines.
Ways Into the Story
Ways Into the Story
Characters do not need to be investigators or senior officers to become involved. Ash Corridor affected systems used by soldiers, medics, transport crews, engineers, communications specialists, records custodians, security personnel, contractors, officers, and witnesses.
Recover a communication fragment, sensor record, checkpoint log, convoy manifest, casualty file, maintenance report, or other record that changes one part of the accepted chronology.
Interview witnesses who experienced different stages of the incident and discover that sincere accounts do not agree.
Join a later Korriban operation where commanders must apply post-Ash Corridor restrictions under real-time pressure.
Serve within Tarika's area of responsibility when verification requirements compete with a closing intervention window.
Serve alongside Maxir's company when restricted escalation authority leaves personnel uncertain about when action is permitted.
Contribute medical, transport, engineering, logistics, communications, security, or evidence-handling expertise to one narrow part of the reconstruction.
Examine whether a particular casualty was realistically preventable given the transport, access, authority, resources, personnel, and information available at the time.
Determine whether an order existed, when it was transmitted, who received it, what authority it carried, and how much useful time remained when it arrived.
Investigate damaged, transferred, missing, or differently preserved evidence without assuming beforehand that disappearance proves conspiracy.
Participate in a readiness, retention, disciplinary, or compliance proceeding whose outcome changes a command relationship.
Discover a Grey Ledger correlation that materially changes one Ash Corridor finding without proving that both investigations share one cause.
Unresolved Questions
Unresolved Questions
What is the most defensible complete sequence of events at Ash Corridor?
Which failures in communications, coordination, evacuation, containment, logistics, authorization, or command materially changed the outcome?
Which casualties were unavoidable, potentially preventable, or preventable with the resources and information genuinely available at the time?
At what point, if any, did continued verification become more dangerous than acting with incomplete certainty?
Were authority boundaries sufficiently clear for the personnel expected to make urgent decisions?
How much responsibility belongs to individual decisions, and how much to defective procedures, communications, logistics, jurisdiction, or institutional design?
Why do surviving operational, casualty, treatment, procurement, and custody records remain inconsistent?
Which custody failures resulted from damaged systems or confusion, and which—if any—resulted from deliberate alteration, isolation, removal, or suppression?
How much weight should the confirmed 3622 failure carry when evaluating a later incident whose complete sequence remains disputed?
What happens if local Army command and outside compliance review reach different defensible conclusions?
Which Ash Corridor discrepancies genuinely connect to the Grey Ledger, and which only resemble a wider pattern?
What the Story Can Change
What the Story Can Change
Ash Corridor can end with more than a verdict.
A stronger reconstruction might clear one disputed decision while exposing another. New timing evidence may change the interpretation of a casualty. A commander might retain rank while losing particular authority, or later operations may demonstrate that an imposed restriction is either necessary or dangerously impractical. Evidence may be authenticated while the institution controlling access to it changes.
The consequences can also alter how Army-administered parts of Korriban function. Evacuation thresholds, delegation rules, communications procedures, convoy control, casualty priorities, evidence custody, countersignature requirements, and relationships among local command, the Medical Corps, and outside oversight can all change through roleplay.
A meaningful resolution does not require discovering one person who caused everything.
The stronger outcome may be a defensible account of which decisions were reasonable, which were not, which systems failed around them, what responsibility each participant actually carried, and what must change before similar conditions produce another casualty list.
Related Records
Related Records
For the current authority, assignments, restrictions, relationships, and personal consequences affecting the people connected to Ash Corridor, browse the Character Directory and the individual dossiers linked above.
For Korriban's environment, controlled access, Sith significance, institutions, hazards, and broader roleplay context, see Korriban.
For the broader institutional context surrounding Army and military service, see Imperial Military.
For the shared campaign date and wider galactic circumstances surrounding the investigation, see Current Setting.
For the wider cross-institutional pattern of contradictory records that sometimes intersects with this investigation, see Grey Ledger.
Page updated
Google Sites
Report abuse