Star Trek: Discovery Season 4 – The Story So Far

Spoiler Warning: There are spoilers ahead for Star Trek: Discovery Seasons 1-3 and the trailers and teasers for Season 4.

As we welcome the month of November, Star Trek: Discovery’s fourth season is now only a couple of weeks away! With the season fast approaching I thought it would be a good idea to recap, as succinctly as possible, the story so far. Michael Burnham and the rest of the crew have been on a wild ride that’s seen them face off against militant Klingons, a Mirror Universe impostor, a rogue AI, Section 31, and a journey into a future that none of them expected to find.

If you haven’t re-watched Discovery since Season 3 ended just after New Year, I hope this recap of the story so far will be helpful going into Season 4. If for some reason you haven’t seen Discovery yet, well this recap might help you get acclimated with the show and some of the characters – but there’s still a couple of weeks to watch the show’s forty-two episodes… so you’d better get on with it!

Season 4 is imminent!

As I’ve said previously, the show’s first season didn’t get off to a great start story-wise. As things settled down, though, Discovery told a creditable story over the course of the season, one which hit a lot of the right notes in terms of “feeling like Star Trek.” But Season 2 was leaps and bounds ahead of where Season 1 had been, with noteworthy improvements in writing and characterisation to tell a truly exciting and engaging story.

Season 3 was a risk in some respects, but in others it was clearly designed to answer criticisms from some quarters about the show’s place in Star Trek’s broader canon. Shooting the ship and crew almost a thousand years into the future meant abandoning the 23rd Century – and everything else familiar about Star Trek’s galaxy. However, this decision opened up Discovery to brand-new storytelling ideas, and gave the writers and producers far more creative freedom. The show was pioneering new ground instead of trying to walk an occasionally awkward line between the franchise’s established history and bringing new ideas to the table.

Captain Burnham in a promo image for Season 4.

There were some great successes in Season 3. For the first time we got standalone episodes – or at least semi-standalone episodes in which the main story of the season took a back seat. We also got spotlight moments for more of the ship’s secondary characters, some of whom had barely had more than a line or two of dialogue despite being fixtures on the bridge. Though I have criticised the Burn storyline – which was the most significant aspect of the season’s story – for having a number of issues, overall Season 3 was a success.

Discovery has been “the Michael Burnham show” since its premiere episode – for better and for worse. The first three seasons can thus be viewed as Burnham’s ascent to the captain’s chair, and the rocky road she took to get there. Though there has been development of other characters – Saru, Tilly, and Mirror Georgiou stand out in particular – the show’s focus has often been on Burnham.

So let’s head back to the beginning and run through all three seasons as briefly as possible! I’ll try to hit all of the most important and relevant points as we go to get you ready for Season 4.

Season 1

Michael Burnham at the beginning of Season 1.

Season 1 began with Michael Burnham serving as first officer to Captain Georgiou of the USS Shenzhou. Saru was also a member of the crew, as was helm officer Detmer. After being called to a region of space near the Klingon border, the Shenzhou encountered a new Klingon leader who had a plan to unify all of the Klingon Great Houses by going to war with the Federation. In a moment we’ll charitably call “confusion” (as opposed to other, harsher terms we could use) Michael Burnham attempted to stage a mutiny against Captain Georgiou and fire the first shot at a large Klingon fleet.

After the arrival of Admiral Anderson and Starfleet reinforcements, a battle broke out between the Federation and Klingons – the opening engagement of a year-long war. Georgiou and Burnham led an away mission to attempt to capture the Klingon leader, T’Kuvma, but the mission ended with both Georgiou and T’Kuvma dead and war assured between the two sides.

Season 1 began with Georgiou killed and a Federation-Klingon war breaking out.

The Klingon war led to Starfleet accelerating work on the Spore Drive – a new method of traversing the galaxy that relies on a kind of fungus. The Spore Drive was installed aboard two ships – Discovery and the USS Glenn. Engineer Paul Stamets was in charge of the Spore Drive aboard Discovery under the command of Captain Gabriel Lorca, but the technology wasn’t effective at first.

The crew of the USS Glenn discovered that a tardigrade – a space-dwelling lifeform – could be used to navigate the mycelial network and might be the key to making the Spore Drive operational. However, the crew were killed when the tardigrade got loose, and the ship was destroyed to prevent it from falling into the wrong hands. Initial experiments using the tardigrade were promising, despite the dangers it posed, but when it became clear how painful the process was for the creature, Stamets merged his DNA with the tardigrade’s so the creature could go free. Stamets thus became Discovery’s navigator and the Spore Drive became fully functional.

A space-dwelling lifeform proved key to making the Spore Drive work.

At the same time, Michael Burnham – now a prisoner following her mutiny – had been brought aboard the USS Discovery by Captain Lorca. She was assigned a cabin with Cadet Sylvia Tilly, and employed as a “mission specialist.” Lorca suggested to Burnham that this could be a way to atone for her role in the outbreak of the war, and she played a role in helping get the Spore Drive operational.

Captain Lorca was captured by the Klingons, but was able to escape thanks to the assistance of Ash Tyler – a fellow Starfleet prisoner. Tyler joined the crew of Discovery as Lorca’s new security officer – despite clearly suffering from post-traumatic stress as a result of his abuse and torture by the Klingons.

A war with the Klingons was the focus of large parts of Season 1.

The USS Discovery was sent to the planet Pahvo, where a crystalline transmitter was located. The transmitter could be used, Starfleet believed, to detect cloaked Klingon ships. When the mission went wrong and the native energy-based Pahvans summoned the Klingons to their planet, Captain Lorca disobeyed orders to implement a new plan. Outwardly his plan was to use multiple Spore Drive jumps to unlock the secrets behind the Klingons’ cloaking device – but in reality his plan was to use the Spore Drive to return to the Mirror Universe.

Captain Lorca was later revealed to be a native of the Mirror Universe, having crossed over inadvertently to the Prime Universe. While in the Mirror Universe the crew of the USS Discovery had to try to fit in as soldiers of the Terran Empire. Burnham and Lorca travelled to the capital ship of Empress Georgiou, where Lorca attempted to rally his forces and stage a coup.

Mirror Lorca returned home and attempted to stage a coup.

Lorca was killed during his coup attempt, but Empress Georgiou’s reign was over anyway; other plotters were already eyeing her throne. In a moment of unthinking impulse, Michael Burnham chose to save Georgiou’s life and transported her to Discovery. After investigating how Lorca was able to use the Spore Drive to jump between universes, the crew were able to reverse the process and return home – only to discover that the Klingons had reached the edge of victory in their absence.

