You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit 8d6237a
Browse filesBrowse the repository at this point in the historyBrowse files
Copy file name to clipboardExpand all lines: rfc/NNNN-gateway-mcp-sandbox-creation/README.md
+5-2Lines changed: 5 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -432,13 +432,16 @@ the gateway proves the child's policy against the parent's current policy,
432
432
without provider layers. The lead's children are bounded by
433
433
the lead's policy, its grandchildren by its children's policies, and so on, so
434
434
each level can only narrow: `child ≤ parent ≤ global maximum`, the model in
435
-
#2025. A single tree-wide ceiling, the lead's policy, would let a child that was
435
+
the spike on agents setting maximum policies for spawned agents
436
+
([#2025](https://github.com/NVIDIA/OpenShell/issues/2025)). A single tree-wide ceiling, the lead's policy, would let a child that was
436
437
given only GitHub read access create a grandchild with everything the lead has.
437
438
438
439
Because the ceiling is the parent's policy at the moment of the create, a
439
440
parent whose policy has grown through an approved proposal can pass that access
440
441
on, and one whose policy has shrunk cannot. Children already running when a
441
-
parent's policy shrinks keep their policy; revalidating them is #3808.
442
+
parent's policy shrinks keep their policy; revalidating them is the subject of
0 commit comments