hermes/cto

Svrnty 405ea616a5 Plan Hermes approval state

2026-06-01 07:40:37 -04:00

1.6 KiB

Raw Blame History

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

CTO Hermes Approval State Issues

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

CTO-WORK-062: Hermes WebUI JP Approval State PRD

Status: validated.

Acceptance criteria:

PRD defines JP approval state scope.
PRD keeps the surface read-only.
PRD forbids executable approval buttons.
PRD keeps Harness-backed summary data as source of truth.
PRD states Hermes visualizes control state; CTO and Harness remain the gates.

CTO-WORK-063: Hermes WebUI JP Approval State Surface

Status: candidate.

Implementation route:

Add read-only approval posture to /api/cto/control-summary.
Add approval_required, approval_granted, and execution_allowed.
Add allowed next actions.
Add blocked next actions.
Render JP approval state in cto_control_panel.js.
Add focused plugin tests.
Record evidence after implementation.

Acceptance criteria:

CTO control summary includes JP approval state.
CTO control summary includes allowed next actions.
CTO control summary includes blocked next actions.
approval_required defaults to true.
approval_granted defaults to false.
execution_allowed defaults to false.
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 visualizes control state; CTO and Harness remain the gates.