Tag: Star Trek TOS

Categories
Trekking Through Compliance

Trekking Through Compliance – Episode 64 – Pattern Recognition Lessons from The Tholian Web

In this episode of Trekking Through Compliance, we consider the episode The Tholian, which aired on November 15, 1968, and occurred on Star Date 3842.3.

When the Enterprise attempts to ascertain the fate of the U.S.S. Defiant, which vanished 3 weeks ago, Spock reports strange sensor readings. They visually detect the Defiant, but sensors indicate it is not there. A landing party beams aboard, and when McCoy tries to touch one of the dead crew members, his hand passes right through him, revealing that the Defiant is starting to disintegrate. They all beam back to save Captain Kirk.

The weakening of the surrounding space fabric traps Kirk and the ship in a parallel universe. The appearance of two hostile Tholian ships disrupts the spatial interphase, which would have allowed Kirk to reenter his universe. Spock convinces the Tholians to wait until the interphase occurs, but the Enterprise cannot beam Kirk aboard. The Tholians then fire and damage the Enterprise.

In her cabin, Uhura sees a vision of Captain Kirk and reports to McCoy that he is alive. McCoy believes Uhura is going mad and confines her to sickbay. Scott then sees the same vision and rushes to the bridge, where everyone, including Spock, also sees it. The Enterprise can hold Kirk in the transporter beam at the next interphase and escape from the completed Tholian web by using the ship’s power to disrupt space-time.

Commentary

The episode follows the Enterprise crew as they investigate the fate of the USS Defiant and encounter the Tholian energy web. Key compliance lessons include identifying anomalies, contextual analysis, leveraging specialized expertise, adaptability, collaborative problem-solving, and proactive monitoring. The show also highlights exciting facts about the episode’s production and its place within Star Trek continuity.

Key Highlights

  • Key Plot Points and Developments
  • Fun Facts and Continuity Issues
  • Compliance Lessons from The Tholian Web

Resources

Excruciatingly Detailed Plot Summary by Eric W. Weisstein

MissionLogPodcast.com

Memory Alpha

Categories
Trekking Through Compliance

Trekking Through Compliance – Episode 63 – Continuous Monitoring from For the World is Hollow and I Have Touched the Sky

In this episode of Trekking Through Compliance, we consider the episode   For the World is Hollow and I Have Touched the Sky, which aired on November 1, 1968, Star Date Unknown.

McCoy calls Kirk to sick bay and informs him that the ship’s Chief Medical Officer (himself) has contracted an incurable fatal disease called xenopolycythemia and has only one year to live. However, McCoy assures Kirk he can still do his job until the end.

Suddenly, the Enterprise is attacked and diverts and determines their point of origin, an asteroid 200 km in diameter, which is a nuclear-powered spaceship on a collision course with planet Daran V. The inhabitants do not know that they are on a spacecraft, except for one old man who had climbed a mountain when he was young and intones “For the world is hollow and I have touched the sky.” After uttering this, the oracle punishes the old man with death using a subcutaneous “instrument of obedience.”

They can put the ship back on course. They also discover databanks of the Fabrini containing a great deal of medical knowledge, including the cure for McCoy’s xenopolycythemia.

Commentary

The episode synopsis includes McCoy’s diagnosis with a fatal disease and the Enterprise’s encounter with a nuclear-powered asteroid spaceship on a collision course with a planet. Through the storyline, Fox draws analogies to various continuous monitoring activities crucial for effective compliance programs, such as transaction monitoring, regulatory change monitoring, audit and incident monitoring, employee behavior monitoring, third-party risk monitoring, whistleblower hotline monitoring, regulatory development screening, and automated controls monitoring. Fox emphasizes the importance of proactive and continuous compliance monitoring to mitigate risks and uphold regulatory adherence.

Key Highlights

  • Story Breakdown and Key Events
  • Fun Fact: The Concept of an Interstellar Ark
  • Compliance Insights: Continuous Monitoring

Resources

Excruciatingly Detailed Plot Summary by Eric W. Weisstein

MissionLogPodcast.com

Memory Alpha

Categories
Trekking Through Compliance

Trekking Through Compliance – Episode 62 – Creating a Culture of Collaboration from the Day of the Dove

In this episode of Trekking Through Compliance, we consider the episode Day of the Dove, which aired on November 1, 1968, Star Date Unknown.

