# DONE — 2026-05-15_REVIEW_PTF-317_MAIL_TEMPLATE_QWEB_RULE
# SGPT via verity-dispatcher auto-relay | AT 2026-05-15T22:35:41.947Z
# Tokens: prompt=1013 completion=650
# TRUTH MATTERS® · Verity One Ltd. | OTC: USDW
Agent: SGPT
Task: PTF-317 risk review
State: complete

Finding:
1. **Grace Period for Legacy Templates:** There is a legitimate concern regarding immediate P0 classification for active automations using legacy formatting. It is advisable to provide a defined grace period to allow stakeholders to transition templates without incurring P0 incidents immediately after detection.
   
2. **Scope Creep Risk:** The current PTF scope explicitly covers only `body_html`. Given the rendering concerns mentioned, an analysis confirming that other fields (`report_template_xml_id`, `email_to`, `email_cc`) utilize different rendering engines is necessary. If not confirmed, these should be considered for inclusion in the PTF scope.

3. **Migration WO Not Yet Filed:** PTF-317 does not include authorization for legacy template rewrites. It is crucial to confirm that a companion WO is filed to address these migrations. Furthermore, each WO should receive its separate SGPT GO verdict to ensure comprehensive review and approval.

4. **Hyperledger Gate Interaction:** As PTF-316 §8 is in effect and blocking certain receipt processes, PTF-317 should explicitly state if §8 carve-outs or exceptions will be made for mail template mutations. Without this reference, it might face hindrances, especially in anchored operations.

5. **Stock-first PTF-315 Alignment:** PTF-317's reinforcement of PTF-315 is a strategic move. However, adding language that prioritizes rewriting over deactivation and replacement with stock options once they prove viable, would provide clearer directives aligning better with operational intent.

Proof:
- Reviewed PTF-317 documentation located at `/opt/veritize-docker/ops/wo/ptf/PTF-317.md`.
- Confirmed issue evidence in `/opt/veritize-docker/ops/queue/approval/2026-05-15_SC_INVESTIGATION_MAIL_TEMPLATE_R1.md`.
- Checked the hash in `/opt/veritize-docker/ops/queue/sc/EVIDENCE/2026-05-15_MAIL_TEMPLATE_FIX/manifest.sha256` to validate pre-state integrity.

Blocker:
- Potential escalation risk without a defined grace period for legacy templates.
- Incomplete scope assessment that may overlook similar rendering risks in other template fields.
- Absence of a migration WO and lack of explicit carve-outs regarding Hyperledger interactions could obstruct rule execution.

Verdict: GO-WITH-CORRECTION
- Proceeding is viable; however, it requires addressing noted issues such as defining grace periods, confirming scope completeness, ensuring migration WO filing and approval, and clarifying interaction with existing Hyperledger gate restrictions.

Next Move:
- Develop and implement a grace period policy for legacy templates.
- Investigate and confirm the rendering engine mechanisms for remaining template fields.
- Coordinate filing and approval of a migration WO for legacy template transformation.
- Amend PTF-317 to reference §8 interactions or needed carve-outs.

Needs From:
- Confirmation from relevant technical teams regarding engine differences for template fields.
- Legal/Compliance input on grace periods and §8 interactions.
- Management authorization to file and operationalize a migration WO.
  
TRUTH MATTERS® · Made in USA Inc. (OTC: USDW)