A mad plan cooked up by Empress Georgiou and Admiral Cornwell saw a bomb transported to the Klingon homeworld, one which would have devastated the planet if it had been set off. Leading a second, pro-Starfleet values mutiny, Burnham rallied the crew of Discovery against the bomb plot and instead saw the super-weapon turned over to L’Rell – who went on to become the new Klingon Chancellor and ended the war.

Season 2

The crew of the USS Discovery at the end of Season 1.

After the war ended, Burnham and the crew received medals for their roles. Burnham was also reinstated at the rank of commander. Following a computer failure aboard the USS Enterprise, Captain Pike was assigned to the USS Discovery and given temporary command of the ship for his mission to chase down an ambiguous entity known as the Red Angel. The Red Angel had been generating anomalies known as Red Bursts at locations across the galaxy.

The Enterprise’s science officer – and Michael Burnham’s adoptive brother – Spock, had gone missing at the same time. The Red Angel was revealed to be a time traveller – someone with the ability to travel into the past and far into the future. A mysterious figure from Spock’s youth – and who had once intervened to save his life – was revealed as the Red Angel and thus connected to Spock’s disappearance.

Where is Spock?

Meanwhile on the Klingon homeworld, Ash Tyler – whose true identity as a Klingon had been discovered – was able to leave the planet with his “son” thanks to the help of Section 31. The son of Voq and Klingon Chancellor L’Rell was taken away to the Klingon monastery on Boreth to be raised with the monks, and Tyler rejoined Section 31 – which counted ex-Empress Georgiou among its new recruits. Captain Leland tried to maintain the peace aboard a state-of-the-art Section 31 vessel.

Section 31 had come to rely heavily on an artificial intelligence named Control during the Klingon war, and it had become routine for Starfleet admirals to run all of their mission data through Control. Unbeknownst to any of them, Control had aspirations of its own, seeking to become fully sentient and to wipe out its creators. Somehow it discovered the existence of an entity known as the Sphere – a planetoid-sized lifeform that had spent more than 100,000 years studying the galaxy and accumulating vast swathes of data on all of its inhabitants.

The USS Discovery (left) and the Sphere.

By merging its programming with the Sphere data, Control would be able to become fully sentient, and it set out to acquire the Sphere data. Thanks to the time-traveling involvement of the Red Angel, the USS Discovery came to possess the Sphere data, and thus became a target for Control.

After Michael Burnham was able to rescue Spock from Section 31, she took him to Talos IV where the Talosians were able to help “unscramble” his brain, leading to Spock explaining as much as he could about the Red Angel, its origins, and its connection to him. The Red Angel was revealed to be a human.

The Talosians were able to help Spock.

The USS Discovery became a fugitive after rescuing Burnham and Spock from Talos IV; hunted by Control, and thus by Section 31 and all of Starfleet. Control was able to kill off many Section 31 leaders and operatives, and used nanites to “assimilate” or possess the body of Captain Leland – but thankfully left Ash Tyler and Georgiou alone!

The crew of Discovery studied scans of the Red Angel following a mission to Saru’s home planet (in which they rescued his people from subservience to the Ba’ul, a second sentient race present on the planet). Saru underwent a transformation to his “evolved” form, losing much of his fearfulness in the process. Scans of the Red Angel revealed that the time traveller was, to everyone’s surprise, Michael Burnham.

Michael Burnham was believed to be the Red Angel.

After a side-story involving native beings in the mycelial network and Tilly, Dr Culber – who had been killed by Tyler/Voq – was able to be rescued from the mycelial network and brought back to life. Meanwhile a plan to lure the Red Angel and trap her ended up proving that Burnham wasn’t the Red Angel – her long-lost mother was.

Dr Gabrielle Burnham had been using the Red Angel suit to interfere in the timeline after getting trapped in the 32nd Century. She arrived there by accident only to find all sentient life in the galaxy gone thanks to Control, which had acquired the Sphere Data and evolved itself. She began taking action to thwart Control, including giving the Sphere data to Discovery to keep safe. She was later pulled back to the 32nd Century; her presence there ultimately determined the ship’s destination at the end of the season.

Dr Gabrielle Burnham explained why she – as the Red Angel – was interfering with the timeline.

Control was hot on Discovery’s heels, and using Captain Leland attempted to gain access to the Sphere data. Pike and the crew realised the data couldn’t be destroyed – it was protecting itself – so they made a plan to send the data into the far future, securing a time crystal from the Klingon monastery on Boreth in order to build a new Red Angel suit. During the mission to Boreth, Captain Pike made a great sacrifice to acquire the crystal – cementing a future for himself of devastating disability.

While preparing for a last stand against Control and a fleet of Section 31 ships under its command, the crew of Discovery raced to build a second Red Angel suit. After Control arrived and a battle raged, Michael Burnham used the completed suit to travel back in time and set the Red Bursts – making the whole story somewhat circular – before leading the USS Discovery (now under Saru’s command) into the future. Captain Pike and Spock remained behind in the 23rd Century.

Season 3

On the bridge of the Enterprise, Captain Pike, Spock, and the crew watched the USS Discovery disappear.

Arriving 930 years later, Michael Burnham was initially alone and crash-landed on the planet Hima. There she met Cleveland Booker who told her about the Burn: a galaxy-wide catastrophe in which many starships were destroyed. The Federation had also disappeared – at least from the local region of space – and though Book initially appeared antagonistic and out for himself, he eventually agreed to help Burnham and took her to a Federation outpost.

There was no sign of Discovery, however, and it was a full year later before the ship emerged from the time-wormhole. After a rough landing on a planet named the Colony, Acting Captain Saru and the crew came into conflict with Zareh, a courier working for a faction called the Emerald Chain. Thanks to the timely arrival of Book and Burnham, Discovery was rescued and proceeded to Earth using the Spore Drive.

After a year in the future with Book, Michael Burnham was able to find Discovery again.

In the 125 years since the Burn, however, many changes had taken place. Earth was just one of many planets to have quit the Federation, retreating to an armed isolationist stance that even saw the planet unwilling to communicate with human colonies inside the Sol system. Searching for a Starfleet Admiral named Senna Tal seemed fruitless at first, but Tal’s Trill symbiont had been transferred to a human named Adira.

