61 lines
2.0 KiB
Markdown
61 lines
2.0 KiB
Markdown
---
|
|
name: CTO Hermes Approval State PRD
|
|
status: validated
|
|
lifecycle_classification: sot
|
|
owner: jp
|
|
created: 2026-06-01
|
|
last_reviewed: 2026-06-01
|
|
core_promotion_status: not-promoted
|
|
---
|
|
|
|
# CTO Hermes Approval State PRD
|
|
|
|
Local planning SOT only. Not a Core Protocol. Not active Core authority.
|
|
|
|
## Problem
|
|
|
|
The CTO panel shows Harness proof state, but it does not yet expose JP approval state or allowed next actions. That leaves Hermes as evidence display only. The endgoal requires Hermes to provide visualization, approval, control, and replay while CTO and Harness keep execution gated.
|
|
|
|
## Scope
|
|
|
|
Add read-only approval posture to the CTO control summary and panel:
|
|
|
|
- `approval_required`
|
|
- `approval_granted`
|
|
- `execution_allowed`
|
|
- approval reason
|
|
- allowed next actions
|
|
- blocked next actions
|
|
|
|
This slice must show what can happen next, not perform the action.
|
|
|
|
## Non-goals
|
|
|
|
- Do not add executable approval buttons.
|
|
- Do not activate Case as default backend.
|
|
- Do not mutate target repositories.
|
|
- Do not edit upstream `hermes-webui`.
|
|
- Do not edit upstream `hermes-agent`.
|
|
- Do not change Cortex Core authority.
|
|
|
|
## Acceptance Criteria
|
|
|
|
- CTO control summary includes read-only approval posture.
|
|
- CTO control summary includes allowed next actions and blocked next actions.
|
|
- Approval state defaults to `approval_required: true`, `approval_granted: false`, and `execution_allowed: false`.
|
|
- Hermes panel renders JP approval state.
|
|
- Hermes panel renders allowed next actions.
|
|
- Harness-backed summary data remains the source of truth.
|
|
- Hermes visualizes control state; CTO and Harness remain the gates.
|
|
|
|
## Validation
|
|
|
|
- Focused plugin tests prove approval posture is present, safe, and rendered by static JS.
|
|
- Plugin aggregate tests pass before commit and after merge.
|
|
- CTO child validator records the planning and evidence state.
|
|
- S69 prose validator passes before final report.
|
|
|
|
## Success Definition
|
|
|
|
Hermes can show JP approval state and allowed next actions for the CTO flow without becoming an authority layer or allowing execution from the WebUI.
|