> ## Documentation Index
> Fetch the complete documentation index at: https://docs.gloo.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Week of 2026-04-28 — Sandbox Substrate, RLS hardening, Capabilities widening

> The substrate week. Sandbox phases 1A–4, RLS on the public API, capabilities chains, HITL approvals.

**2026-04-28**

The substrate week. Sandbox phases 1A–4, RLS on forgeApi, capabilities chains, HITL approvals.

Last updated 2026-11-11

·
applies to 2026-05-02

·
main

## Hero

The substrate week

Phases 1A → 4

Tool-capability annotation · lazy provisioning · three-axis policy · factory-worker security parity · cold-start palette · observability surface.

*Hero media slot — replace with the snapshot-graph + replay screenshot from the Phase 4 observability surface.*

## Summary

The substrate week. Sandbox shipped end-to-end across six phases — from the original tool-capability annotation in Phase 1A to the observability surface in Phase 4. Authorization tightened across the public API. The capabilities registry widened to support provider chains, an internal-first secrets store, and a stateless fallback proxy. Human-in-the-loop approvals got assignee wiring end-to-end. About a hundred and twenty PRs in total, the heaviest concentration in convex backend work.

## Highlights

### Sandbox Substrate — Phases 1A through 4

* Tool-capability annotation + substrate detector (Phase 1A)
* Propagate `requiresSandbox` in the tool registry sync (Phase 1A′)
* Lazy provisioning via deferred-init `sandbox_action` wrapper (Phase 1B)
* Three-axis substrate config types + a sandbox-config-to-policy adapter (Phase 1C)
* Consume three-axis `SubstratePolicy` + plumb `substrateKind` into governance (Phase 1D)
* Factory-worker security parity + default-deny egress + local-dev provider (Phase 2)
* Cold-start palette: image hardening + snapshot-warm boot + idle warm pool (Phase 3)
* Observability surface: snapshot graph + replay + diff + provenance + lifetime stream (Phase 4)
* Pass explicit Vercel credentials when provisioning a sandbox
* Set `requiresSandbox=true` on `sandbox_action` and `pa_sandbox_action`

### RLS hardening on the public API

* Authed/admin function builders
* Admin-gate DLQ queries + normalize inline auth
* `returns: v.null()` on 56 void public mutations
* Stamp `agentType` on operator agents + remove governance.tier fallback
* RLS Phase 3 intent comment + `check-public-auth` advisory script

### Capabilities: provider chains and secrets store

* Stateless metadata in provider registry
* Widen `CapabilityConfig.provider` to `providers[]`
* Runtime fallback proxy for stateless chains
* Ctx-aware provider registry + `secrets_store` domain
* `secrets_store` internal provider + Convex table
* `secrets_store` external providers
* Widen virtualKeys schema with `secretRef` + backfill migration
* Narrow `virtual_key_management` to single internal ctx-bound provider

### HITL approvals: assignees

* Schema + `AssigneeTarget` type + resolver + tests
* Human node assignee wiring: resolve, store, notify
* Approval system assignee wiring: create, store, route email
* Console UI: assignee picker + approval badge

### Chat-core — turn-by-turn maturity

* Per-message annotation slot for moderation/governance UIs
* Extract reusable normalizers
* Structured error bubble, retry, cost fallback
* Multi-worker timeline merged query
* Composer maturity: mentions, attachments, draft, banner
* Stream rendering: grouping, dividers, idle-tail, typing, visibility, hover

### Trust Fabric

* Two-Agent Rule all-rung enforcement + agent co-sign
* LTM memory integrity checksums + daily audit cron
* Risk calibration matrix + IR playbooks + AaaS vendor review
* Tool Credentials approval queue + navigation
* Virtual keys issuance approval queue

### Console — dashboards and tools

* `forge-sdk` v2 surface parity
* Dashboard canvas UI, replace home page
* `forge-mcp` v2 surface MCP tools/resources parity
* Personal Agent dashboard tools
* Dashboard Architect agent
* Add Widget dialog + WORKFLOW\_OUTPUT invalidation

### Public API consistency pass II

* Eight changes split large internal modules into thematic siblings; analytics drained into dedicated modules; settings/resources/factories/agents/runs/workflows/ops/org all decomposed.

## What this means

Substrate is no longer optional infrastructure

After Phase 4, the substrate is observable, replayable, and policy-driven. `requiresSandbox` is set on `sandbox_action`, `pa_sandbox_action`, and the factory-worker tools; the three-axis `SubstratePolicy` (privilege, network, image) is consumed by governance; default-deny egress is on for factory workers. The substrate is no longer just "where code runs" — it is part of the trust contract.

The public API is now safer to extend. Every public mutation has an explicit `returns: v.null()` (the type contract is no longer load-bearing on inference); admin and authed function builders centralize the auth pattern; the `check-public-auth` advisory script catches new functions that miss the gate. New operator-agent stamps remove the governance.tier fallback class of bugs.

The capabilities registry is now a real chain. `providers[]` lets a capability fall back through tiers (internal → external A → external B); `secrets_store` lands as a first-class capability with both internal and external providers; virtual keys can now reference secrets via `secretRef`. The provider-chain pattern generalizes to any capability that wants stateless fallback.

## What's next

Sandbox observability is shipped but not yet exposed in the Console — that surface is on the queue for next week. The Console dashboards are foundational; the architect-driven dashboards are still alpha. Phase 6 of the docs strategy (Tier 1 content) starts the following week and will document the substrate work that landed here.

***

**Plan tags:** Sandbox Substrate Phases 1A–4 · RLS hardening · provider chains · HITL assignees · secrets store · LLM proxy

*See also: [Sandbox Substrate architecture](https://docs.gloo.com/forge/build/configure-sandbox.md#how-the-sandbox-works) | [Composable Capabilities](https://docs.gloo.com/forge/concepts/capabilities.md) | [Trust Fabric Internals](https://docs.gloo.com/forge/run/trust-fabric.md)*


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.