After helping the people of Earth reconnect with their fellow humans on Titan, Discovery visited the Trill homeworld to help Adira – and to learn the location of Federation HQ, which was no longer on Earth. Burnham and the crew were able to help the Trill, who had been suffering from a shortage of suitable candidates for their symbionts, and also helped Adira in the process. Discovery was then able to travel to Federation HQ – a cloaked space station that housed the remnants of both the Federation government and Starfleet.

The USS Discovery docked at Federation HQ.

Having peaked at around 350 members, by the time of Discovery’s arrival the Federation was down to a mere 38 remaining worlds, some of which were out of contact due to the Burn’s lingering effects and damage to subspace communications. The ship undertook a short mission to recover some seeds from the USS Tikhov – a Starfleet seed vault – in order to provide medical care. Nhan, a Barzan officer, remained behind on the Tikhov.

The USS Discovery then underwent a retrofit, one which kept the familiar interior look of the ship but which upgraded many of its systems to 32nd Century standards, including detached nacelles and programmable matter. The crew were permitted to remain together under Captain Saru’s command, but Discovery was seconded to Federation HQ as a “rapid response vessel” thanks to its Spore Drive.

Admiral Vance was the head of Starfleet in the 32nd Century.

Michael Burnham and Georgiou undertook an off-the-books mission to rescue Book, who had been captured by the Emerald Chain. The upshot of Book’s rescue was the discovery of a Starfleet black box, and the data inside proved that the Burn did not happen everywhere simultaneously, as had been theorised. Instead it had a point of origin – but without more information it wasn’t possible to pinpoint it.

SB-19 was a project run by Ni’Var – the renamed planet Vulcan following reunification between Vulcans and Romulans – in the years before the Burn. Ni’Var had come to believe that SB-19 was responsible for the Burn and were unwilling to share any details about the project, even though Burnham asked them to share it to help pinpoint the Burn’s source. Eventually, however, the reappearance of Dr Gabrielle Burnham, who was now a member of the Qowat Milat, an order of armed Romulan nuns, showed Burnham the way to get the information and recommit herself to Starfleet following a year away from the ship.

A holographic depiction of SB-19.

After acquiring the SB-19 data, Discovery undertook a mission to Book’s home planet of Kwejian. Threatened by the Emerald Chain and its leader, Osyraa, Book’s brother attempted to turn him over to the faction in exchange for protecting the harvest and thus Kwejian’s food supply. Piloting Book’s ship, Lieutenant Detmer was able to damage the Emerald Chain flagship while the crew of Discovery found a way to protect Kwejian’s food supply without the need to rely on the Emerald Chain.

Mirror Georgiou had fallen ill, and a mysterious Federation figure named Kovich knew why – travelling through time and travelling across from a parallel universe leads to a painful and fatal condition which he believed to be incurable. The USS Discovery undertook a mission to a planet near the Gamma Quadrant to help Georgiou, and she was able to travel to a parallel universe very similar to the Mirror Universe.

Burnham and Georgiou travelled to this planet to seek help for her illness.

While in the Mirror Universe, Georgiou attempted to make changes. Having spent time with Burnham and the Federation she had become more compassionate and less quick to violence than before, and though she ultimately failed to bring about major reforms to the Terran Empire, she was deemed “worthy” of a second chance by the entity which sent her there – an entity which subsequently revealed itself to be the Guardian of Forever.

Georgiou was able to use the Guardian’s portal to leave the 32nd Century and thus save her life – but she had to say goodbye to Saru, Burnham, and the rest of the crew. Her destination isn’t clear – but if the Section 31 series gets off the ground in future we may just find out! Don’t hold your breath for that, though… it’s feeling less and less likely as time goes by!

The Guardian of Forever sent Georgiou to an unknown destination in order to save her life.

With the data from the black boxes and SB-19, Burnham and the crew were able to triangulate the source of the Burn: the Verubin Nebula. Inside the nebula was a crashed Kelpien starship, the KSF Khi’eth, and a life-form was detected on board despite the dangerous radiation from the nebula. Discovery made another jump to the nebula, and Captain Saru left Ensign Tilly in charge while he went to save the lost Kelpien.

The Emerald Chain took advantage of this situation to capture the USS Discovery, wanting to keep the Spore Drive technology for themselves. Leader Osyraa then set course for Federation HQ, keeping Discovery’s crew hostage while she tried to force the Federation into an alliance. Admiral Vance called her bluff, and Osyraa attempted to escape. In the meantime, though, Michael Burnham had jettisoned poor Stamets off the ship, and without him to control the Spore Drive Discovery was forced to rely on warp.

Stamets was ejected into space – but don’t worry, he’s okay!

Following a battle with the Emerald Chain both in space and aboard Discovery, Book was able to kill Osyraa’s lieutenant Zareh and Burnham was able to kill Osyraa herself, while Tilly and other members of the bridge crew regained control of the ship. Book’s empathic abilities allowed him to use the Spore Drive, transporting Discovery back to the Verubin Nebula just in time to save Saru, Culber, Adira, Gray, and Su’Kal – the Kelpien who was accidentally responsible for the Burn all those years ago.

Su’Kal had developed a telepathic link with dilithium thanks to the Verubin Nebula’s radiation and because the Khi’eth had crashed on a planet composed largely of the valuable fuel. When Su’Kal’s mother died while he was still a child, a telepathic shockwave that Su’Kal accidentally unleashed led to the Burn. By taking him away from the Verubin Nebula, any prospect of a repeat of the Burn was nullified.

Saru was able to rescue Su’Kal and prevent a reoccurrence of the Burn.

A short epilogue to the season showed us that Trill had rejoined the Federation and that the Federation was hoping to use the dilithium in the Verubin Nebula to bring hope back to the galaxy. Ni’Var was considering rejoining too, and Saru took a leave of absence to go to Kaminar with Su’Kal. In his absence, Burnham had been promoted and assumed command of Discovery.

And that’s the story so far!

We now know that Captain Burnham and the crew will have to contend with a gravitational anomaly in Season 4; an uncharted, never-before-seen phenomenon that appears to be threatening the Federation and all of known space. How that will play out isn’t clear at all right now, but we don’t have to wait too much longer to find out!

The USS Discovery in the Season 4 trailer.

I hope that this recap of the story so far has been useful. I didn’t include everything – this article would have been far too long if I’d tried to include every character moment and side-story. But I think I hit the most important story beats from all three seasons. I’d encourage you to check out other story recaps from other places to make sure you’re getting a full picture, though! Or you could just go back and re-watch Discovery… two episodes per day will get you pretty close, and then binge-watch the final few!

