cto/.sot/03-PROTOCOLS/CTO-HERMES-WEBUI-CONTROL-PANEL-EVIDENCE.md

55 lines
2.0 KiB
Markdown

---
name: CTO Hermes WebUI Control Panel Evidence
status: validated
lifecycle_classification: sot
owner: jp
created: 2026-06-01
last_reviewed: 2026-06-01
core_promotion_status: not-promoted
---
# CTO Hermes WebUI Control Panel Evidence
Local planning SOT only. Not a Core Protocol. Not active Core authority.
## Scope
This evidence closes `CTO-WORK-059`.
The implementation adds a Hermes-owned WebUI consumer panel for CTO Harness proof state. It does not change Cortex Core authority, Case authority, target repository ownership, upstream `hermes-webui`, or upstream `hermes-agent`.
## Implementation Evidence
- Hermes plugin commit: `9c8f345 Add CTO harness control panel`
- Route: `/api/cto/control-summary`
- Route file: `routes/cto_control_summary.py`
- Frontend asset: `cto_control_panel.js`
- Style asset: `cto_control_panel.css`
- Connection map: `CONNECTION-MAP.md is fresh`
## Validation Evidence
- Focused validation before commit: `python3 -m pytest tests/unit/test_cto_control_summary.py tests/evals/test_features.py -q`
- Focused result: `8 passed, 1 skipped`
- Aggregate validation before commit: `python3 scripts/ast-connection-map.py --check`
- Aggregate validation before commit: `python3 -m pytest tests/ -q`
- Aggregate result before commit: `100 passed, 4 skipped`
- Aggregate validation after merge: `python3 scripts/ast-connection-map.py --check`
- Aggregate validation after merge: `python3 -m pytest tests/ -q`
- Aggregate result after merge: `104 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
- Case remains a candidate backend behind the CTO Harness seam.
- Hermes provides visualization and control only.
- Cortex remains SOT authority.
## Result
`CTO-WORK-059` is validated because Hermes now exposes a read-only CTO control panel over Harness evidence without activating Case, mutating target repositories, or editing upstream vendor source.