chore(plating): de-dash shipped code + intake-neutral customer emails
Replace em-dashes and en-dashes with hyphens across 789 shipped source files (py/xml/js/scss) so the delivered module reads as human-written; em-dashes had become a recognizable AI-generated tell. Internal .md dev notes are excluded. The WO-sticker mojibake strippers keep their dash search targets (now written — / –). No logic changes: comments and display strings only; validated with py_compile + lxml parse. Rewrite the 7 customer notification emails to be intake-neutral (ship-in / drop-off / pickup) and repair-aware, and fix the Shipped email documents line (packing slip vs bill of lading; certificate only when issued). Subjects use a hyphen separator. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
This commit is contained in:
@@ -4,7 +4,7 @@
|
||||
# Part of the Fusion Plating product family.
|
||||
|
||||
{
|
||||
'name': 'Fusion Plating — Controlled Goods Program',
|
||||
'name': 'Fusion Plating - Controlled Goods Program',
|
||||
'version': '19.0.1.2.3',
|
||||
'category': 'Manufacturing/Plating',
|
||||
'summary': 'Canadian Controlled Goods Program (CGP) compliance for plating '
|
||||
@@ -12,7 +12,7 @@
|
||||
'personnel security assessments, visitor control, controlled goods '
|
||||
'log, security incidents.',
|
||||
'description': """
|
||||
Fusion Plating — Controlled Goods Program (CGP)
|
||||
Fusion Plating - Controlled Goods Program (CGP)
|
||||
===============================================
|
||||
|
||||
Part of the Fusion Plating product family by Nexa Systems Inc.
|
||||
@@ -27,21 +27,21 @@ manager's view.
|
||||
|
||||
Records included
|
||||
----------------
|
||||
* CGP Registration — company registration with PSPC, 5-year renewal cycle
|
||||
* Authorized Individuals — AI appointment, training, PSA linkage
|
||||
* Personnel Security Assessments (PSA) — restricted to CGP Officer+
|
||||
* Visitor Control — PSA-on-file check, escort, approval
|
||||
* Controlled Goods Inventory — what the shop actually handles
|
||||
* Receipts & Shipments — movement log with AI authorization
|
||||
* Security Incidents — breach reporting, PSPC notification (restricted)
|
||||
* Physical Access Log — entry / exit of controlled areas
|
||||
* Security Plan — seeded as a doc.control template
|
||||
* CGP Registration - company registration with PSPC, 5-year renewal cycle
|
||||
* Authorized Individuals - AI appointment, training, PSA linkage
|
||||
* Personnel Security Assessments (PSA) - restricted to CGP Officer+
|
||||
* Visitor Control - PSA-on-file check, escort, approval
|
||||
* Controlled Goods Inventory - what the shop actually handles
|
||||
* Receipts & Shipments - movement log with AI authorization
|
||||
* Security Incidents - breach reporting, PSPC notification (restricted)
|
||||
* Physical Access Log - entry / exit of controlled areas
|
||||
* Security Plan - seeded as a doc.control template
|
||||
|
||||
Security model
|
||||
--------------
|
||||
A new restricted group ``CGP Officer`` is introduced on top of the core
|
||||
Fusion Plating privilege. PSA and Security Incident records are visible
|
||||
ONLY to the CGP Officer and the CGP Designated Official — not to the
|
||||
ONLY to the CGP Officer and the CGP Designated Official - not to the
|
||||
generic manager role, because not every manager should see personnel
|
||||
assessments. Admin must grant the new group manually; no user is
|
||||
assigned by default.
|
||||
|
||||
Reference in New Issue
Block a user