extant2000/kill-switch
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

README: plainer wording

Browse Source 
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This commit is contained in:
extant2000git
2026-09-28 14:52:13 -04:00
co-authored by Claude Opus 5.5
parent 6062d23480
commit 204df0f2ad
1 changed files with 2 additions and 4 deletions
Download Patch File Download Diff File Expand all files Collapse all files
README.md
+2 -4
View File
@@ -5,8 +5,7 @@ resource class, including the billing that tends to outlive it.
## What it does and why ## What it does and why
Deleting is the easy half. The hard half is proving nothing remains, and the Deleting is straightforward. Proving that nothing remains is harder, and the two failures that matter are both invisible to the delete path itself.
two failures that matter are both invisible to the delete path itself.
### Billing outliving compute ### Billing outliving compute
@@ -21,8 +20,7 @@ so KillSwitch reports it as a separate critical finding and prints it first.
A `DELETE` that returns 200 means the API accepted the request. It does not A `DELETE` that returns 200 means the API accepted the request. It does not
mean the resource is gone. A teardown whose only evidence is its own success mean the resource is gone. A teardown whose only evidence is its own success
response has verified nothing, so an `absent` state backed only by response has verified nothing, so an `absent` state backed only by
`delete-response` is reported as not assessed. That is the difference `delete-response` is reported as not assessed.
between terminated and verifiably terminated.
KillSwitch never deletes anything. It takes an inventory you enumerated and KillSwitch never deletes anything. It takes an inventory you enumerated and
decides whether the removal can be evidenced. There is no network access and decides whether the removal can be evidenced. There is no network access and