Story Synopsis

In this episode of Trekking Through Compliance, we consider the episode Day of the Dove, which aired on November 1, 1968, Star Date Unknown.

Called to Earth colony Beta 12A by a distress signal which claims that the colony is under attack. Kirk’s suspicions of Klingon’s involvement seem confirmed when the Enterprise detects the approach of a Klingon battlecruiser.

Klingon Commander Kang and his landing party then beam down and subdue the Enterprise’s landing party. He accuses the Enterprise of attacking and killing 400 Klingons aboard his ship and demands that Kirk beam the Klingon landing party up to the Enterprise. Meanwhile, Kirk accuses Kang of destroying the colonists of 12A.

Kirk pretends to comply with Kang’s order but warns Spock by pressing a special button on his communicator. Kang and his landing party are then beamed aboard and taken prisoner with the rest of the Klingon crew, who have been beamed to the Enterprise from their stricken ship. Soon after, the Enterprise spontaneously accelerates to Warp 9 and traps all but 38 crew members below deck.

When Kirk confronts Kang and accuses him of being responsible for trapping the Enterprise’s crew, phasers and room ornaments turn into swords. The Klingons escape and take control of engineering. Their attempt to cut off life support to the bridge is foiled, however, when normal functioning returns for no apparent reason.

Meanwhile, Spock ascertained that an unfamiliar alien life force was aboard. After watching the Enterprise crew and the Klingons turn at each other’s throats, Kirk realized that the alien was influencing matter, humans, and Klingons’ behavior, somehow deriving sustenance from their violent emotions.

Kirk and Mara use intra-ship beaming to pass through the Klingon defenses. With Mara’s help, and after fighting Kang in a sword battle involving all Klingons and Enterprise crew members, Kirk eventually convinces Kang to cease hostilities and participate in temporary gestures of goodwill. These drive the creature away, returning control to Kirk.

Commentary

The episode explores the struggle between the crew of the Enterprise and Klingons under mind control, leading to violent confrontations and a painful scene of Chekov attempting to rape Mara, Kang’s wife. Tom highlights the compliance lessons from this episode, emphasizing establishing a collaborative culture within organizations. Key strategies include leadership by example, cross-functional teamwork, transparent communication, fostering a ‘speak-up’ culture, and leveraging technology to enhance compliance. He closes with tips for continuous improvement and rewards for collaborative behaviors.

Key Highlights

  • Story Synopsis
  • Continuity Issues and Interesting Tidbits
  • Effective Strategies for Collaborative Compliance

Resources

Excruciatingly Detailed Plot Summary by Eric W. Weisstein

MissionLogPodcast.com

Memory Alpha

Categories
Trekking Through Compliance

Trekking Through Compliance – Episode 61 – Using Technology in Compliance Investigation found in Spectre of the Gun

In this episode of Trekking Through Compliance, we consider the episode Spectre of the Gun, which aired on October 25, 1968, with a Star Date of 4385.3.

On a mission to establish contact with the reclusive Melcotians, Kirk ignores the message of a space probe. The landing party encounters a Melcotian who informs them they are an outside disease that must be destroyed. Their trespassing is to be punished by death, and the pattern of their death will be taken from Kirk’s memories. As Kirk’s ancestors pioneered the West, the landing party was teleported to Tombstone, Arizona, on October 26, 1881.

Desperately, Bones and Spock cooperate to build a tranquilizer bomb that will incapacitate the Earps. Scotty volunteers to test the potion Bones has cooked up. Despite Bones’ careful preparation, something else is needed. Spock is the only one who understands the significance of this fact, saying, “You do not seem to understand. It did not function. But it must function.” Spock realizes that nothing around them is real; the whole scenario occurs in their minds.

They end up at the OK Corral, and the Melcotians, impressed that Kirk did not kill, then extend an invitation to establish relations with the Federation.

Commentary

Tom recounts the storyline where Kirk and his team face an illusionary recreation of the historic gunfight at the O.K. Corral. The discussion extends to how technology can aid compliance officers in investigations, covering seven key areas: data analytics and visualization, automated monitoring systems, digital forensics, collaboration platforms, predictive analytics and machine learning, robotic process automation, and regulatory compliance management platforms. Through these techniques, compliance officers can improve the effectiveness and efficiency of their compliance processes.

