Policy Explorer
The OS security kernel: given an approved computer plan, should each action be permitted? Advisory decisions only — the runtime executes nothing. Read-only.
Policy "default-enforce" (enforce) on mcp "mcp-research": 5 allowed, 0 need approval, 0 denied (0 unresolved, fail-closed) → allow. Advisory until the Broker exists.
Policy "default-enforce" (enforce) on mcp "mcp-integration-write": 1 allowed, 2 need approval, 0 denied (0 unresolved, fail-closed) → requires_approval. Advisory until the Broker exists.
Policy "emergency-stop" (enforce) on mcp "mcp-research": 0 allowed, 0 need approval, 5 denied (0 unresolved, fail-closed) → deny. Advisory until the Broker exists.
The Policy Runtime owns approval rules, RBAC/org permissions, token/monetary budgets, rate limits, compliance regimes, maintenance windows, dry-run/simulation, emergency stop, rollback and secret requirements — and returns decisions only. It never executes. POLICY-EXT (ADR-0079) extends the same kernel to judge MCP, Terminal, and Filesystem sessions as normalized policy subjects; unresolved references fail closed; decisions remain advisory until the future Vault → Approval → Broker chain makes allow binding.