Going back to the stories of earlier seasons was a bit of fun, and it’s helped get me back into a Star Trek mood in time for Season 4, which will be upon us before you know it! I’m currently not writing up reviews of Prodigy episodes, as you may have noticed – the series is unavailable here in the UK and I see no point in covering a show that ViacomCBS doesn’t see fit to make available to Trekkies internationally. However, I will cover Discovery’s fourth season in depth, including weekly episode reviews and theory posts, as well as other occasional articles on topics of interest while the season is ongoing. So I hope you’ll stay tuned for all of that here on the website in the weeks ahead.

Star Trek: Discovery Seasons 1-3 are available to stream now on Paramount+ in the United States and on Netflix internationally. Season 4 will begin on the 18th of November in the United States and the 19th of November internationally. The Star Trek franchise – including Discovery and all other properties mentioned above – is the copyright of ViacomCBS. This article contains the thoughts and opinions of one person only and is not intended to cause any offence.

Star Trek: Picard + Star Trek: Discovery crossover theory: Control and the Romulans

Spoiler Warning: There are spoilers ahead for the most recent seasons of Star Trek: Picard and Star Trek: Discovery. There may be further spoilers for other iterations of the Star Trek franchise.

While Star Trek: Picard Season 1 was ongoing earlier in the year, I postulated a number of theories about what was going on in the show. One theory that I had related to Control – the rogue artificial intelligence from Star Trek: Discovery Season 2. Specifically, I speculated that the Zhat Vash’s hatred and fear of synthetic life may have stemmed from a run-in with Control, or that the Romulans may have been trying to compete with Starfleet in a mid-23rd Century AI arms race. It seemed possible that Control could have attacked Romulan ships or settlements in the time between its takeover of Section 31 and its defeat by the USS Discovery, or that if the Romulans developed their own AI that it would have similarly gotten out of control and attacked them.

This theory came back with a vengeance after Picard reused a couple of CGI sequences from Discovery in the latter part of the season, particularly as those sequences depicted Control attacking – and ultimately destroying – all organic life in the galaxy. While Picard and Discovery had thematic similarities in their most recent seasons, insofar as both stories looked at the creation of synthetic life and how that synthetic life could go rogue, there was no broader crossover. The Zhat Vash were not motivated by either their own rogue AI from the mid-23rd Century or by an attack from Control.

This CGI sequence of a planet being destroyed was created for Discovery… and recycled in Picard.

But that doesn’t necessarily mean that we have to drop the idea of there being any connection between the Zhat Vash in Picard and Control in Discovery. My theory started with the idea that Control could have been the reason for the Zhat Vash… but what if it’s the other way around? What if the Zhat Vash are responsible for Control going rogue?

There was no explanation given for why Control decided to lash out and attack its creators. It wanted to acquire the data from the planetoid-sized lifeform known as the Sphere, believing that data would help it achieve true sentience. But that isn’t a reason to go on to commit genocide; something inside Control made it want to kill. Remember that Dr Gabrielle Burnham – Michael’s mother – arrived in a future timeline where no sentient organic life existed in the known galaxy; Control had wiped it all out. Why did it want to do that?

Dr Gabrielle Burnham.

We could try to argue that Control’s murderous rage is somehow a result of Starfleet denying it access to the Sphere data. But Starfleet and the USS Discovery only came to possess the data because of the time-travelling interventions of Dr Burnham; we don’t know how Control came to acquire it in the “original,” pre-intervention timeline. There are a couple of possibilities. The first is that when the Sphere died, it broadcast its data as far and wide as possible and that’s how Control acquired it. It’s also possible that Starfleet received the transmission and Control gained access to it from there. However, neither of these scenarios involve Starfleet actively trying to prevent Control accessing the data, meaning that it wasn’t Starfleet who started the fight with Control.

So if Control had no reason on the surface to attack its organic creators, why did it do so? It could simply be a programming error; Control was programmed to prevent war, and perhaps that got twisted around so that it decided the only way to prevent the Milky Way’s organic civilisations from fighting was to exterminate all of them. This kind of basic AI programming mistake is one that’s not uncommon in science fiction, and arguably something we need to consider out here in the real world as we develop our own AIs!

Control assimilated Captain Leland and went on a murderous rampage.

So that’s one possibility. But here’s where the Zhat Vash could come in: what if they are responsible for corrupting Control’s programming? We saw in Picard that the Zhat Vash know enough about synthetic life to hack into Federation synths and change their programming. That’s what they did on Mars, causing F8 and the other synths to go rogue and destroy Admiral Picard’s rescue armada. If they had that capability in the 24th Century, it isn’t much of a stretch to think they could have been capable of something similar in the 23rd Century too.

We also know that the Zhat Vash are “far older” than the Tal Shiar. Let’s look at what we know for sure to try to pin down a rough estimate of how old they could be. The Romulans split from the Vulcans somewhere around the 4th Century AD, and by that time were capable of interstellar flight. By the 2150s the Romulans were involved in covert operations on Vulcan, trying to start a war between Vulcans and Andorians. While it was never stated outright in Enterprise that the Romulan operatives we saw were working for the Tal Shiar, it’s not an unreasonable assumption. The Zhat Vash sent Commodore Oh to infiltrate the Federation sometime around the discovery of Data, which took place in the year 2338. When Raffi asked La Sirena’s Emergency Navigational Hologram about the octonary star system, he described the Romulan star charts that depicted it as “ancient,” which seems to suggest they’re more than a century old at least. It was the discovery of Aia, the planet in the octonary star system, and the beacon that resided there that led to the creation of the Zhat Vash.

Raffi and the ENH discuss the octonary star system.

Put all of that together and we can assume with reasonable confidence that the Zhat Vash existed by the mid-23rd Century. We also know, thanks to what we saw in Enterprise and Deep Space Nine, that Romulan intelligence was far better than Starfleet’s – they knew a lot more about the Federation than the Federation did about them.

There’s a question of just how secret Control was. Section 31 was much more out in the open in Discovery than it was by the time of Deep Space Nine, but even so it seems logical to assume that Control would be a top-secret project within an already-secretive organisation. Still, when most Starfleet flag officers used Control regularly, word of its existence would get out and it was generally known within Starfleet that an AI existed. Thus any Zhat Vash or Tal Shiar operative would have come to know about Control.

