folder rename

fusion_plating/fusion_plating_compliance_tor/README.md

@@ -0,0 +1,62 @@
+# Fusion Plating - Toronto Compliance Pack
+
+City of Toronto regulatory data pack for the `fusion_plating_compliance`
+framework. Loads Toronto Municipal Code Chapter 681 (Sewers By-law)
+discharge limits and related compliance obligations.
+
+## Dependencies
+
+* `fusion_plating_compliance` (framework)
+* `fusion_plating_compliance_on` (Ontario pack)
+
+## What it loads
+
+### Jurisdiction
+* City of Toronto (child of Ontario, level = municipality)
+
+### Regulators
+* Toronto Water - Industrial Waste Section (administers Chapter 681)
+* Toronto Fire Services (hazardous material inventory)
+* Toronto Municipal Licensing & Standards
+
+### Discharge Limits - Table 1 (Sanitary / Combined Sewers)
+Loads all ~50 parameters verified against the official Chapter 681 PDF,
+including pH (range 6.0 to 11.5), temperature (60 C), conventional pollutants
+(BOD, TSS, phosphorus), metals relevant to plating (nickel 2, total chromium 4,
+hexavalent chromium 2, copper 2, zinc 2, lead 1, cadmium 0.7, mercury 0.01,
+etc.), phenolics, VOCs, PCBs, PAHs, phthalates and other organics.
+
+### Discharge Limits - Table 2 (Storm Sewers)
+The 14 most plating-relevant parameters from the storm sewer limit table.
+These are dramatically stricter than sanitary limits.
+
+**Note:** The framework's `limit_value` and `min_value` fields are
+`Float(digits=(16, 4))`, so any value with more than 4 decimal places will
+be rounded on load. The Cadmium storm limit (0.00008 mg/L) is loaded as
+the smallest representable value (0.0001 mg/L) and documented in notes;
+same caveat applies to any other sub-0.0001 values if they exist.
+
+### Compliance Obligation Templates
+Facility-independent templates that can be copied per facility:
+* P2 Plan - First submission (Year 1)
+* P2 Plan - Year 3 Update
+* P2 Plan - Year 6 Full Re-plan
+* Sewer Sample - Quarterly Monitoring
+* IWSA / Surcharge Agreement Renewal
+* Toronto Fire Hazardous Material Inventory
+
+The framework requires `due_date` on compliance events, so the templates
+carry a far-future placeholder date that should be updated when the template
+is copied to a specific facility.
+
+## Install
+
+Local dev:
+
+    docker exec odoo-dev-app odoo -d fusion-dev \
+        -i fusion_plating_compliance_tor --stop-after-init
+
+Upgrade in place:
+
+    docker exec odoo-dev-app odoo -d fusion-dev \
+        -u fusion_plating_compliance_tor --stop-after-init