RomanNum3ral
/
paperclip
mirror of https://github.com/paperclipai/paperclip.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

docs(runner): explain remote signal failure handling 

Co-Authored-By: Paperclip <noreply@paperclip.ing>
This commit is contained in:
Dotta 2026-09-12 22:37:59 -05:00
parent cb938e4006
commit 5fda8df551
1 changed files with 5 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

5
doc/execution-semantics.md
View File

@ -1222,3 +1222,8 @@ Local and remote runners use the same attachment publication contract. Remote
files are read through the bound environment runner, with workspace confinement,
no symlinks or hardlinks, stable file identity, a 10 MiB bound, and exact size and
SHA-256 checks before storage. Remote paths are never opened on the controller.
An asynchronous remote signal failure, including a sandbox already removed by
the operator, must not crash the controller. Logging that failure must also be
contained. A rejected signal does not prove termination: existing process and
provider monitoring still own stop acknowledgement and cleanup proof.