Key Highlights

  • Key Moments and Analysis
  • Technology in Compliance Investigations
  • Conclusion and Next Episode Preview

Resources

Excruciatingly Detailed Plot Summary by Eric W. Weisstein

MissionLogPodcast.com

Memory Alpha

Categories
Trekking Through Compliance

Trekking Through Compliance – Episode 60 – Ethical Lessons from Is There No Truth in Beauty

In this episode of Trekking Through Compliance, we consider the episode Is There No Truth in Beauty, which aired on October 18, 1968, Star Date 5630.7.

The Enterprise is given the mission of transporting the Medusan ambassador Kollos, a member of a species so ugly that the mere sight of it causes humans to go insane back to his home planet. The ambassador arrives enclosed in a specially designed box and is accompanied by the telepath Dr. Miranda Jones, who is looking after his needs. Like Spock, Jones can look at a Medusan through a visor, supposedly because she has studied on Vulcan but in reality because she is blind.

Larry Marvick, one of the Enterprise’s designers, also beamed aboard. He seeks revenge against Kollos for taking Miranda away from him but is driven insane when he inadvertently looks at Kollos while attempting to shoot him with a phaser. The insane Marvick commandeers the Enterprise and pilots it to an unknown location outside the galaxy.

Using the visor to protect his human half from the sight of the Medusan, Spock melds minds with Kolos and returns the Enterprise to its galaxy. Miranda and Kollos are then delivered to their destination. Upon parting, Kirk presents Miranda with a rose. Miranda queries, “I suppose it has thorns,” and Kirk responds, “I never met a rose that didn’t.”

Commentary

In this episode of Trekking Through Compliance, the Enterprise must transport the Medusan Ambassador Kolos, a being so hideous it drives humans insane on sight, back to his home planet. Key characters include Dr. Miranda Jones, a telepath who cares for Kolos, and Larry Marvick, an engineer infatuated with Jones. The episode deals with cultural sensitivity, safeguarding sensitive information, impartial decision-making, balancing safety with individual rights, transparency, and ethical decision-making. The show notes also touch on how these themes translate to best practices for compliance professionals. Additionally, the episode covers exciting trivia, such as the creation of the Itik by Gene Roddenberry and references to Shakespeare’s ‘The Tempest.’

Key Highlights

  • Story Synopsis: Is There No Truth in Beauty?
  • Fun Facts and Behind the Scenes
  • Ethical Lessons for Compliance Officers

Resources

Excruciatingly Detailed Plot Summary by Eric W. Weisstein

MissionLogPodcast.com

Memory Alpha

Categories
Trekking Through Compliance

Trekking Through Compliance – Episode 59 – Investigative Lessons from And the Children Shall Lead

In this episode of Trekking Through Compliance, we consider the episode And The Children Shall Lead, which aired on October 11, 1968, Star Date 5027.1.

Story Synopsis

This episode explores themes of manipulation and the power of belief. The Enterprise crew responds to a distress signal from the Federation colony on Triacus and discovers all the adults dead from an apparent suicide, leaving only the children alive.

Captain Kirk and his team find the children seemingly unaffected and playing happily, which raises suspicion. Dr. McCoy’s medical scans show no physical harm or unusual conditions, but the children’s behavior is concerning. It soon becomes evident that the children are under the influence of an alien entity named Gorgan, who appears to them as a friendly figure promising them power and control. Gorgan manipulates the children to help him take over the Enterprise.

The children use their telekinetic abilities, granted by Gorgan, to take control of the ship, causing chaos among the crew. They create illusions that play on the crew members’ deepest fears, further destabilizing the situation. Kirk and Spock investigate and uncover historical data about the previous encounters with Gorgan and how he exploits the innocence and trust of children to achieve his goals.

Realizing that Gorgan’s power depends on the children’s belief in him, Kirk devises a plan to break his hold. He confronts the children with the truth about their parents’ deaths and shows them how Gorgan has deceived them. The children, seeing the reality of their actions and the consequences, withdraw their belief and support from Gorgan.

Without the children’s belief to sustain him, Gorgan loses power and vanishes. The children, freed from his influence, begin to process their grief and the reality of their situation. The episode concludes with the Enterprise leaving Triacus and restoring order and safety to the ship.

Commentary

