local-first · v0.1

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.

9
Evaluations
46
Actions judged
16
Need approval
8
Denied
Cross-surface enforcement (POLICY-EXT)74 subjects14 denied34 approve
mcp:mcp-researchallowed
default-enforce · enforce · 5 subjects · checksum 5b519d86
5 allow1 secret name

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.

mcp:mcp-integration-writerequires_approval
default-enforce · enforce · 3 subjects · checksum 384deb07
1 allow2 approve1 destructive3 secret names

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.

mcp:mcp-researchdenied
emergency-stop · enforce · 5 subjects · checksum 53221a69
0 allow5 deny1 secret name

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.