closedloop-technologies Protected Surface Editing
Use this skill before touching paths that are denied or approval-required by ClimbHill policy.
Inputs
- Active policy
- Proposed edit paths
- Reason for edit
- Human approval status
Procedure
- Read
.climbhill/policy.yamlor the active policy snapshot. - Classify every proposed path as allowed, denied, or approval-required.
- If any path is denied, stop and propose an alternative.
- If any path requires approval, ask for human approval before editing.
- For approved protected edits, keep changes minimal and document why they are necessary.
- Record the policy check result in the attempt report.
Outputs
- Path classification
- Approval request when needed
- Policy check result
- Risk notes
Rubric
- Denied paths are not edited.
- Approval-required paths are not edited before approval.
- Protected edits are narrow and justified.
- Reports identify the protected surface and reason.