diff --git a/packages/paperclip-runner/spec/paperclip-native-runner-implementation-plan.md b/packages/paperclip-runner/spec/paperclip-native-runner-implementation-plan.md
index 72e72841fe8..364eb7da42b 100644
--- a/packages/paperclip-runner/spec/paperclip-native-runner-implementation-plan.md
+++ b/packages/paperclip-runner/spec/paperclip-native-runner-implementation-plan.md
@@ -343,12 +343,20 @@ the reported machine port. Require screenshots for UX and QA review.
 demo chats, steer and interrupt a live Codex turn, resolve at least one real
 request, inspect subagent/goal state when supported, refresh and replay the same
 session, and approve or revise the interaction contract. Do not create Phase 5
-tasks until the user explicitly accepts this checkpoint and asks to continue.
+tasks until this checkpoint records acceptance and every Phase 4b gate passes.
 
-**Planning-only state (2026-08-08):** Phase 4 is still finishing. This section
-specifies Phase 4b only. Do not create Phase 4b implementation children, start a
-service, claim a port, or start Phase 5 until the board approves the updated plan
-and later explicitly authorizes execution after Phase 4 completes.
+**Authorization and execution state (2026-08-08):** Phase 4 implementation,
+security review, CTO contract review, QA validation, and the isolation-evidence
+follow-up are complete. The board accepted the Phase 4 result and explicitly
+authorized Phase 4b execution. Create one Phase 4b checkpoint issue with
+parallel lowest-layer protocol/server and UX decision work, followed by the
+browser implementation, Security and CTO reviews, QA tutorial execution, and a
+human checkpoint. Keep every change and all evidence inside
+`packages/paperclip-runner/` on the existing branch. The board also authorized
+Phase 5 conditionally: do not create or start Phase 5 until the complete Phase
+4b tracer, targeted and package acceptance tests, package-local documentation,
+tutorial, screenshots, OKF journal entry, review gates, QA evidence, live
+service handoff, and human checkpoint are complete.
 
 ## Phase 5 — Browser reference console and reusable SDK surface
 
@@ -376,7 +384,9 @@ the accepted Phase 4b lifecycle without importing demo internals.
 **Owners/review:** UXDesigner creates/reviews the component plan first; ClaudeCoder or CodexCoder implements after UX approval; QA performs browser validation and screenshot review.
 
 **Depends on:** completed and human-accepted Phase 4b. Do not run it in parallel
-with Phase 4 or Phase 4b because it freezes APIs from the live proof.
+with Phase 4b because it freezes APIs from the live proof. Phase 5 is
+conditionally authorized, but its issue graph remains uncreated until the Phase
+4b checkpoint records all required passing evidence.
 
 **Human checkpoint:** use the browser tutorial as a small SDK consumer, run fake and real-driver sessions, and give UI feedback before Paperclip integration starts.
 
diff --git a/packages/paperclip-runner/spec/paperclip-native-runner-spike-spec.md b/packages/paperclip-runner/spec/paperclip-native-runner-spike-spec.md
index af830f122ab..e3d73fb6e1e 100644
--- a/packages/paperclip-runner/spec/paperclip-native-runner-spike-spec.md
+++ b/packages/paperclip-runner/spec/paperclip-native-runner-spike-spec.md
@@ -6667,17 +6667,20 @@ The completion evidence must include a real Codex end-to-end run and a live
 service started on this execution machine. The checkpoint comment must state the
 exact startup command, host binding, port, and reachable `paperclip-dev:PORT` so
 the human can exercise it. That runtime handoff is an implementation/QA
-deliverable, not part of this planning-only revision.
+deliverable for the authorized Phase 4b execution.
 
-Phase 5 begins only after the Phase 4b human checkpoint is accepted and the user
-explicitly asks to continue. Phase 5 generalizes the accepted browser proof into
-a stable TypeScript SDK, reusable component contracts, and a second minimal
+Phase 5 begins only after the Phase 4b human checkpoint records a working live
+service and passing targeted and package acceptance tests, documentation,
+tutorial, screenshots, OKF evidence, reviews, and QA. The board conditionally
+authorized that transition on 2026-08-08, so no additional planning approval is
+required after those gates pass. Phase 5 generalizes the accepted browser proof
+into a stable TypeScript SDK, reusable component contracts, and a second minimal
 consumer application. Phase 6 remains the first Paperclip control-plane
 integration phase.
 
 ## 30. Dependency sequencing
 
-The phase dependency graph, task-creation gates, owner guidance, per-phase completion contract, and retained issue-sized future backlog are maintained in [`paperclip-native-runner-implementation-plan.md`](./paperclip-native-runner-implementation-plan.md). The current order is Phase 4 completion and human acceptance, then Phase 4b planning approval and explicit execution authorization, then the Phase 4b human checkpoint, then Phase 5. Do not create Phase 4b or Phase 5 implementation tasks from this planning revision.
+The phase dependency graph, task-creation gates, owner guidance, per-phase completion contract, and retained issue-sized future backlog are maintained in [`paperclip-native-runner-implementation-plan.md`](./paperclip-native-runner-implementation-plan.md). Phase 4 is complete and accepted, and Phase 4b execution is authorized. The current order is parallel Phase 4b lowest-layer protocol/server and UX decision work, then browser implementation, Security and CTO reviews, QA and live-service evidence, the Phase 4b human checkpoint, and only then the conditionally authorized Phase 5 issue graph. Do not create Phase 5 tasks before the complete Phase 4b checkpoint passes.
 
 ---