cto/.sot/03-PROTOCOLS/CTO-GOVERNED-EXECUTION-REQUEST-ISSUES.md
2026-06-01 07:51:09 -04:00

50 lines
1.5 KiB
Markdown

---
name: CTO Governed Execution Request Issues
status: validated
lifecycle_classification: sot
owner: jp
created: 2026-06-01
last_reviewed: 2026-06-01
core_promotion_status: not-promoted
---
# CTO Governed Execution Request Issues
Local planning SOT only. Not a Core Protocol. Not active Core authority.
## Issue: CTO-WORK-066 - Governed Execution Request PRD
Status: validated.
Acceptance:
- Define the governed execution request scope.
- Require a non-mutating execution request record.
- Preserve the exact approval packet, admitted target repository, allowed paths, and Harness command.
- Record `approval_granted: false`.
- Record `execution_allowed: false`.
- State: Do not execute Case.
- State: Do not activate Case as default backend.
- State: Do not mutate target repositories.
- State: Runtime default activation remains false.
- State: JP approval is still required before execution.
## Issue: CTO-WORK-067 - Governed Execution Request Record
Status: validated.
Acceptance:
- Create the governed execution request record.
- Include the admitted target repository.
- Include allowed paths.
- Include the Harness command.
- Include proof pointers from prior Harness and Hermes evidence.
- Keep `approval_granted: false`.
- Keep `execution_allowed: false`.
- State: Do not execute Case.
- State: Do not activate Case as default backend.
- State: Do not mutate target repositories.
- State: Runtime default activation remains false.
- State: JP approval is still required before execution.