Skip to content

Commit 8d6237a

Browse files
committed
docs(rfc): link and name issues NVIDIA#2025 and NVIDIA#3808
Signed-off-by: patkraw <[email protected]>
1 parent fc1d6ef commit 8d6237a

1 file changed

Lines changed: 5 additions & 2 deletions

File tree

  • rfc/NNNN-gateway-mcp-sandbox-creation

‎rfc/NNNN-gateway-mcp-sandbox-creation/README.md‎

Lines changed: 5 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -432,13 +432,16 @@ the gateway proves the child's policy against the parent's current policy,
432432
without provider layers. The lead's children are bounded by
433433
the lead's policy, its grandchildren by its children's policies, and so on, so
434434
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
436437
given only GitHub read access create a grandchild with everything the lead has.
437438

438439
Because the ceiling is the parent's policy at the moment of the create, a
439440
parent whose policy has grown through an approved proposal can pass that access
440441
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
443+
[#3808](https://github.com/NVIDIA/OpenShell/issues/3808), "revalidate running
444+
subagents when ancestor authority changes".
442445

443446
**What the agent writes.** The agent supplies only the child's
444447
`network_policies`. The gateway builds the child's full policy from the

0 commit comments

Comments
 (0)