diff --git a/notes/pr13_update_summary.md b/notes/pr13_update_summary.md
new file mode 100644
index 0000000000..fc2bd47b00
--- /dev/null
+++ b/notes/pr13_update_summary.md
@@ -0,0 +1,19 @@
+# PR #13 Update Summary
+
+## Operator dispatch kit
+
+The branch now defines the operational kit needed to send the fixed outbound
+packet and track reply-to-intake readiness.
+
+## Turn DoD
+
+The branch now defines explicit done criteria for 10+ loop operational turns.
+
+## At-a-glance status surface
+
+The branch now defines one explicit status surface for dispatch, reply,
+transition, and intake readiness.
+
+## Current label
+
+`continue_sharpening`
diff --git a/notes/tpi_014_decision.md b/notes/tpi_014_decision.md
new file mode 100644
index 0000000000..da65b1ec19
--- /dev/null
+++ b/notes/tpi_014_decision.md
@@ -0,0 +1,25 @@
+# TPI-014 Decision
+
+## Current bottleneck
+
+The only blocker is still the absence of one returned filled provider block.
+
+## Decision label
+
+`continue_sharpening`
+
+## Exact next action
+
+Send the fixed outbound dispatch packet if not yet sent. Otherwise, record
+whether a returned filled block arrived, whether it matches the exact return
+shape, whether the transition rule passed, and whether intake may start now.
+
+## Branch rule
+
+- returned block absent: `continue_sharpening`
+- returned block accepted and landing verified: `promote_to_execution_resume`
+- returned block accepted but attach or landing fails: `move_to_failure_ledger`
+
+## Turn DoD
+
+This turn is done only if the status surface and turn DoD fields are explicit.
diff --git a/notes/tpi_014_operator_dispatch_kit.md b/notes/tpi_014_operator_dispatch_kit.md
new file mode 100644
index 0000000000..eb69742d04
--- /dev/null
+++ b/notes/tpi_014_operator_dispatch_kit.md
@@ -0,0 +1,27 @@
+# TPI-014 Operator Dispatch Kit
+
+## Objective
+
+Package the exact operational surface needed to send the fixed outbound dispatch packet, track whether it was sent, record whether a reply arrived, and decide whether the reply may move into intake.
+
+## Fixed outbound artifact
+
+- use the TPI-012 outbound dispatch packet exactly as written
+- do not rewrite the return block shape
+- do not reopen provider discovery, Git auth, or execution logic
+
+## Operator checklist
+
+- outbound dispatch packet prepared
+- outbound dispatch packet sent or not sent
+- returned filled block received or not received
+- returned reply matches the exact return block or not
+- transition rule passed or not passed
+- TPI-011 intake may start now or not
+- TPI-011 intake started or not started
+
+## Rule
+
+This loop is complete only when the operational state is explicit enough that
+the next actor can tell, at a glance, whether the workflow is still waiting on
+a returned filled block or may move into intake immediately.
diff --git a/notes/tpi_014_status_surface.md b/notes/tpi_014_status_surface.md
new file mode 100644
index 0000000000..5e1f21286d
--- /dev/null
+++ b/notes/tpi_014_status_surface.md
@@ -0,0 +1,27 @@
+# TPI-014 Status Surface
+
+## Required explicit fields
+
+- outbound_dispatch_sent: yes | no
+- returned_filled_block_present: yes | no
+- returned_block_matches_exact_shape: yes | no | not_applicable
+- transition_rule_passed: yes | no | not_applicable
+- intake_started: yes | no
+- intake_may_start_now: yes | no
+- still_waiting_on_provider: yes | no
+- current_bottleneck: <text>
+- exact_next_action: <text>
+
+## Field meanings
+
+- `outbound_dispatch_sent`: whether the TPI-012 outbound packet has actually been sent
+- `returned_filled_block_present`: whether any returned block exists yet
+- `returned_block_matches_exact_shape`: whether the returned reply uses the exact TPI-012 return block shape
+- `transition_rule_passed`: whether the TPI-012 transition rule passed
+- `intake_started`: whether TPI-011 intake has already started
+- `intake_may_start_now`: whether intake may begin immediately in this turn
+- `still_waiting_on_provider`: whether the workflow is still blocked on provider reply
+- `current_bottleneck`: the single active blocker
+- `exact_next_action`: the one next move for the next actor
+
+`not_applicable` is allowed only when no returned block exists yet.
diff --git a/notes/tpi_014_turn_dod.md b/notes/tpi_014_turn_dod.md
new file mode 100644
index 0000000000..ae2710f71c
--- /dev/null
+++ b/notes/tpi_014_turn_dod.md
@@ -0,0 +1,26 @@
+# TPI-014 Turn DoD
+
+A turn is done only if all of the following are explicit in the PR artifacts or
+PR comment:
+
+- current bottleneck
+- decision label
+- exact next action
+- outbound dispatch sent or not
+- returned filled block exists or not
+- returned block matches exact shape or not
+- transition rule passed or not
+- intake may start now or must remain blocked
+
+## Checklist
+
+- [ ] current bottleneck is explicit
+- [ ] decision label is explicit
+- [ ] exact next action is explicit
+- [ ] outbound dispatch state is explicit
+- [ ] returned block presence is explicit
+- [ ] exact-shape match state is explicit
+- [ ] transition rule state is explicit
+- [ ] intake start readiness is explicit
+
+If any one item is missing, the turn is not done.