Section 31 HQ was heavily-guarded, but perhaps not impenetrable for a Zhat Vash spy.

Okay, so let’s slow down. Even if we’re confident that the Zhat Vash existed by Discovery’s era, and had commenced their anti-synthetic crusade, and even if they had operatives within Starfleet who would have made them aware of the existence of Control, that doesn’t mean they could just walk up to Control’s data servers and start messing around. Right? I mean, Control was based at Section 31 headquarters, which as we saw in the show was incredibly well-protected. And we saw no evidence of such an operative. Did we?

How about Admiral Patar, the Vulcan Starfleet admiral who was killed by Control at Section 31 headquarters? We know that Commodore Oh spent decades embedded within Starfleet, waiting to make her move at just the right moment. We also know she was able to attain a very high rank, and it’s only one short step from being a commodore to being an admiral. It’s at least possible. Admiral Patar had the means to access Control. She spent time at Section 31 headquarters right around the time Control went rogue. She was a Vulcan, and thus was biologically indistinguishable from a Romulan – meaning she could have been an undercover Romulan operative. Enterprise depicted Romulans undercover on Vulcan a century earlier, meaning that they had infiltrated Vulcan by that time and were able to do so with relative ease. The pieces fall into place for Admiral Patar to be a Romulan operative – or to have been replaced by one – even if the evidence is only circumstantial. Even if it wasn’t Patar, there may well have been other Vulcans working at Section 31 headquarters, any one of whom could have been a Romulan spy.

Admiral Patar on the USS Discovery’s viewscreen.

Once they had access to Control’s systems and specifications, the Zhat Vash could have figured out how to mess with Control’s programming and turn it hostile. Perhaps they only intended for it to attack the Federation, forcing them to shut it down permanently. Or perhaps they hoped it would cause wider chaos so they could force the kind of galactic ban on synthetic life that we saw in Picard. So the question of what they had to gain by such a move is obvious; it’s the same basic goal as they had for staging the attack on Mars.

If the Zhat Vash introduced a glitch in Control’s programming that would turn it murderous, they obviously didn’t intend for Control to go on and wipe out everything. That wasn’t the goal; that’s what they were trying to prevent. However, as I wrote earlier, it’s possible for even well-intentioned AI to get out of control or to act in a way its creators and programmers couldn’t anticipate. Perhaps that’s what happened with Control, and by the time it had assimilated Captain Leland, killed off most of Section 31’s leadership, and got a fleet at its command, there was no way for the Zhat Vash to stop it. If their sole operative had been killed when Control wiped out Section 31’s headquarters, the Zhat Vash may not have even been aware that the mission was not going to plan until it was too late.

Control commandeered a small armada of Section 31 vessels.

So that’s my crossover theory for Star Trek: Discovery and Star Trek: Picard – the Zhat Vash hacked or reprogrammed Control, and that’s what made it go rogue. There’s enough circumstantial evidence for this theory to be possible, and it would explain why Control went from being a useful tool for Starfleet to a menace capable of wiping out all sentient life in the galaxy. However, there’s no concrete proof. All we really have are two shows with similar themes, and a bunch of unrelated pieces that could be made to fit together – but also may not fit at all!

As I always say: it’s just a fan theory. Unless we get some confirmation on screen in future – which seems unlikely given both Picard and Discovery are almost certainly moving on to new stories in their upcoming seasons – we have to consider it as unconfirmed at best. I consider it plausible (obviously, or I wouldn’t have written an article about it!) but it may prove to be a complete miss… just like many of my other Star Trek: Picard theories!

This post was edited 31.03.21 to replace header image. Star Trek: Discovery and Star Trek: Picard are available to stream now on CBS All Access in the United States. Discovery is available internationally on Netflix; Picard is available internationally on Amazon Prime Video. The Star Trek franchise – including all properties mentioned above – is the copyright of ViacomCBS. This article contains the thoughts and opinions of one person only and is not intended to cause any offence.

Star Trek: Picard Season 1 theory roundup!

Spoiler Warning: There are spoilers ahead for the entirety of Star Trek: Picard Season 1, including its ending. There may also be spoilers for other iterations of the Star Trek franchise.

Star Trek: Picard’s first season wrapped up at the end of March – and it feels like forever ago, what with everything that’s happened in the world since! While the season was running, in addition to reviewing each of the episodes in turn I also concocted a number of different theories for what was going on in the show. Star Trek: Picard very carefully set up a number of mysteries, and even heading into the second half of the finale, it wasn’t clear exactly how they would be resolved.

I’d argue that the first season’s two-part finale wasn’t the show at its best, and it felt as though a season which started incredibly strongly ended up stumbling a little as it crossed the finish line. There were a number of reasons for this – which I covered at the time – but it boils down to some of the show’s mysteries not being fully explained, and some storylines being dropped or left unresolved. That and the truly awful gold makeup used for the synths on Coppelius!

Yikes.

If you’d like to read all of my theories from Star Trek: Picard Season 1, you can find them on my dedicated Star Trek: Picard page. Click or tap here to be taken there!

This time, what I’d like to do is take a look back at some of the theories I postulated while the season was running. I’ll explain why I thought they seemed viable – and why they ended up being total misses! In a way, part of the fun of theory-crafting and speculating is knowing that you won’t always get it right… and boy oh boy did I have some seriously wrong theories!

Number 1: Dahj and Soji aren’t synthetics, they’re genetically-engineered humans.

Soji in the episode Nepenthe.

This is a theory I first came up with right at the beginning of the series, almost from the very moment Picard begins to suspect that Dahj is synthetic. It seemed like it could’ve been a clever idea for a double-bluff – establishing Dahj and Soji as synths, only to rip that away and challenge both Picard’s and the audience’s expectations. However, it didn’t pan out that way, and looking back, this theory was kind of ridiculous!

Genetic enhancements, similar to those made on characters like Dr Bashir and Khan, could have given Dahj the incredible speed and strength that she possessed in Remembrance, so from that point of view it wasn’t wholly unthinkable. But looking back, while Star Trek: Picard did aim to be a show that kept us guessing and didn’t telegraph every aspect of its storyline, this kind of subversion of expectations would have been a step too far. We didn’t know anything about Dahj or Soji at the beginning of the series, and to take the one established fact about them and make it a lie or a misunderstanding would have been a storytelling mistake.

Dahj during her fight against Zhat Vash operatives in Remembrance.