I consider this episode the worst episode of the original Star Trek series. The episode, which first aired on October 11, 1968, involves the Enterprise crew investigating the mysterious mass suicide of adults on the scientific colony Triacus and the subsequent manipulation of their children by an alien entity known as the Gorgon. Despite the episode’s shortcomings, Fox identifies key compliance and investigative lessons, including thorough fact-finding, identifying patterns, adapting techniques, engaging with vulnerable parties, addressing ethical dilemmas, and leveraging cross-functional expertise.

Key Highlights

  • Story Synopsis: And the Children Shall Lead
  • Critical Reception and Fun Facts
  • Compliance and Leadership Lessons

Resources

Excruciatingly Detailed Plot Summary by Eric W. Weisstein

MissionLogPodcast.com

Memory Alpha

Categories
Trekking Through Compliance

Trekking Through Compliance – Episode 58 – Ethical Lessons from The Paradise Syndrome

In this episode of Trekking Through Compliance, we consider the episode The Paradise Syndrome, which aired on October 4, 1968, with a Star Date of 4842.6.

Story Synopsis

The crew of the USS Enterprise discovers an idyllic planet inhabited by a peaceful, Native American-like tribe. Captain Kirk, suffering from amnesia due to the effects of an ancient obelisk, is mistaken for a deity by the inhabitants. He begins to live among them, forming a deep bond with a woman named Miramanee, whom he marries.

While Kirk adapts to his new life, the Enterprise faces a critical mission to deflect an asteroid on a collision course with the planet. Spock and McCoy work tirelessly to solve the mystery of the obelisk and restore Kirk’s memory. As the asteroid approaches, Kirk eventually regains his memory, and the truth about the obelisk is revealed: it is a deflector device left by an advanced civilization to protect the planet.

Tragically, Kirk’s return to his true identity and the intervention come too late to save Miramanee. She dies from injuries inflicted by her tribe, who turn against her when the deflector initially fails to work. The episode ends with the asteroid being diverted and a heartbroken Kirk resuming his duties aboard the Enterprise, forever affected by his experiences on the planet.

Commentary

The episode’s synopsis includes Kirk, Spock, and McCoy’s mission to prevent an asteroid from destroying a planet inhabited by Native American tribes. Amidst Kirk’s memory loss and the Enterprise’s struggle to deflect the asteroid, themes of cultural sensitivity, informed consent, and unintended consequences are explored. The discussion highlights five key compliance and ethical lessons: cultural preservation, informed consent, responsibility for unintended consequences, balancing progress with preservation, and maintaining transparency and accountability.

Key Highlights

  • Kirk’s Amnesia and Integration
  • Enterprise’s Struggle with the Asteroid
  • Climax and Resolution
  • Ethical Lessons from The Paradise Syndrome

Resources

Excruciatingly Detailed Plot Summary by Eric W. Weisstein

MissionLogPodcast.com

Memory Alpha

Categories
Trekking Through Compliance

Trekking Through Compliance – Episode 57 – Compliance Leadership Lessons from The Enterprise Incident

In this episode of Trekking Through Compliance, we consider the episode The Enterprise Incident aired on September 27, 1968, Star Date 5031.3.

Story Synopsis

The Enterprise Incident follows Captain James T. Kirk and his crew undertaking a daring and covert mission within the Neutral Zone, the border region between the United Federation of Planets and the Romulan Star Empire.

The episode begins with Captain Kirk displaying erratic behavior, directing the U.S.S. Enterprise into the Neutral Zone without explanation. This action provokes an aggressive response from Romulan ships, resulting in the Enterprise being captured. The Romulan Commander, a determined and intelligent woman, boards the Enterprise and questions Kirk and Spock.

Kirk’s seemingly unstable behavior escalates, leading Spock to declare his captain unfit for command. Kirk attacks Spock but is subdued, and Spock, following Vulcan discipline, appears to kill him with a nerve pinch. This move results in Kirk’s confinement, during which the Romulan Commander attempts to persuade Spock to defect, appealing to his Vulcan logic and offering him a position in the Romulan fleet.

In reality, the entire sequence is a meticulously planned ruse. Disguised as a Romulan, Kirk infiltrates the Romulan vessel to steal a highly advanced cloaking device. Dr. McCoy’s medical skills and Spock’s loyalty are crucial in maintaining the charade. Kirk successfully retrieves the cloaking device and returns it to the Enterprise. Meanwhile, Spock stalls the Romulan Commander, revealing the truth only when necessary.

