diff --git a/python/meltdown-mitigation/.exercism/config.json b/python/meltdown-mitigation/.exercism/config.json
new file mode 100644
index 0000000..eb88d8b
--- /dev/null
+++ b/python/meltdown-mitigation/.exercism/config.json
@@ -0,0 +1,22 @@
+{
+  "authors": [
+    "sachsom95",
+    "BethanyG"
+  ],
+  "contributors": [
+    "kbuc"
+  ],
+  "files": {
+    "solution": [
+      "conditionals.py"
+    ],
+    "test": [
+      "conditionals_test.py"
+    ],
+    "exemplar": [
+      ".meta/exemplar.py"
+    ]
+  },
+  "icon": "circular-buffer",
+  "blurb": "Learn about conditionals and avoid a meltdown by developing a simple control system for a Nuclear Reactor."
+}
diff --git a/python/meltdown-mitigation/.exercism/metadata.json b/python/meltdown-mitigation/.exercism/metadata.json
new file mode 100644
index 0000000..997bfc3
--- /dev/null
+++ b/python/meltdown-mitigation/.exercism/metadata.json
@@ -0,0 +1 @@
+{"track":"python","exercise":"meltdown-mitigation","id":"b1c401666a194150aa374afe91089205","url":"https://exercism.org/tracks/python/exercises/meltdown-mitigation","handle":"Chomp1295","is_requester":true,"auto_approve":false}
\ No newline at end of file
diff --git a/python/meltdown-mitigation/HELP.md b/python/meltdown-mitigation/HELP.md
new file mode 100644
index 0000000..f931e6c
--- /dev/null
+++ b/python/meltdown-mitigation/HELP.md
@@ -0,0 +1,130 @@
+# Help
+
+## Running the tests
+
+We use [pytest][pytest: Getting Started Guide] as our website test runner.
+You will need to install `pytest` on your development machine if you want to run tests for the Python track locally.
+You should also install the following `pytest` plugins:
+
+- [pytest-cache][pytest-cache]
+- [pytest-subtests][pytest-subtests]
+
+Extended information can be found in our website [Python testing guide][Python track tests page].
+
+
+### Running Tests
+
+To run the included tests, navigate to the folder where the exercise is stored using `cd` in your terminal (_replace `{exercise-folder-location}` below with your path_).
+Test files usually end in `_test.py`, and are the same tests that run on the website when a solution is uploaded.
+
+Linux/MacOS
+```bash
+$ cd {path/to/exercise-folder-location}
+```
+
+Windows
+```powershell
+PS C:\Users\foobar> cd {path\to\exercise-folder-location}
+```
+
+<br>
+
+Next, run the `pytest` command in your terminal, replacing `{exercise_test.py}` with the name of the test file:
+
+Linux/MacOS
+```bash
+$ python3 -m pytest -o markers=task {exercise_test.py}
+==================== 7 passed in 0.08s ====================
+```
+
+Windows
+```powershell
+PS C:\Users\foobar> py -m pytest -o markers=task {exercise_test.py}
+==================== 7 passed in 0.08s ====================
+```
+
+
+### Common options
+- `-o` : override default `pytest.ini` (_you can use this to avoid marker warnings_)
+- `-v` : enable verbose output.
+- `-x` : stop running tests on first failure.
+- `--ff` : run failures from previous test before running other test cases.
+
+For additional options, use `python3 -m pytest -h` or `py -m pytest -h`.
+
+
+### Fixing warnings
+
+If you do not use `pytest -o markers=task` when invoking `pytest`, you might receive a `PytestUnknownMarkWarning` for tests that use our new syntax:
+
+```bash
+PytestUnknownMarkWarning: Unknown pytest.mark.task - is this a typo?  You can register custom marks to avoid this warning - for details, see https://docs.pytest.org/en/stable/mark.html
+```
+
+To avoid typing `pytest -o markers=task` for every test you run, you can use a `pytest.ini` configuration file.
+We have made one that can be downloaded from the top level of the Python track directory: [pytest.ini][pytest.ini].
+
+You can also create your own `pytest.ini` file with the following content:
+
+```ini
+[pytest]
+markers =
+    task: A concept exercise task.
+```
+
+Placing the `pytest.ini` file in the _root_ or _working_ directory for your Python track exercises will register the marks and stop the warnings.
+More information on pytest marks can be found in the `pytest` documentation on [marking test functions][pytest: marking test functions with attributes] and the `pytest` documentation on [working with custom markers][pytest: working with custom markers].
+
+Information on customizing pytest configurations can be found in the `pytest` documentation on [configuration file formats][pytest: configuration file formats].
+
+
+### Extending your IDE or Code Editor
+
+Many IDEs and code editors have built-in support for using `pytest` and other code quality tools.
+Some community-sourced options can be found on our [Python track tools page][Python track tools page].
+
+[Pytest: Getting Started Guide]: https://docs.pytest.org/en/latest/getting-started.html
+[Python track tools page]: https://exercism.org/docs/tracks/python/tools
+[Python track tests page]: https://exercism.org/docs/tracks/python/tests
+[pytest-cache]:http://pythonhosted.org/pytest-cache/
+[pytest-subtests]:https://github.com/pytest-dev/pytest-subtests
+[pytest.ini]: https://github.com/exercism/python/blob/main/pytest.ini
+[pytest: configuration file formats]: https://docs.pytest.org/en/6.2.x/customize.html#configuration-file-formats
+[pytest: marking test functions with attributes]: https://docs.pytest.org/en/6.2.x/mark.html#raising-errors-on-unknown-marks
+[pytest: working with custom markers]: https://docs.pytest.org/en/6.2.x/example/markers.html#working-with-custom-markers
+
+## Submitting your solution
+
+You can submit your solution using the `exercism submit conditionals.py` command.
+This command will upload your solution to the Exercism website and print the solution page's URL.
+
+It's possible to submit an incomplete solution which allows you to:
+
+- See how others have completed the exercise
+- Request help from a mentor
+
+## Need to get help?
+
+If you'd like help solving the exercise, check the following pages:
+
+- The [Python track's documentation](https://exercism.org/docs/tracks/python)
+- The [Python track's programming category on the forum](https://forum.exercism.org/c/programming/python)
+- [Exercism's programming category on the forum](https://forum.exercism.org/c/programming/5)
+- The [Frequently Asked Questions](https://exercism.org/docs/using/faqs)
+
+Should those resources not suffice, you could submit your (incomplete) solution to request mentoring.
+
+Below are some resources for getting help if you run into trouble:
+
+- [The PSF](https://www.python.org) hosts Python downloads, documentation, and community resources.
+- [The Exercism Community on Discord](https://exercism.org/r/discord)
+- [Python Community on Discord](https://pythondiscord.com/) is a very helpful and active community.
+- [/r/learnpython/](https://www.reddit.com/r/learnpython/) is a subreddit designed for Python learners.
+- [#python on Libera.chat](https://www.python.org/community/irc/) this is where the core developers for the language hang out and get work done.
+- [Python Community Forums](https://discuss.python.org/)
+- [Free Code Camp Community Forums](https://forum.freecodecamp.org/)
+- [CodeNewbie Community Help Tag](https://community.codenewbie.org/t/help)
+- [Pythontutor](http://pythontutor.com/) for stepping through small code snippets visually.
+
+Additionally, [StackOverflow](http://stackoverflow.com/questions/tagged/python) is a good spot to search for your problem/question to see if it has been answered already.
+ If not - you can always [ask](https://stackoverflow.com/help/how-to-ask) or [answer](https://stackoverflow.com/help/how-to-answer) someone else's question.
\ No newline at end of file
diff --git a/python/meltdown-mitigation/HINTS.md b/python/meltdown-mitigation/HINTS.md
new file mode 100644
index 0000000..bee2779
--- /dev/null
+++ b/python/meltdown-mitigation/HINTS.md
@@ -0,0 +1,50 @@
+# Hints
+
+## General
+
+- The Python Docs on [Control Flow Tools][control flow tools] and the Real Python tutorial on [conditionals][real python conditionals] are great places to start.
+- The Python Docs on [Boolean Operations][boolean operations] can be a great refresher on `bools`, as can the Real Python tutorial on [booleans][python booleans].
+- The Python Docs on [Comparisons][comparisons] and [comparisons examples][python comparisons examples] can be a great refresher for comparisons.
+
+## 1. Check for criticality
+
+- Comparison operators ([comparisons][comparisons review]) and boolean operations ([concept:python/bools]()) can be combined and used with conditionals.
+- Conditional expressions must evaluate to `True` or `False`.
+- `else` can be used for a code block that will execute when all conditional tests return `False`.
+
+  ```python
+     >>> item = 'blue'
+     >>> item_2 = 'green'
+     
+     >>>  if len(item) >= 3 and len(item_2) < 5:
+            print('Both pass the test!')
+          elif len(item) >= 3 or len(item_2) < 5:
+            print('One passes the test!')
+          else:
+            print('None pass the test!')
+    ...
+    One passes the test!
+  ```
+
+## 2. Determine the Power output range
+
+- Comparison operators can be combined and used with conditionals.
+- Any number of `elif` statements can be used as decision "branches".
+- Each "branch" can have a separate `return`, although it might be considered "bad form" by linting tools.
+- If the linter complains, consider assigning the output of a branch to a common variable, and then `return`ing that variable.
+
+## 3. Fail Safe Mechanism
+
+- Comparison operators can be combined and used with conditionals.
+- Any number of `elif` statements can be used as decision "branches".
+- Each "branch" can have a separate `return`, although it might be considered "bad form" by linting tools.
+- If the linter complains, consider assigning the output of a branch to a common variable, and then `return`ing that variable.
+
+
+[boolean operations]: https://docs.python.org/3/library/stdtypes.html#boolean-operations-and-or-not
+[comparisons review]: https://www.learnpython.dev/02-introduction-to-python/090-boolean-logic/20-comparisons/
+[comparisons]: https://docs.python.org/3/library/stdtypes.html#comparisons
+[control flow tools]: https://docs.python.org/3/tutorial/controlflow.html
+[python booleans]: https://realpython.com/python-boolean/
+[python comparisons examples]: https://www.tutorialspoint.com/python/comparison_operators_example.htm
+[real python conditionals]: https://realpython.com/python-conditional-statements/
\ No newline at end of file
diff --git a/python/meltdown-mitigation/README.md b/python/meltdown-mitigation/README.md
new file mode 100644
index 0000000..d16704e
--- /dev/null
+++ b/python/meltdown-mitigation/README.md
@@ -0,0 +1,172 @@
+# Meltdown Mitigation
+
+Welcome to Meltdown Mitigation on Exercism's Python Track.
+If you need help running the tests or submitting your code, check out `HELP.md`.
+If you get stuck on the exercise, check out `HINTS.md`, but try and solve it without using those first :)
+
+## Introduction
+
+In Python, [`if`][if statement], `elif` (_a contraction of 'else and if'_) and `else` statements are used to [control the flow][control flow tools] of execution and make decisions in a program.
+Unlike many other programming languages, Python versions 3.9 and below do not offer a formal case-switch statement, instead using multiple `elif` statements to serve a similar purpose.
+
+Python 3.10 introduces a variant case-switch statement called `structural pattern matching`, which will be covered separately in another concept.
+
+Conditional statements use expressions that must resolve to `True` or `False` -- either by returning a `bool` type directly, or by evaluating as ["truthy" or "falsy"][truth value testing].
+
+```python
+x = 10
+y = 5
+
+# The comparison '>' returns the bool 'True',
+# so the statement is printed.
+if x > y:
+    print("x is greater than y")
+...
+>>> x is greater than y
+```
+
+When paired with `if`, an optional `else` code block will execute when the original `if` condition evaluates to `False`:
+
+```python
+x = 5
+y = 10
+
+# The comparison '>' here returns the bool 'False',
+# so the 'else' block is executed instead of the 'if' block.
+if x > y:
+    print("x is greater than y")
+else:
+    print("y is greater than x")
+...
+>>> y is greater than x
+```
+
+`elif` allows for multiple evaluations/branches.
+
+```python
+x = 5
+y = 10
+z = 20
+
+# The 'elif' statement allows for the checking of more conditions.
+if x > y:
+    print("x is greater than y and z")
+elif y > z:
+    print("y is greater than x and z")
+else:
+    print("z is greater than x and y")
+...
+>>> z is greater than x and y
+```
+
+[Boolean operations][boolean operations] and [comparisons][comparisons] can be combined with conditionals for more complex testing:
+
+```python
+>>> def classic_fizzbuzz(number):
+        if number % 3 == 0 and number % 5 == 0:
+            say = 'FizzBuzz!'
+        elif number % 5 == 0:
+            say = 'Buzz!'
+        elif number % 3 == 0:
+            say = 'Fizz!'
+        else:
+            say = str(number)
+        
+        return say
+
+>>> classic_fizzbuzz(15)
+'FizzBuzz!'
+
+>>> classic_fizzbuzz(13)
+'13'
+```
+
+[boolean operations]: https://docs.python.org/3/library/stdtypes.html#boolean-operations-and-or-not
+[comparisons]: https://docs.python.org/3/library/stdtypes.html#comparisons
+[control flow tools]: https://docs.python.org/3/tutorial/controlflow.html#more-control-flow-tools
+[if statement]: https://docs.python.org/3/reference/compound_stmts.html#the-if-statement
+[truth value testing]: https://docs.python.org/3/library/stdtypes.html#truth-value-testing
+
+## Instructions
+
+In this exercise, we'll develop a simple control system for a nuclear reactor.
+
+For a reactor to produce the power it must be in a state of _criticality_.
+If the reactor is in a state less than criticality, it can become damaged.
+If the reactor state goes beyond criticality, it can overload and result in a meltdown.
+We want to mitigate the chances of meltdown and correctly manage reactor state.
+
+The following three tasks are all related to writing code for maintaining ideal reactor state.
+
+## 1. Check for criticality
+
+The first thing a control system has to do is check if the reactor is balanced in criticality.
+A reactor is said to be critical if it satisfies the following conditions:
+
+- The temperature is less than 800 K.
+- The number of neutrons emitted per second is greater than 500.
+- The product of temperature and neutrons emitted per second is less than 500000.
+
+Implement the function `is_criticality_balanced()` that takes `temperature` measured in kelvin and `neutrons_emitted` as parameters, and returns `True` if the criticality conditions are met, `False` if not.
+
+```python
+>>> is_criticality_balanced(750, 600)
+True
+```
+
+## 2. Determine the Power output range
+
+Once the reactor has started producing power its efficiency needs to be determined.
+Efficiency can be grouped into 4 bands:
+
+1. `green` -> efficiency of 80% or more,
+2. `orange` -> efficiency of less than 80% but at least 60%,
+3. `red` -> efficiency below 60%, but still 30% or more,
+4. `black` ->  less than 30% efficient.
+
+The percentage value can be calculated as `(generated_power/theoretical_max_power)*100`
+where `generated_power` = `voltage` * `current`.
+Note that the percentage value is usually not an integer number, so make sure to consider the
+proper use of the `<` and `<=` comparisons.
+
+Implement the function `reactor_efficiency(<voltage>, <current>, <theoretical_max_power>)`, with three parameters: `voltage`,
+`current`, and `theoretical_max_power`.
+This function should return the efficiency band of the reactor : 'green', 'orange', 'red', or 'black'.
+
+```python
+>>> reactor_efficiency(200,50,15000)
+'orange'
+```
+
+## 3. Fail Safe Mechanism
+
+Your final task involves creating a fail-safe mechanism to avoid overload and meltdown.
+This mechanism will determine if the reactor is below, at, or above the ideal criticality threshold.
+Criticality can then be increased, decreased, or stopped by inserting (or removing) control rods into the reactor.
+
+Implement the function called `fail_safe()`, which takes 3 parameters: `temperature` measured in kelvin,
+`neutrons_produced_per_second`, and `threshold`, and outputs a status code for the reactor.
+
+- If `temperature * neutrons_produced_per_second` < 90% of `threshold`, output a status code of 'LOW'
+  indicating that control rods must be removed to produce power.
+
+- If the value `temperature * neutrons_produced_per_second` is within 10% of the `threshold` (so either 0-10% less than the threshold, at the threshold, or 0-10% greater than the threshold), the reactor is in _criticality_ and the status code of 'NORMAL' should be output, indicating that the reactor is in optimum condition and control rods are in an ideal position.
+
+- If `temperature * neutrons_produced_per_second` is not in the above-stated ranges, the reactor is
+  going into meltdown and a status code of 'DANGER' must be passed to immediately shut down the reactor.
+
+```python
+>>> fail_safe(temperature=1000, neutrons_produced_per_second=30, threshold=5000)
+'DANGER'
+```
+
+## Source
+
+### Created by
+
+- @sachsom95
+- @BethanyG
+
+### Contributed to by
+
+- @kbuc
\ No newline at end of file
diff --git a/python/meltdown-mitigation/conditionals.py b/python/meltdown-mitigation/conditionals.py
new file mode 100644
index 0000000..ef0bb26
--- /dev/null
+++ b/python/meltdown-mitigation/conditionals.py
@@ -0,0 +1,79 @@
+"""Functions to prevent a nuclear meltdown."""
+
+
+def is_criticality_balanced(temperature, neutrons_emitted):
+    """Verify criticality is balanced.
+
+    :param temperature: int or float - temperature value in kelvin.
+    :param neutrons_emitted: int or float - number of neutrons emitted per second.
+    :return: bool - is criticality balanced?
+
+    A reactor is said to be critical if it satisfies the following conditions:
+    - The temperature is less than 800 K.
+    - The number of neutrons emitted per second is greater than 500.
+    - The product of temperature and neutrons emitted per second is less than 500000.
+    """
+
+    if (
+        temperature < 800
+        and neutrons_emitted > 500
+        and temperature * neutrons_emitted < 500000
+    ):
+        return True
+
+    return False
+
+
+def reactor_efficiency(voltage, current, theoretical_max_power):
+    """Assess reactor efficiency zone.
+
+    :param voltage: int or float - voltage value.
+    :param current: int or float - current value.
+    :param theoretical_max_power: int or float - power that corresponds to a 100% efficiency.
+    :return: str - one of ('green', 'orange', 'red', or 'black').
+
+    Efficiency can be grouped into 4 bands:
+
+    1. green -> efficiency of 80% or more,
+    2. orange -> efficiency of less than 80% but at least 60%,
+    3. red -> efficiency below 60%, but still 30% or more,
+    4. black ->  less than 30% efficient.
+
+    The percentage value is calculated as
+    (generated power/ theoretical max power)*100
+    where generated power = voltage * current
+    """
+
+    efficiency = ((voltage * current) / theoretical_max_power) * 100
+
+    if efficiency >= 80:
+        return "green"
+    if efficiency >= 60:
+        return "orange"
+    if efficiency >= 30:
+        return "red"
+
+    return "black"
+
+
+def fail_safe(temperature, neutrons_produced_per_second, threshold):
+    """Assess and return status code for the reactor.
+
+    :param temperature: int or float - value of the temperature in kelvin.
+    :param neutrons_produced_per_second: int or float - neutron flux.
+    :param threshold: int or float - threshold for category.
+    :return: str - one of ('LOW', 'NORMAL', 'DANGER').
+
+    1. 'LOW' -> `temperature * neutrons per second` < 90% of `threshold`
+    2. 'NORMAL' -> `temperature * neutrons per second` +/- 10% of `threshold`
+    3. 'DANGER' -> `temperature * neutrons per second` is not in the above-stated ranges
+    """
+
+    if temperature * neutrons_produced_per_second < threshold * 0.9:
+        return "LOW"
+
+    if temperature * neutrons_produced_per_second <= threshold * 1.1:
+        return "NORMAL"
+
+    if temperature * neutrons_produced_per_second > threshold * 1.1:
+        return "DANGER"
diff --git a/python/meltdown-mitigation/conditionals_test.py b/python/meltdown-mitigation/conditionals_test.py
new file mode 100644
index 0000000..5e48ca3
--- /dev/null
+++ b/python/meltdown-mitigation/conditionals_test.py
@@ -0,0 +1,82 @@
+import unittest
+import pytest
+from conditionals import (is_criticality_balanced,
+                          reactor_efficiency,
+                          fail_safe)
+
+
+class MeltdownMitigationTest(unittest.TestCase):
+    """Test cases for Meltdown mitigation exercise.
+    """
+
+    @pytest.mark.task(taskno=1)
+    def test_is_criticality_balanced(self):
+        """Testing border cases around typical points.
+
+        T, n == (800, 500), (625, 800), (500, 1000), etc.
+
+        """
+
+        test_data = ((750, 650, True), (799, 501, True), (500, 600, True),
+                     (1000, 800, False), (800, 500, False), (800, 500.01, False),
+                     (799.99, 500, False), (500.01, 999.99, False), (625, 800, False),
+                     (625.99, 800, False), (625.01, 799.99, False), (799.99, 500.01, True),
+                     (624.99, 799.99, True), (500, 1000, False), (500.01, 1000, False),
+                     (499.99, 1000, True))
+
+        for variant, data in enumerate(test_data, start=1):
+            temp, neutrons_emitted, expected = data
+            with self.subTest(f'variation #{variant}', temp=temp, neutrons_emitted=neutrons_emitted, expected=expected):
+
+                # pylint: disable=assignment-from-no-return
+                actual_result = is_criticality_balanced(temp, neutrons_emitted)
+                failure_message = (f'Called is_criticality_balanced({temp}, {neutrons_emitted}). '
+                                   f' The function returned {actual_result}, '
+                                   f'but the test expected {expected} as the return value.')
+
+                self.assertEqual(actual_result, expected, failure_message)
+
+    @pytest.mark.task(taskno=2)
+    def test_reactor_efficiency(self):
+        voltage = 10
+        theoretical_max_power = 10000
+
+        # The numbers are chosen so that current == 10 x percentage
+        test_data = ((1000, 'green'), (999, 'green'), (800, 'green'),
+                     (799, 'orange'), (700, 'orange'), (600, 'orange'),
+                     (599, 'red'), (560, 'red'), (400, 'red'), (300, 'red'),
+                     (299, 'black'), (200, 'black'), (0, 'black'))
+
+        for variant, data in enumerate(test_data, start=1):
+            current, expected = data
+            with self.subTest(f'variation #{variant}', voltage=voltage, current=current,
+                              theoretical_max_power=theoretical_max_power, expected=expected):
+
+                # pylint: disable=assignment-from-no-return
+                actual_result = reactor_efficiency(voltage, current, theoretical_max_power)
+                failure_message =(f'Called reactor_efficiency({voltage}, {current}, {theoretical_max_power}). '
+                                  f'The function returned {actual_result}, '
+                                  f'but the test expected {expected} as the return value.')
+
+                self.assertEqual(actual_result, expected, failure_message)
+
+    @pytest.mark.task(taskno=3)
+    def test_fail_safe(self):
+        temp = 10
+        threshold = 10000
+        test_data = ((399, 'LOW'), (300, 'LOW'), (1, 'LOW'),
+                     (0, 'LOW'), (901, 'NORMAL'), (1000, 'NORMAL'),
+                     (1099, 'NORMAL'), (899, 'LOW'), (700, 'LOW'),
+                     (400, 'LOW'), (1101, 'DANGER'), (1200, 'DANGER'))
+
+        for variant, (neutrons_per_second, expected) in enumerate(test_data, start=1):
+            with self.subTest(f'variation #{variant}', temp=temp, neutrons_per_second=neutrons_per_second,
+                              threshold=threshold, expected=expected):
+
+                # pylint: disable=assignment-from-no-return
+                actual_result = fail_safe(temp, neutrons_per_second, threshold)
+                failure_message = (f'Called fail_safe({temp}, {neutrons_per_second}, {threshold}). '
+                                   f'The function returned {actual_result}, '
+                                   f'but the test expected {expected} as the return value.')
+
+                self.assertEqual(actual_result, expected, failure_message)