There was also plenty of evidence that Dahj and Soji were synthetic: Picard’s meeting with Dr Jurati, Narek’s interest in Soji, and the strong connection Picard felt to Dahj (and later to Soji) because of his friendship with Data. All of that would have made no sense in the story if we’d ended up dealing with genetically-enhanced humans!

I brought this theory back after episode 3, The End is the Beginning, based on a line spoken by one of the Romulans who attempted to assassinate Picard: “she’s not what you think she is!” This of course referred to Soji, and it struck me that, as Picard and his comrades believed Soji to be a synth, perhaps the Romulan knew that she was not. However, as the story progressed it became abundantly clear that Soji and Dahj were the synthetics that the story established them to be, and that I was barking up the wrong tree with this one!

Number 2: Section 31 will make an appearance in the show.

A black Section 31 combadge from Star Trek: Discovery.

This theory was crafted not so much because of anything that directly happened in the plot of the show, but rather for production reasons. In short, the Star Trek timeline is seriously fractured, with shows being produced simultaneously occupying very different timeframes. When Discovery’s third season kicks off in a few weeks time, there will be four shows occupying four time periods. This complicates the franchise, and what that means is that some threads of continuity would be very helpful, especially for casual viewers.

Section 31 featured heavily in Discovery’s second season, and in addition, a spin-off based on the organisation is currently being worked on. It seemed logical that Star Trek: Picard might want to find some way of incorporating Section 31 if for no other reason than having one of those threads of continuity running through the franchise, tying things loosely together and being a frame of reference for casual viewers.

My first thought for a potential Section 31 appearance was that they could’ve been responsible for the attack on Mars and the destruction of Picard’s armada. I theorised they might have taken such aggressive action to prevent the Federation giving aid to the Romulans. This was extended to include Section 31 hacking the Mars synths as part of this plan.

F8’s eyes during a flashback sequence that depicted the hack.

I next had two potential Section 31 operatives pegged – Chris Rios and Seven of Nine. Rios because he worked aboard a Starfleet ship that was “erased” from the records, and Seven of Nine because it wasn’t clear who she worked for or why she was following Picard.

Finally, as these other theories fell by the wayside, I speculated that Section 31 may have arrived to take control of the Artifact after it was abandoned by the Romulans and later crashed on Coppelius. While I suppose you could argue that might yet happen, it didn’t happen in Season 1, and thus any real benefit of the organisation crossing over from a behind-the-scenes perspective was lost.

I maintain that this theory makes a lot of sense from a production perspective, and my final idea in particular – Section 31 taking control of the Artifact to study it – could have been accomplished without making any changes whatsoever to the season’s storyline. However, it didn’t happen!

Number 3: Soji’s Trill friend will end up getting assimilated or killed.

Soji with Dr Kunamadéstifee in Maps and Legends.

Episode 2, Maps and Legends, introduced a Trill doctor working aboard the Artifact along with Soji. She ultimately only appeared in one sequence, but that sequence seemed to contain a lot of horror film-style foreshadowing, and for weeks I was insistent that we’d see this character meet an unpleasant end! Aboard a Borg cube – even a disabled one – the most likely way that would manifest would’ve been her assimiliation.

After Soji helped Dr Kunamadéstifee with her uniform, the two stood together while they listened to a speech from one of the Artifact’s Romulan guards. He stated that the area they were about to enter was incredibly dangerous, and a nearby sign seemed to reinforce the possibility of assimilation by counting the days since it had last happened. This seemed as thought it could tie in with Soji working on de-assimilating Borg drones; was she about to see her friend end up on her operating table?

Dr Kunamadéstifee again.

It turned out, of course, that I was reading too much into one side character and one short sequence, because not only didn’t Dr Kunamadéstifee end up assimilated, she was never seen again after Maps and Legends, which was a shame because she seemed like a potentially interesting character. Soji spent much of her time from episodes 2-6 with Narek, and giving her someone else to interact with was a good idea. My theory was that their friendship may have built up a little more, leading to shock and sadness for Soji upon learning of Dr Kunamadéstifee’s fate.

I suppose in theory we could say that it’s unlikely that she survived the various disasters which befell the Artifact, from Narissa executing huge numbers of ex-Borg to the ship crashing on Coppelius, but nothing was ever seen on screen to even hint at her fate.

Number 4: Commodore Oh is a synthetic.

Commodore Oh in the episode Broken Pieces.

As with Soji and Dahj being human, this was kind of an “out there” theory! But the whole point of theory crafting is to make wild guesses sometimes, and there were a couple of reasons why I considered this a possibility. First of all, it would have been thoroughly unexpected and shocking. Many recent films, games, and television series have tried to pull off genuinely unexpected twists, and had this been true, it would have been one heck of a shock!

Secondly, the premise of Star Trek: Picard’s first season had been the cloak-and-dagger factions vying to thwart or create synthetic life. The Zhat Vash and the Tal Shiar were on one side, Maddox and his team on the other. There were rogue traders, Romulans, ex-Borg, and all sorts of shadowy figures involved – any one of whom could have not been what they seemed. The show crafted mysteries for us to examine. As we learned more about the Zhat Vash and their mission, I began to wonder if they could have been infiltrated by someone who wanted to stop them harming synths. This later evolved into wondering if they’d been infiltrated by someone who wanted to bring about the very disaster they sought to prevent.

Commodore Oh on the bridge of her ship.

Dahj and Soji were both unaware of their true synthetic natures, which built on past iterations of Star Trek that showed synths can be programmed to not realise they’re synths. Commodore Oh could have genuinely believed in the Zhat Vash cause – but been programmed to “activate” at the opportune moment. We later learned that the Zhat Vash feared the arrival of a faction of super-synths that I dubbed the “Mass Effect Reapers” (because they were very similar to that video game faction) and I incorporated that into this theory, suggesting that Commodore Oh may be working for the “Mass Effect Reapers” to try and bring about their arrival.

Of course it was a complete bust! Commodore Oh was a Zhat Vash operative to the core, and as far as we know, wholly organic in nature! I still think she’s a fascinating character, and I wrote an article a few months back looking at her place in the Star Trek timeline. You can find it by clicking or tapping here.

Number 5: Picard telling everyone that their enemies are the Tal Shiar – and not the Zhat Vash – will have consequences.

A Zhat Vash operative.

