---
name: CTO Hermes Approval Packet Issues
status: candidate
lifecycle_classification: sot
owner: jp
created: 2026-06-01
last_reviewed: 2026-06-01
core_promotion_status: not-promoted
---

# CTO Hermes Approval Packet Issues

Local planning SOT only. Not a Core Protocol. Not active Core authority.

## CTO-WORK-064: Hermes WebUI JP Approval Packet PRD

Status: validated.

Acceptance criteria:

- PRD defines the JP approval packet scope.
- PRD keeps packet generation read-only.
- PRD includes `approval_packet`.
- PRD includes `approval_command_text`.
- PRD forbids executable approval buttons.
- PRD states Hermes prepares approval text; JP remains the approver.

## CTO-WORK-065: Hermes WebUI JP Approval Packet Surface

Status: candidate.

Implementation route:

- Add `approval_packet` to `/api/cto/control-summary`.
- Add `approval_command_text`.
- Add copy/paste approval packet text for JP.
- Include required evidence paths.
- Include allowed paths.
- Include blocked actions.
- Render copy/paste packet text in `cto_control_panel.js`.
- Add focused plugin tests.
- Record evidence after implementation.

Acceptance criteria:

- CTO control summary includes `approval_packet`.
- CTO control summary includes `approval_command_text`.
- CTO control summary includes required evidence paths.
- CTO control summary includes allowed paths.
- CTO control summary includes blocked actions.
- Do not add executable approval buttons.
- Do not activate Case as default backend.
- Do not mutate target repositories.
- Harness-backed summary data remains the source of truth.
- Hermes prepares approval text; JP remains the approver.