- Date
- 1 BBY
- Continuity
- Canon
- Place
- Massassi Great Temple, Yavin 4
Chronology note. Following Star Wars: Timelines, this pre-Yavin event is placed in 1 BBY. Older publications sometimes label it 0 BBY. About the dating convention →
The evidence still seems incomplete
Jyn and her companions returned to the Alliance headquarters on Yavin 4 with what they had learned about Galen's hidden reactor flaw. The actual construction plans, however, remained under heavy Imperial security at the Scarif Citadel. Without them, military planners could not identify the weakness with sufficient precision to attack it.
A coalition cannot agree
Members of the Alliance council disagreed about whether to attack Scarif. Some leaders considered the risk unacceptable or believed that the newly demonstrated superweapon made open resistance futile. Others argued that no safe future could be built by allowing the Empire's station to remain in service.
A mission without formal authorization
Jyn's appeal failed to win the council's full approval. Cassian and several volunteers nevertheless offered to follow her, joined by Chirrut, Baze, Bodhi, K-2SO, Melshi and other rebel specialists. They prepared a captured Imperial transport for a mission that the central leadership had declined to order.
Anthropological assessment
The disagreement illustrates the political complexity of a coalition. Resistance movements must decide when collective procedure is binding and when a moral emergency justifies unauthorized action. The volunteers' choice also changed the decision facing the Alliance fleet once fighting began.
Interactive evidence lab
Open a chronology check or switch perspectives. The result appears immediately below your selection.
Did the full Alliance council unanimously approve the Rogue One mission?
No. A volunteer group left without formal authorization after the council failed to agree.
Source-critical investigation · Scarif to Yavin
Why incomplete evidence divides a coalition
The Alliance leadership must decide what to risk after Jyn and Cassian bring the warning about Galen Erso's involvement in the Death Star.
Jyn's argument combines personal testimony with a military proposal: her father's work may contain a vulnerability, but proof of the precise design remains inside an Imperial archive. Members of the council have reason to fear another trap or an operation that their available forces cannot sustain. That does not make them indifferent to oppression. A political coalition is made from leaders accountable to different worlds, personnel and risks. It can recognize a threat and still disagree over what action the evidence warrants.
The council's failure to authorize the attack is therefore a decision about collective resources as well as belief. To approve an official fleet operation is to accept responsibility for lost ships and potentially for civilians exposed to Imperial reprisals. A dissenting group can nevertheless judge delay to be more dangerous. The film distinguishes these positions: Jyn's team acts after the formal refusal, and later Alliance forces respond once the unauthorized operation becomes an active battle. Those later responses do not retroactively turn the earlier vote into authorization.
This moment is useful for political anthropology because information does not automatically produce consensus. Participants interpret uncertainty through prior experience, their obligations to others and their expectations about whether cooperation will be reciprocated. The archive should describe the scene as a disputed decision on Yavin 4, not assume every council member had access to the same private knowledge of Galen's design. The engineering data recovered from Scarif changed the available evidence after the meeting rather than before it.
Test the historical record: Did the Alliance council formally vote to launch the Scarif assault as Jyn proposed?
Correction and insight: No. The mission began without council authorization; other Alliance forces chose to assist once the operation was underway.
Primary source: Rogue One: A Star Wars Story and Lucasfilm: Jyn Erso Databank. The Databank establishes narrated events; institutional interpretation is IDS analysis, not attributed dialogue.
Related records: rogue one unsanctioned scarif 0 → · scarif transmits death star plans 1 →
Sources and methods
Rogue One: A Star Wars Story; StarWars.com Jyn Erso databank. Explore the original background →. Interpretive analysis is distinguished from information shown in the story. Captions disclose when artwork is a character portrait rather than a depiction of the specific historical scene.
Canon · 1 BBY · Pre-Yavin history
The Alliance debates Scarif
Documented historical sequence
Jyn Erso informed the Rebel Council on Yavin 4 that her father had engineered a weakness in the Death Star. The construction records were still at Scarif. The Council refused to authorize a dangerous attack, so Jyn and a small band volunteered for an unsanctioned mission that other Alliance forces later supported.
Institutions, identity and material life
The refusal reveals a coalition whose leaders faced real disagreements about resources, uncertainty and risk. Jyn's supporters used initiative to circumvent formal authorization, but they continued to depend on other rebels' ships and communications.
Why 1 BBY, rather than 0 BBY?
Recent Star Wars chronologies use the Battle of Yavin as the zero point. Rogue One and events immediately before that battle belong to 1 BBY rather than a separate 0 BBY year. The character or story illustration at the top provides context, not a photograph of the entire event.
Test the historical evidence
Two graded questions with corrections and explanations.