Whitepaper · Sandbox and approval
Inside Sudo: a sandbox, a diff, a person
Sudo, the admin assistant in Curiosity Studio, changes your configuration in a sandbox and hands you a diff. This paper shows what the sandbox holds, what it lacks, and what an approval binds.
What it covers
No route to the host. No route in but a diff.
Sudo has no route to the host or the network, and no route to your workspace except a diff an administrator approved. A commit stages a change and stops. A person applies it, under their own permissions, into the history you already audit.
- Step 01
Read
Workspace and reference
- Step 02
Edit
In Sudo’s own copy
- Step 03
Build
Compiles every change
- Step 04
Commit
Stages it, then stops
Chapters
Six chapters, from files to the audit trail
01 · Page 03All four
Configuration is already files
One filesystem and one tool reach every surface.
02 · Page 05Read · Edit
Nine mounts, two writable
Only a write under /workspace is a change.
03 · Page 07Read · Edit
An interpreter, not a shell
No host, no processes, no network, by construction.
04 · Page 11Build · Commit
Commit stages, a person applies
Approval is bound to the commit you were shown.
05 · Page 15Read
Permissions bound Sudo from below
Sudo reads as you and writes none of your data.
06 · Page 17Commit
Accountability and reuse
Every change audited, and the same sandbox for your assistant.
Your data. Your infrastructure.