Record Hermes approval state evidence
This commit is contained in:
@@ -0,0 +1,56 @@
|
||||
---
|
||||
name: CTO Hermes Approval State Evidence
|
||||
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 Evidence
|
||||
|
||||
Local planning SOT only. Not a Core Protocol. Not active Core authority.
|
||||
|
||||
## Scope
|
||||
|
||||
This evidence closes `CTO-WORK-063`.
|
||||
|
||||
The implementation adds read-only JP approval state and next-action visibility to the Hermes WebUI CTO control panel. It does not add executable approval buttons, mutate target repositories, activate Case as default backend, or change Cortex authority.
|
||||
|
||||
## Implementation Evidence
|
||||
|
||||
- Hermes plugin commit: `154d835 Add CTO approval state surface`
|
||||
- API field: `approval_required`
|
||||
- API field: `approval_granted`
|
||||
- API field: `execution_allowed`
|
||||
- API field: allowed next actions
|
||||
- API field: blocked next actions
|
||||
- UI surface: `static/cto_control_panel.js`
|
||||
- Route surface: `routes/cto_control_summary.py`
|
||||
|
||||
## Validation Evidence
|
||||
|
||||
- Focused validation: `python3 -m pytest tests/unit/test_cto_control_summary.py tests/unit/test_cto_control_panel_static.py -q`
|
||||
- Focused result: `5 passed`
|
||||
- Aggregate validation before commit: `python3 scripts/ast-connection-map.py --check`
|
||||
- Aggregate result before commit: `CONNECTION-MAP.md is fresh`
|
||||
- Aggregate validation before commit: `python3 -m pytest tests/ -q`
|
||||
- Aggregate result before commit: `103 passed, 4 skipped`
|
||||
- Aggregate validation after merge: `python3 scripts/ast-connection-map.py --check`
|
||||
- Aggregate result after merge: `CONNECTION-MAP.md is fresh`
|
||||
- Aggregate validation after merge: `python3 -m pytest tests/ -q`
|
||||
- Aggregate result after merge: `107 passed`
|
||||
|
||||
## Governance Evidence
|
||||
|
||||
- Harness-backed summary data remains the source of truth.
|
||||
- Case runtime default active: false
|
||||
- target repository mutation: false
|
||||
- upstream `hermes-webui` edited: false
|
||||
- upstream `hermes-agent` edited: false
|
||||
- Hermes visualizes control state; CTO and Harness remain the gates.
|
||||
|
||||
## Result
|
||||
|
||||
`CTO-WORK-063` is validated because Hermes now exposes JP approval posture and next-action visibility without gaining execution authority.
|
||||
Reference in New Issue
Block a user