One thing that Star Trek: Picard didn’t do particularly well, in my opinion, was staying consistent in how it referred to its antagonists. In Remembrance, the faction who attacked Picard and Dahj weren’t named, but in Maps and Legends we learned of the existence of the Zhat Vash – an ancient, shadowy organisation which operated within, yet were distinct from, the Tal Shiar.

Yet for several episodes, Picard and others kept referring to their adversaries as the Tal Shiar. In-universe, there’s a certain kind of logic to this. Picard may not have believed fully in the Zhat Vash’s existence, having only heard about them from one source, or he may have felt trying to explain the difference would have been too time consuming and/or made him seem too conspiratorial. However, with practically everything else in the show being done deliberately to achieve certain story payoffs, I wondered whether Picard’s decision not to be up front with his crew might have had repercussions.

Colonel Lovok (or rather, a changeling impersonating him) was a Tal Shiar operative seen in Star Trek: Deep Space Nine.

Elnor was the one character who I felt seemed most likely to be affected by the revelation that it was the Zhat Vash, not the Tal Shiar, that he was up against. As a member of the Qowat Milat, Elnor was opposed to the Tal Shiar. But the Qowat Milat’s relationship with the Zhat Vash was unclear; even if they were enemies, the Qowat Milat may have had particular techniques for dealing with them. And at the very least, Elnor and his faction seemed likely to know of their existence.

However, Elnor learned in Nepenthe that he was facing off against the Zhat Vash, not the Tal Shiar, and the revelation seemed to have no impact on him whatsoever. The rest of La Sirena’s crew were equally nonplussed, and there were no consequences at all for the confused terminology – at least, not from an in-universe point of view. I think that, unfortunately, the decision to complicate the terminology around the show’s antagonists may have made it harder to follow for casual viewers. When dealing with made-up names like “Tal Shiar” and “Zhat Vash”, remaining consistent is important for the audience to be able to follow what’s going on.

Number 6: There’s a Starfleet-Zhat Vash conspiracy.

Admiral Clancy, the commander-in-chief of Starfleet.

In Maps and Legends, we were introduced to Commodore Oh for the first time. It was a great shock to see a high-ranking Starfleet officer involved in Dahj’s murder, and at the time it wasn’t at all clear whether Commodore Oh was a Romulan infiltrator or a Vulcan co-conspirator. If she was a Starfleet officer working with the Zhat Vash, it stood to reason that others in Starfleet were as well – perhaps even senior admirals.

Furthermore, when we learned how Commodore Oh recruited Dr Jurati into the conspiracy – all it took was a brief mind-meld – it seemed plausible that she may have used the same technique on others. Commodore Oh had been embedded in Starfleet for more than sixty years, and in that time there’s no telling how many people she may have interacted with.

Lieutenant Rizzo arrives to meet Commodore Oh.

However, it turned out not to be the case. Admiral Clancy, the head of Starfleet Command, wasn’t compromised, nor were any of the other Starfleet officers and leaders seen or referenced in Season 1. As far as we know – and this could change if future Star Trek projects decide to look at this aspect more deeply – only Commodore Oh and Rizzo were involved within Starfleet, and they were both Zhat Vash operatives.

This is one theory that I’m definitely pleased didn’t pan out. Making Starfleet itself the “bad guys”, even if there were a reason for it, wouldn’t have felt great in a Star Trek series, and would have been a far darker path for the show to have taken. Seeing Riker show up in Et in Arcadia Ego, Part 2 at the head of a Starfleet armada was a beautiful moment (though sadly one that had been telegraphed ahead of time) in large part because it proved that Starfleet and the Federation were still on the right side. The plot to kill the synths and attack Mars was purely a Zhat Vash creation.

Number 7: The Control AI, from Star Trek: Discovery Season 2, is involved.

A re-used image from Star Trek: Discovery.

Although I initially considered it to be a bit out of left field, the episode Nepenthe really kicked this theory into high gear! My first thought had been that perhaps the reason why the Zhat Vash were so frightened of synthetic life was because they had some involvement with Control, the rogue artificial intelligence from Star Trek: Discovery’s second season. I was convinced – wrongly – that the producers behind the overall Star Trek franchise would have wanted to build a major connection between Discovery and Picard for some of the reasons already discussed, and bringing Control in seemed like a viable option for accomplishing this.

In the episode Nepenthe, we finally got to see how Dr Jurati came to be recruited into the conspiracy – she was shown a vision by Commodore Oh, one that seemed to warn of something apocalyptic. Contained within this vision were a couple of visuals that were made for Star Trek: Discovery – more specifically, they were used to show a vision Michael Burnham and Spock had of the Control AI.

The Control AI commandeered Captain Leland’s body in Star Trek: Discovery.

At the time, I noted that there could be production-side reasons to re-use visual effects, as it was less time-consuming and cheaper than making wholly new CGI. However, for a couple of weeks I really did think that we were going to find some connection between Control and the Zhat Vash; perhaps the Romulans and Federation had been competing in some kind of mid-23rd Century AI arms race, or perhaps while Control was on the loose it had attacked Romulan ships or planets.

In a thematic sense, Star Trek: Picard’s first season and Discovery’s second season share some significant points. Both consider the potential for rogue or out-of-control artificial life, and both look at the consequences of continuing to develop AI – something that we arguably should be concerned about today! But there was no deeper crossover beyond basic themes, and the shows remain almost entirely separate from one another. The re-used visuals are what completely threw me for this one!

Number 8: The synths on Coppelius are already dead.

A crowd of clearly not dead synths in Et in Arcadia Ego, Part 2.

Star Trek: Picard’s first season had, unfortunately, one rather large plot hole. The driving force for much of the first half of the season was locating and rescuing Bruce Maddox, the Federation cyberneticist who built Soji, Dahj, and many of the other synths. Maddox was on a planet called Freecloud, a place he travelled to when he seemed to have nowhere else to turn. He ended up returning to the dangerous Bjayzl, someone he owed a lot of money to, and was captured. The reason he put himself in such grave danger was because his lab had been destroyed by the Tal Shiar, or so he claimed.

But in the two-part finale, Picard and the crew travelled to Coppelius and saw for themselves that Maddox’s lab hadn’t been destroyed, and the Tal Shiar or the Zhat Vash had never been there. This feels like a pretty major issue, because the question of why Maddox was on Freecloud now has no satisfactory answer. The reason seems to be “because plot”, and that’s never a good thing.

Bruce Maddox only went to Bjayzl because his lab had been destroyed.

However, before the finale I was still trying to square that particular circle. One of the possibilities I came up with was that Maddox was right – his lab had already been destroyed, which could mean that the synths he’d built were already dead. It would have made Narek’s mission kind of a waste of time, as his colleagues had already killed off the synths, not to mention being a rather bleak way to end the season, but it would have fit together with what had already been established.

I don’t think I’d have enjoyed this storyline, which would have left Soji as perhaps the sole survivor of her race. It would have been very dark, and would have felt like a victory for the show’s antagonists. But at the time, I was scrambling around looking for ways to make the story of the first half of the season – culminating in Maddox’s statement to Bjayzl about his lab being destroyed – fit with the second half of the season and the revelation of the existence of more synths.

Number 9: The captain of the USS Ibn Majid is a character from a past Star Trek show.

Harry Kim could’ve been a starship captain in this time period.

This was a pretty simple theory by my standards. When we learned that Rios had served aboard a ship called the USS Ibn Majid, which was destroyed and covered up, I began to wonder who might’ve been in command of the vessel. Rios was clearly very attached to his former captain, and I wasn’t sure if we might’ve seen – in flashback form – this character make an appearance.

From Rios’ initial comments about the character – that they were dead, male, and “heroic” – I put together a shortlist based on possible characters from past Star Trek shows who could conceivably have been starship captains in that era. I ruled out those who seemed to have no desire to sit in the captain’s chair, like Dr Bashir or Tom Paris, and obviously ruled out those who wouldn’t be eligible like Chief O’Brien. Finally, Zhaban had mentioned that La Forge and Worf were still alive, so they were out too. That left a handful of characters, including Chakotay and Harry Kim, both from Voyager. I also suggested Edward Jellico from The Next Generation two-parter Chain of Command, Solok from the Deep Space Nine episode Take Me Out to the Holosuite, and Captain Bateson from The Next Generation Season 5 episode Cause and Effect.

Solok, the Vulcan captain of the USS T’Kumbra.

There were other possibilities – most of which were minor characters who made only one or two appearances in Star Trek – and there were many male officers who could, in theory, have made the cut. I liked this idea simply for the sake of continuity, as having the Ibn Majid’s captain be someone we already knew seemed like an interesting concept.

With Bruce Maddox, Hugh, and Icheb all killed off in Star Trek: Picard’s first season, it was clear that the producers has no qualms about getting rid of legacy characters! That fact also contributed to making this theory plausible. Past iterations of Star Trek has been reluctant to kill off main characters, but Star Trek: Picard did so several times. However, none of this came to pass, and instead a new character – Captain Alonso Vandermeer – was created for the show, and was only seen briefly in a photograph.

Number 10: Narek will go rogue.

Narek in Broken Pieces after trying to kill Soji.

Narek was a unique character, not only in Star Trek: Picard but in the whole franchise. Never before had an out-and-out villain been a main character, with their name in the opening titles. Narek was also an interesting and nuanced character in a season where – most of the time – the villains could feel flat and one-dimensional. I’m still disappointed that his storyline was unceremoniously dumped midway through the season finale; we didn’t even learn what became of him after Picard’s “death”.

But that’s somewhat beside the point. From as early as the third episode, I began speculating that somehow, Narek would be convinced to abandon his mission and join with Soji and Picard. His clear feelings for Soji seemed to offer a route for him to make this happen, but even if the show didn’t go for the “spy falls in love with his target” trope, there were other ways it could’ve happened. Narek seemed like a reasonable man; if it were demonstrated to him that the synths were not a threat, it seemed at least plausible that he might’ve switched sides.

Narek’s final appearance.

However, as of the last time we saw him – before he just dropped of the face of the series with no conclusion to his story – he was still 100% committed to the Zhat Vash cause. In fact, he never wavered. His attempt to kill Soji may have caused him great distress, but that didn’t stop him going ahead with his mission; he didn’t even hesitate.

I actually like that Narek was unpredictable, and as a whole I like that the show set up what looked to be a familiar trope – the spy with a heart of gold who switches sides for the girl he loves – only to say that actually, Narek was still committed to his cause and his mission. However, it’s a shame that this never really got a proper payoff, as Narek disappeared. His character arc feels incomplete, and as I’m fairly confident he won’t be returning for the show’s second season, we may never learn what happened to him after the events on Coppelius.

So that’s it. A handful of my theories for Star Trek: Picard Season 1 that never came to pass! I did manage to successfully predict a handful of (more obvious) plot points across the first season, so my theories didn’t all fail as hard as those listed above. The important thing, though, was that I had fun doing this. Thinking about the series and writing up the theories was really enjoyable at the time, and it’s something I hope to do with Discovery later in the year – at least, provided it has suitable theory-crafting material to work with!

Jean-Luc Picard will return for Season 2!

The important thing when considering fan theories is to remember that they’re just guesses and speculation. The showrunners, writers, and producers are the ones who craft the story, and they’re the ones who get the final say on how it’s going to pan out. Getting overly attached to any one theory – no matter how much we like it or how plausible it seems – really just means we’re setting ourselves up for disappointment. I could point to many projects in recent years which have suffered as a result of this, but all I really want to say is that, for those of you who followed my theories during Star Trek: Picard Season 1, I hope that I didn’t cause you any disappointment or frustration when I was wrong. At the end of the day, this is supposed to be fun and an excuse to spend more time in the Star Trek galaxy. Let’s all try to take fan theories with an extra-large pinch of salt!

Star Trek: Lower Decks is currently airing its first season – the second of three Star Trek projects in 2020. For all the problems that this year has thrown at us, having three different Star Trek shows to enjoy has been a blessing. If you missed it, I’ve reviewed the first episode of Lower Decks and I’ll soon be taking a look at episode 2, which will be available to watch (at least for viewers in the US and Canada) later today. And as mentioned I’ll be looking at Discovery when that airs in October. There’s no word on when exactly we can expect to see Season 2 of Star Trek: Picard. It has an optimistic release date of 2021, but given that California is still largely locked down and filming has yet to begin, I wouldn’t be surprised if that slips back. Regardless, whenever we get it I’ll be taking a look at the episodes and probably crafting a bunch more theories!

Star Trek: Picard Season 1 is available to stream now on CBS All Access in the United States, and on Amazon Prime Video in the United Kingdom and elsewhere. The Star Trek franchise – including Star Trek: Picard – is the copyright of ViacomCBS. This article contains the thoughts and opinions of one person only and is not intended to cause any offence.