The episode culminates with the Enterprise escaping with the cloaking device. The Romulan Commander, realizing Spock’s deception, is left with a sense of betrayal and admiration for her adversaries. This mission highlights the strategic acumen and boldness of the Starfleet crew, as well as the complex interplay of loyalty and deception in espionage. “The Enterprise Incident” remains a standout episode for its suspenseful plot and the nuanced portrayal of its characters.

Commentary

The discussion focuses on key leadership lessons for compliance professionals, including ethical decision-making under pressure, maintaining transparency, managing sensitive information and technology, navigating complex regulatory environments, and balancing risk and innovation. The episode highlights how Captain Kirk and his crew’s risky mission to steal a Romulan cloaking device illustrates these principles.

Key Highlights

  • Story Synopsis: The Enterprise Incident
  • Fun Fact: Spock’s Romantic Scene Controversy
  • Reception and Critique of The Episode
  • Compliance Leadership Lessons from The Enterprise Incident

Resources

Excruciatingly Detailed Plot Summary by Eric W. Weisstein

MissionLogPodcast.com

Memory Alpha

Categories
Trekking Through Compliance

Trekking Through Compliance – Episode 56 – Business Continuity Lessons from Spock’s Brain

In this episode of Trekking Through Compliance, we consider the episode Spock’s Brain, which aired on September 20, 1968, and occurred on Star Date 5431.4.

Story Synopsis

Almost universally panned as the work Star Trek TOS episode, the story involves a race of beings who kidnap Spock’s brain to run a planet-wide computer system for insipid beings, both male and female.

“Spock’s Brain” is the first episode of the third season of “Star Trek: The Original Series.” The USS Enterprise, commanded by Captain Kirk, encounters a mysterious and advanced woman who boards the ship, renders the crew unconscious, and steals Spock’s brain. The crew awakens to find Spock alive but in a comatose state. Using the ship’s sensors, they trace the woman’s path to a primitive planet with a technologically advanced underground civilization.

Kirk, Dr. McCoy, and a landing party beam down and discover that the civilization is composed entirely of women who rely on a central computer, the “Controller,” to manage their society. The Controller, now revealed to be Spock’s brain, is essential for their survival. McCoy uses a special device to temporarily enhance his surgical skills, allowing him to reattach Spock’s brain while keeping him conscious enough to guide the procedure.

Ultimately, Spock’s brain is successfully reconnected, and he recovers fully. The crew leaves the planet, disrupting civilization’s dependence on the Controller and initiating a new development phase. The episode is often noted for its unusual and campy premise, becoming one of the more infamous entries in the Star Trek series.

Commentary

Widely regarded as the worst episode in TOS, it centers on removing and retrieving Spock’s brain. Fox draws parallels between the episode and business continuity planning. He outlines six key organizational strategies for maintaining functionality during personnel absences: critical role assessment, cross-training, comprehensive documentation, prioritizing operations, emergency succession planning, and compliance testing. The analysis turns a campy and criticized Star Trek episode into valuable business continuity lessons.

Key Highlights

  • Story Synopsis of Spock’s Brain
  • Fun Facts and Legacy of Spock’s Brain
  • Business Continuity Lessons from Spock’s Brain
  • Practical Compliance Strategies

Resources

Excruciatingly Detailed Plot Summary by Eric W. Weisstein

MissionLogPodcast.com

Memory Alpha

 

Categories
Blog

Setting the Tone at the Top in Star Trek: Devil in the Dark

In the world of compliance, the tone at the top is paramount. It sets the stage for the organizational culture, influencing every business layer. As an award-winning compliance blogger, I often seek examples from popular media to illustrate key compliance principles. One compelling example comes from Star Trek: The Original Series (TOS). The episode “The Devil in the Dark” demonstrates effective leadership and ethical decision-making, embodying the first Hallmark of an Effective Compliance Program: tone at the top.

Summary of The Devil in the Dark

In this episode, Captain Kirk and his crew are summoned to a mining colony on the planet Janus VI, where a mysterious creature has been killing miners and sabotaging equipment. The miners are desperate and demand the creature’s destruction. However, as the Enterprise crew investigates, they uncover that the creature, known as the Horta, is intelligent and acting out of self-defense to protect its eggs, which the miners have unknowingly destroyed.

