local-first · v0.1

Universal Execution Runtime

Phase VIII · V5 — the first runtime whose output is a work product. Given an authorized ProviderExecutionPlan (V4) backed by a binding BrokerGrant (V3), it validates the plan, re-verifies the grant, resolves credentials through the Vault BY REFERENCE, consumes the single-use grant, and dispatches each authorized action — deterministically and fail-closed. The real side effect is the deferred boundary (no real I/O). Inherits the A0 Kernel lifecycle. Read-only.

2
Executed
5
Denied
2
Grants consumed
9
Actions dispatched
Execution boundary is deferred. V5 owns the execution lifecycle up to the boundary — plan validation, grant re-verification, credential resolution by reference (no value), single-use consumption, action dispatch — and produces immutable results. The actual world-touching side effect (network / subprocess / filesystem / browser) is the one deferred boundary a real transport adapter honors. 8 action kinds supported. Executes only; capabilities/approval/provider/boot remain owned by prior runtimes.

The Universal Execution Runtime consumes an authorized ProviderExecutionPlan (V4) and produces an immutable ExecutionResult: it validates the plan is selected and carries a handoff, re-verifies the binding BrokerGrant (V3) is unexpired, unexecuted, and unconsumed, resolves each of the grant's authorized credential references through the Vault (by reference only — the value is never read or released; the One-Way Secret Law), and verifies every action is supported and credential-authorized BEFORE dispatching any — never partially executing an invalid plan. On success it dispatches each action in order, produces artifacts and a value-free append-only audit, and consumes the single-use grant; single-use is a state-level fold, so a reused grant denies on every surface. Fail-closed: any missing authorization, invalid credential, expired lease, provider mismatch, unsupported action, or ambiguity denies with zero actions executed. It performs no real I/O — the world-touching side effect is the deferred boundary — and inherits the A0 Intelligence Kernel lifecycle, redefining no boot behavior.