diff --git a/docs/ads/aiads_interface/asb.md b/docs/ads/aiads_interface/asb.md
new file mode 100644
index 0000000..e66e2de
--- /dev/null
+++ b/docs/ads/aiads_interface/asb.md
@@ -0,0 +1,11 @@
+# Autonomous System Break
+
+The ASB serves to allow the autonomous system to slow itself down, however the supervisor for this system is very mission critical and such it also has the option to trigger the ShutDown Circuit and in turn the Emergency System Break. The supervisor should monitor the other electronic systems to ensure they do not stall (if they do: SDC), and is itself monitored by a hardware watchdog that requires a heartbeat or else it will trigger the SDC.
+
+## What signals does it monitor and what does it care about them
+
+It monitors the CANbus to ensure that no system has stalled. Every system should update the values associated with it every X amount of time. If they fail to do so, the supervisor should trigger the SDC. 100ms is a reasonable time for this if CANbus is at 50Hz (FSG Rules define 500ms as the longest digital signal timeout permissable).
+
+- Pi/Jetson sends heartbeat through the PCAN link
+- ESPs sensor data changing should constitute a heartbeat
+- Test to ensure it is able to detect a broken wire, a short to ground, an analogue sensor short to supply, an implausible or out-of-range sensor value, and corrupt, missing or delayed digital messages.
\ No newline at end of file
diff --git a/docs/ads/aiads_interface/overview.md b/docs/ads/aiads_interface/overview.md
index eb04998..66a33d5 100644
--- a/docs/ads/aiads_interface/overview.md
+++ b/docs/ads/aiads_interface/overview.md
@@ -1 +1,74 @@
-in development
\ No newline at end of file
+# Systems Overview
+
+This page details how the AI/ADS interface works. **Currently the system has not been built yet so the details on this page are subject to change, however we are attempting to build to this vision so they should not vary wildly. This notice will be removed once the system is built and relatively stable.**
+
+## What is the AI/ADS interface anyways?
+
+Interface is the layer that stands between the control team on software and the integration team on hardware. This means that we will be getting in details as to what acceleration and steering angle to reach from Control's ROS node, using that to dictate how the various actuators and motors around the car operate, reading data back from a number of sensors we have, and adjusting based off of that. We also have to monitor the systems we create to ensure they do not fail, and if they do we engage the Shut Down Circuit (SDC) to shut the car down and engage the Emergency Braking System (EBS).
+
+## How do we achieve this
+
+```mermaid
+graph LR
+    subgraph Ethernet
+        JT["Autonomous Software Stack Jetson"]
+        PI["Raspberry Pi/Jetson"]
+        NT["Nanotec N5"]
+        JT <--> PI
+        PI <--> NT
+    end
+    ZX["ZedX"]
+    XS["XSens"]
+    SM["Steering Motor"]
+    ZX --> JT
+    XS --> JT
+    NT --> SM
+    PI <-- USB --> PK
+    subgraph CAN bus
+        PK["PEAK PCAN-LINK"]
+        TE["Throttle ESP"]
+        SE["Steering ESP"]
+        CE["Clutch ESP"]
+        GE["Gear ESP"]
+        HE["HMI ESP"]
+        AHE["Auxillary Health ESP"]
+        DS["DEWEsoft Logger"]
+        ME["Microsquirt ECU"]
+        subgraph ASB Supervisor
+            AS["ASB Supervisor ESP"]
+            HW["Hardware Watchdog"]
+            AS -- Heartbeat --> HW
+        end
+        TE .-> AS
+        SE .-> AS
+        CE .-> AS
+        GE .-> AS
+        HE .-> AS
+        ME .-> AS
+        PK <--> TE
+        PK <--> SE
+        PK <--> CE
+        PK <--> GE
+        PK <--> HE
+        PK <--> AHE
+        PK <--> AS
+        ME --> PK
+    end
+    SDC["SDC Latch"]
+    AS --> SDC
+    HW --> SDC
+```
+
+### ASB Supervisor
+  - Monitors Autonomous System Brake (ASB) and ESB, if checks fail, engages SDC.
+  - Monitors other ESPs and if they stall or behave irregularly, engages SDC.
+  - Watchdog needs to be on the same PCB. Watchdog recieves a heartbeat from the ASB Supervisor, if does not it engages the SDC.
+
+### Low Level Logic
+  - Each of the ESPs listed in the diagram needs to be programmed to deal with targets for its relevant domain and be able to adjust itself to achieve those (PID?)
+  - Each of the ESPs needs to be able to communicate over CAN bus a unified. This uses a 20AWG twisted pair as the wire, an Adafruit CAN Pal on each ESP32, the inbuilt TWAI controller driver using a prexisting [library](https://github.com/collin80/esp32_can). The twisted pair needs to be terminated with 120 omhs.
+
+### Raspberry Pi/Jetson
+  - Is a ROS node that forwards on the instructions gotten from control's node via CAN using the PCAN LINK.
+  - Returns details such as actual wheel angle, speed, etc, up the chain by publishing it.
+  - Using [ros2nix](https://github.com/wentasah/ros2nix) would be nice to minimise issues relating to setting up multiple redundant devices and migrating from one to another. This will also help to deal with compatability issues of ROS with different versions of Linux and reduce unessicary time spent compiling from source.
\ No newline at end of file
diff --git a/mkdocs.yml b/mkdocs.yml
index 54fa858..3a4a093 100644
--- a/mkdocs.yml
+++ b/mkdocs.yml
@@ -134,6 +134,7 @@ nav: # This is the structure of the sidebar
       - AI/ADS Interface:
             - Overview: ads/aiads_interface/overview.md
             - Raspberry Pi Setup: ads/aiads_interface/raspberrypi.md
+            - Autonomous System Break: ads/aiads_interface/asb.md
       - Actuation Control:
             - Overview: ads/actuation_control/overview.md
   - Resources: