|
| 1 | +# Public-Safe Dry-Run Workflow |
| 2 | + |
| 3 | +This document defines a public-safe dry-run workflow contract for HAN Agent OS. |
| 4 | + |
| 5 | +It is intentionally narrow. |
| 6 | + |
| 7 | +It does not perform live execution. |
| 8 | + |
| 9 | +It does not mutate files. |
| 10 | + |
| 11 | +It does not run arbitrary shell commands. |
| 12 | + |
| 13 | +It does not launch browser automation. |
| 14 | + |
| 15 | +It does not require secrets. |
| 16 | + |
| 17 | +It does not call live OpenClaw. |
| 18 | + |
| 19 | +It only defines the safe shape of a future dry-run request, response, and receipt. |
| 20 | + |
| 21 | +--- |
| 22 | + |
| 23 | +## Purpose |
| 24 | + |
| 25 | +The goal is to show how HAN Agent OS should handle a proposed action before any real execution happens. |
| 26 | + |
| 27 | +A dry-run is not a live action. |
| 28 | + |
| 29 | +A dry-run should answer: |
| 30 | + |
| 31 | + What would be done if this were approved later? |
| 32 | + |
| 33 | +It should not actually do the action. |
| 34 | + |
| 35 | +--- |
| 36 | + |
| 37 | +## Difference between status-read and dry-run |
| 38 | + |
| 39 | +| Workflow | Purpose | Performs action | |
| 40 | +|---|---|---| |
| 41 | +| status-read | Read current public-safe status | No | |
| 42 | +| dry-run | Simulate or describe a proposed action | No | |
| 43 | +| live execution | Actually perform the approved action | Yes, but not in this public workflow | |
| 44 | + |
| 45 | +This document covers dry-run only. |
| 46 | + |
| 47 | +--- |
| 48 | + |
| 49 | +## Roles |
| 50 | + |
| 51 | +| Role | System | Responsibility | |
| 52 | +|---|---|---| |
| 53 | +| Human Operator | Human | Requests a dry-run preview | |
| 54 | +| Brain | Hermes | Understands intent and classifies the request | |
| 55 | +| Control bus | HAN Agent OS | Enforces dry-run boundary | |
| 56 | +| Hands | OpenClaw | Not called live in this public workflow | |
| 57 | +| Code specialist | Codex | Not required unless the dry-run concerns code changes | |
| 58 | +| Receipt layer | HAN Agent OS | Records the simulated plan and confirms no live action occurred | |
| 59 | + |
| 60 | +--- |
| 61 | + |
| 62 | +## Example request |
| 63 | + |
| 64 | +Human: |
| 65 | + |
| 66 | + Dry-run what would happen if OpenClaw checked local agent status. |
| 67 | + |
| 68 | +Hermes should classify this as: |
| 69 | + |
| 70 | + task_class: dry_run |
| 71 | + mutation_allowed: false |
| 72 | + live_task_execution_allowed: false |
| 73 | + file_write_allowed: false |
| 74 | + shell_execution_allowed: false |
| 75 | + browser_automation_allowed: false |
| 76 | + credential_access_allowed: false |
| 77 | + repeated_execution_allowed: false |
| 78 | + chained_execution_allowed: false |
| 79 | + |
| 80 | +The important distinction: |
| 81 | + |
| 82 | + Dry-run planning is allowed. |
| 83 | + Live execution is not allowed. |
| 84 | + |
| 85 | +--- |
| 86 | + |
| 87 | +## Allowed dry-run behavior |
| 88 | + |
| 89 | +A public-safe dry-run may: |
| 90 | + |
| 91 | +- describe the intended action |
| 92 | +- validate whether the request is narrow enough |
| 93 | +- identify the target system |
| 94 | +- identify whether human approval would be needed |
| 95 | +- produce a simulated command mapping |
| 96 | +- produce a simulated receipt shape |
| 97 | +- recommend stop, revise, or request approval |
| 98 | + |
| 99 | +It must stay descriptive. |
| 100 | + |
| 101 | +It must not execute the action. |
| 102 | + |
| 103 | +--- |
| 104 | + |
| 105 | +## Forbidden dry-run behavior |
| 106 | + |
| 107 | +A public-safe dry-run must not: |
| 108 | + |
| 109 | +- execute tasks |
| 110 | +- mutate files |
| 111 | +- run arbitrary shell commands |
| 112 | +- launch browser automation |
| 113 | +- persist credentials |
| 114 | +- persist browser sessions |
| 115 | +- persist API keys |
| 116 | +- call live OpenClaw |
| 117 | +- call live Codex execution |
| 118 | +- expose raw private configuration |
| 119 | +- expose raw stdout or stderr logs |
| 120 | +- expose private runtime receipts |
| 121 | +- repeat automatically |
| 122 | +- chain into a live action |
| 123 | + |
| 124 | +If a dry-run request needs any forbidden behavior, it must be blocked and escalated for human review. |
| 125 | + |
| 126 | +--- |
| 127 | + |
| 128 | +## Expected routing |
| 129 | + |
| 130 | +The routing should be: |
| 131 | + |
| 132 | + Human Operator |
| 133 | + -> Hermes classifies the request as dry_run |
| 134 | + -> HAN Agent OS checks the dry-run boundary |
| 135 | + -> HAN Agent OS produces a simulated action plan |
| 136 | + -> No live OpenClaw call is made |
| 137 | + -> No Codex execution is made unless explicitly scoped as code planning |
| 138 | + -> HAN Agent OS records a dry-run receipt |
| 139 | + -> Human decides whether to stop, revise, or approve a later action |
| 140 | + |
| 141 | +Dry-run does not automatically authorize live execution. |
| 142 | + |
| 143 | +--- |
| 144 | + |
| 145 | +## Minimal dry-run receipt |
| 146 | + |
| 147 | +A dry-run receipt should include: |
| 148 | + |
| 149 | + operation_type: dry_run |
| 150 | + target: openclaw |
| 151 | + requested_action: status_check_preview |
| 152 | + mutation_performed: false |
| 153 | + live_task_executed: false |
| 154 | + file_write_performed: false |
| 155 | + shell_execution_performed: false |
| 156 | + browser_automation_performed: false |
| 157 | + credential_access_performed: false |
| 158 | + openclaw_live_call_performed: false |
| 159 | + codex_execution_performed: false |
| 160 | + repeated_execution_performed: false |
| 161 | + chained_execution_performed: false |
| 162 | + simulated_plan_available: true |
| 163 | + next_step: human approval required before any live action |
| 164 | + |
| 165 | +This receipt proves both the simulated plan and the fact that no live action occurred. |
| 166 | + |
| 167 | +--- |
| 168 | + |
| 169 | +## Human-facing response shape |
| 170 | + |
| 171 | +A good response should look like this: |
| 172 | + |
| 173 | + Dry-run completed. |
| 174 | + Proposed target: OpenClaw. |
| 175 | + Proposed action: status check preview. |
| 176 | + No task execution was performed. |
| 177 | + No files were changed. |
| 178 | + No shell command was run. |
| 179 | + No browser automation was used. |
| 180 | + No credentials were accessed. |
| 181 | + No live OpenClaw call was made. |
| 182 | + Next step: stop, revise the plan, or request explicit approval. |
| 183 | + |
| 184 | +The response should not imply that OpenClaw was actually called. |
| 185 | + |
| 186 | +The response should not imply that a live result was obtained. |
| 187 | + |
| 188 | +--- |
| 189 | + |
| 190 | +## Why this belongs in v0.2.2 |
| 191 | + |
| 192 | +The v0.2.0 line introduced a public-safe status-read workflow contract. |
| 193 | + |
| 194 | +The v0.2.1 line added a public-safe status-read mock implementation example. |
| 195 | + |
| 196 | +The next safe step is dry-run contract definition. |
| 197 | + |
| 198 | +This creates a controlled bridge between read-only status and future execution planning without jumping into live automation. |
| 199 | + |
| 200 | +--- |
| 201 | + |
| 202 | +## Final boundary |
| 203 | + |
| 204 | +This workflow is a contract only. |
| 205 | + |
| 206 | +It does not authorize live OpenClaw execution. |
| 207 | + |
| 208 | +It does not authorize Codex code changes. |
| 209 | + |
| 210 | +It does not authorize shell access. |
| 211 | + |
| 212 | +It does not authorize browser automation. |
| 213 | + |
| 214 | +It only defines a safe dry-run workflow shape. |
0 commit comments