chore: update compliance docs

Author: shon-button

docs/compliance/automated_process_compliance_handlers.md

@@ -46,10 +46,12 @@ This `can_handle()` function will return true if the ComplianceObligation's invo
 This `handle()` function does the following:
 
 1. Check if the ComplianceObligation's invoice has FAA interest owing
+
    - if it does, it sets the ComplianceReportVersion's status to `Obligation Met, Interest Not Paid`
    - otherwise, it sets the status to `Obligation Met`
 
 2. Determines whether the ComplianceObligation should be charged GGEAPAR Interest (Was the obligation the result of a supplementary report submitted beyond the compliance deadline)
+
    - if it does, it will call the PenaltyCalculationService with the appropriate parameters to create a GGEAPAR Interest penalty & invoice in eLicensing
 
 3. Determines whether the ComplianceObligation should be charged an Automatic Overdue Penalty (Original obligation paid past the deadline, or supplementary obligation paid after custom due date)
@@ -64,3 +66,13 @@ This `can_handle()` function will return true if the ComplianceObligation's invo
 #### What does it do
 
 This `handle()` function will flip the status of the ComplianceReportVersion from `Obligation Met, Interest Not Paid` to `Obligation Met`.
+
+![4 AM Compliance Cycle](./images/bciers-compliance-cycle.png)
+
+#### Image Generation details
+
+- **Tool:** ChatGPT (OpenAI), including AI image generation
+- **Input:** Technical information contained in this document
+
+> [!NOTE]
+> AI-generated diagrams are for explanatory purposes only. If a diagram conflicts with the application code, technical documentation, or applicable regulations, those sources take precedence.

docs/compliance/images/bciers-compliance-cycle.png

@@ -5,8 +5,8 @@ This document describes penalties as defined in the [Greenhouse Gas Emission Adm
 ## Accruing vs Existing
 
 Penalties begin _ACCRUING_ as soon as an obligation owes a balance beyond the due date.
-However, a penalty data object in the BCIERS system and a related invoice in eLicensing will not be created until the obligation triggering the penalty has been paid in full (elicensinginvoice.fee_amount_balance == $0.00).
-As far as BCIERS is concerned, A penalty does not _EXIST_ while it is _ACCRUING_. It only becomes data in the system and has an invoice once the triggering obligation is paid in full.
+However, a penalty data object in the BCIERS system and a related invoice in eLicensing will not be created until the obligation triggering the penalty has been paid in full (elicensinginvoice.fee*amount_balance == $0.00).
+As far as BCIERS is concerned, A penalty does not \_EXIST* while it is _ACCRUING_. It only becomes data in the system and has an invoice once the triggering obligation is paid in full.
 
 ## Types of Penalties
 
@@ -101,3 +101,13 @@ The penalty will be calculated with a base of:
 $800,000.00 from Dec 1 - Dec 20
 $300,000.00 from Dec 21 - Jan 25
 ```
+
+![Understanding Compliance Penalties](./images/bciers-penalties-overview.png)
+
+#### Image Generation details
+
+- **Tool:** ChatGPT (OpenAI), including AI image generation
+- **Input:** Technical information contained in this document
+
+> [!NOTE]
+> AI-generated diagrams are for explanatory purposes only. If a diagram conflicts with the application code, technical documentation, or applicable regulations, those sources take precedence.

docs/compliance/images/bciers-penalties-overview.png

@@ -190,3 +190,13 @@ This `can_handle()` function will return true if the credited_emission values an
 #### What does it do
 
 This `handle()` function will create a compliance report version with the No Obligation or Earned Credits status. No related obligation or earned credit record will be created in this case.
+
+![Supplementary Report Engine](./images/bciers-supplementary-report-engine.png)
+
+#### Image Generation details
+
+- **Tool:** ChatGPT (OpenAI), including AI image generation
+- **Input:** Technical information contained in this document
+
+> [!NOTE]
+> AI-generated diagrams are for explanatory purposes only. If a diagram conflicts with the application code, technical documentation, or applicable regulations, those sources take precedence.