coulomb/glas-harness
4
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

docs: record production namespace boundary proof
All checks were successful
ci / validate (push) Successful in 1m12s
Details

Browse source 
Assistant: codex
Assistant-Model: gpt-5.6-sol
Assistant-Session: 01a0233b-178d-7162-b92f-31a31ea8ca9b
This commit is contained in:
tegwick 2026-08-23 01:52:26 +02:00
parent 4061ce860f
commit 5bfc4a6a7d
2 changed files with 21 additions and 1 deletions
Download patch file Download diff file Expand all files Collapse all files

9
docs/intakes/residuals.md
View file

@ -68,6 +68,15 @@ description: |
identity, and network contract needed by both local profiles. Do not restore
host-side execution as a workaround.
A production retry on 2026-08-23 removed the upstream actor mismatch and
reached the same boundary with governed actor agt. Glas created sandbox
d750cd5c, then failed closed at session_start before dispatch or commit
because direct nsenter remained Operation not permitted. The sandbox was
destroyed and its workspace removed. Loading Ubuntu's bwrap user-namespace
AppArmor profile kept bwrap alive with child CapEff=0 but did not grant the
consumer namespace-entry authority. This strengthens the owner-exec need; it
does not justify widening host execution.
Done when a non-secret probe and one real rein command execute inside the
namespace, the source checkout is not visible/mutable, required egress is
explicit, and teardown removes the sandbox workspace.