folder rename

fusion_plating/fusion_plating_bridge_sign/README.md

@@ -0,0 +1,44 @@
+# Fusion Plating — E-Sign Bridge (EE)
+
+**Enterprise-only bridge module.** Wires `fusion_plating_quality` into Odoo EE `sign`
+so customer CoC (Certificate of Conformance) acceptance can be captured as a
+legally-binding e-signature.
+
+Copyright © 2026 Nexa Systems Inc.
+License: OPL-1
+
+## Behaviour
+
+| Trigger | Result |
+|---|---|
+| Install both `fusion_plating_quality` and EE `sign` | This bridge auto-installs |
+| Install only the CE stack | This module is never discovered — `depends: sign` hides it |
+| FAIR reaches state `approved` | "Send for Customer Signature" button appears in the header |
+| Customer completes signature in Sign | `sign.request.state` flips; bridge preserves back-reference |
+
+## What it adds
+
+On `fusion.plating.fair`:
+
+- `x_fc_sign_request_id` — M2o `sign.request` (the generated signing envelope)
+- `x_fc_sign_request_state` — related display of signing progress
+- `x_fc_signed_date`, `x_fc_signed_by`, `x_fc_signed_pdf_id` — final artefact
+- Header buttons: Send for Customer Signature / View Sign Request / Download Signed PDF
+- E-Signature notebook page on the FAIR form
+
+## What it does NOT do
+
+- Sync Sign status back into the FAIR automatically on every change. The EE sign
+  module fires its own activities; this bridge only stores the back-reference and
+  lets users navigate. A customer-delivered callback wiring `sign.request` state
+  changes back onto FAIR is a future enhancement.
+- Work on Community Edition. By design.
+
+## Install
+
+When you add EE `sign` to a site that already runs `fusion_plating_quality`, the
+bridge appears with `auto_install=True` and loads on the next update:
+
+```bash
+docker exec odoo-dev-app odoo -d fusion-dev -u base --stop-after-init
+```