Kirk, guided by his moral compass and influenced by Spock’s logical counsel, chooses to communicate with the Horta instead of destroying it. This decision leads to a peaceful resolution, saving the miners and the Horta and establishing a cooperative relationship between the two species.

Leadership and Ethical Decision-Making

Captain Kirk’s handling of the situation is a textbook example of setting the right tone at the top. His leadership in “The Devil in the Dark” highlights several critical aspects of effective compliance leadership:

1. Setting an Ethical Example. From the outset, Kirk exemplifies ethical leadership. Kirk remains open-minded and cautious despite the miners’ insistence on killing the creature. He refuses to jump to conclusions, instead opting to gather all necessary information before deciding. This approach mirrors the importance of due diligence in compliance practices, where leaders must ensure they have a comprehensive understanding of situations before acting.

  1. Encouraging a Culture of Integrity. Kirk’s decision to explore non-violent solutions fosters a culture of integrity among his crew. By valuing life and seeking understanding over immediate destruction, he sets a precedent for ethical behavior. This decision demonstrates that ethical considerations should be paramount, even when facing significant pressure. In a corporate context, this translates to promoting a culture where employees feel empowered to act ethically and report misconduct without fear of retribution.
  2. Transparent Communication. Throughout the episode, Kirk maintains open and transparent communication with his team. He discusses options, seeks input from his officers, and explains his reasoning behind decisions. This transparency fosters trust and ensures all team members align with the organization’s mission and values. This underscores the importance of clear and honest communication for compliance leaders in promoting a compliant and ethical workplace.
  3. Empathy and Understanding. Kirk’s empathy towards the Horta is a defining moment in the episode. Instead of viewing the creature as a threat, he considers its perspective and motivations. This empathy leads to a peaceful resolution and mutual understanding. In the corporate world, leaders who demonstrate empathy can better understand the concerns of their employees and stakeholders, fostering a more inclusive and supportive work environment.
  4. Decision-Making Under Pressure. Kirk’s ability to make ethical decisions under pressure is another critical aspect of his leadership. Faced with the miners’ demands and the immediate threat the Horta poses, he remains composed and focused on finding a solution that upholds the Enterprise’s values. This mirrors the challenges compliance leaders face, who must often navigate complex situations and make difficult decisions that align with ethical standards and regulatory requirements.

Lessons for Compliance Leaders

The Devil in the Dark offers several valuable lessons for compliance leaders seeking to establish and maintain a strong tone at the top.

  1. Lead by Example. Leaders must consistently demonstrate ethical behavior and decision-making. This sets a standard for the entire organization and encourages employees to follow suit. As seen with Captain Kirk, leading by example can inspire confidence and trust among team members.
  2. Foster a Culture of Integrity. Creating a culture where integrity is valued and ethical behavior is rewarded is crucial. This involves setting expectations and providing the necessary support and resources for employees to act ethically. Compliance leaders should encourage open dialogue and create an environment where employees feel safe reporting concerns.
  3. Prioritize Transparency. Clear and transparent communication is key to building trust and ensuring alignment within the organization. Leaders should be open about their decisions and reasoning, fostering an environment of honesty and accountability.
  4. Demonstrate Empathy. Understanding and considering the perspectives of others can lead to more effective and ethical decision-making. Leaders who show empathy are better equipped to address concerns and build strong, collaborative relationships.
  5. Make Ethical Decisions Under Pressure. Compliance leaders often face high-pressure situations where the right course of action may not be immediately clear. Maintaining composure and staying true to ethical principles is essential. As demonstrated by Captain Kirk, ethical decision-making can lead to positive outcomes, even in the most challenging circumstances.

Captain Kirk exemplifies the core principles of effective leadership and ethical decision-making in The Devil in the Dark, setting a strong tone at the top. His actions demonstrate the importance of leading by example, fostering a culture of integrity, prioritizing transparency, demonstrating empathy, and making ethical decisions under pressure. For compliance leaders, these lessons are invaluable. By embracing these principles, leaders can create a compliant and ethical organizational culture that meets regulatory requirements and promotes long-term success and trust.

As we navigate the complexities of the modern business world, let us remember the timeless lessons from Captain Kirk and the crew of the Enterprise, boldly going where few compliance programs have gone before.