diff --git a/notes/pr18_update_summary.md b/notes/pr18_update_summary.md
new file mode 100644
index 0000000000..ff14229e34
--- /dev/null
+++ b/notes/pr18_update_summary.md
@@ -0,0 +1,19 @@
+# PR #18 Update Summary
+
+## Dispatch execution evidence
+
+The branch now fixes one place to record dispatch execution evidence, but the
+current reality is still `send_performed: no`.
+
+## Post-send state update
+
+The branch now fixes the post-send state update surface, but that state is not
+entered until the fixed outbound dispatch packet is actually sent.
+
+## Current label
+
+`continue_sharpening`
+
+## Next step
+
+Dispatch execution is next. Attach is still blocked.
diff --git a/notes/tpi_019_decision.md b/notes/tpi_019_decision.md
new file mode 100644
index 0000000000..9e3f6f8912
--- /dev/null
+++ b/notes/tpi_019_decision.md
@@ -0,0 +1,20 @@
+# TPI-019 Decision
+
+## Current bottleneck
+
+One returned filled provider block is still missing.
+
+## Decision label
+
+`continue_sharpening`
+
+## Exact next action
+
+Perform the fixed outbound dispatch packet and record concrete send evidence
+immediately after that send occurs.
+
+## Branch rule
+
+- returned filled block absent -> `continue_sharpening`
+- returned block accepted + landing verified -> `promote_to_execution_resume`
+- returned block accepted + attach/landing failure -> `move_to_failure_ledger`
diff --git a/notes/tpi_019_dispatch_execution_evidence.md b/notes/tpi_019_dispatch_execution_evidence.md
new file mode 100644
index 0000000000..6e8cdb248a
--- /dev/null
+++ b/notes/tpi_019_dispatch_execution_evidence.md
@@ -0,0 +1,19 @@
+# TPI-019 Dispatch Execution Evidence
+
+## Execution evidence
+
+- outbound_dispatch_sent: no
+- send_performed: no
+- send_timestamp_or_reference: not_applicable
+- sent_by: not_applicable
+- dispatch_channel_or_reference: not_applicable
+- sent_artifact_reference: not_applicable
+
+## Evidence note
+
+- no concrete send artifact is present in the current operational record
+- no provider reply can exist before the fixed outbound dispatch packet is sent
+
+## Rule
+
+Use this note to record whether the fixed outbound dispatch packet was actually sent in this turn, and by whom, where, and with what reference.
diff --git a/notes/tpi_019_post_send_state.md b/notes/tpi_019_post_send_state.md
new file mode 100644
index 0000000000..d9eb655330
--- /dev/null
+++ b/notes/tpi_019_post_send_state.md
@@ -0,0 +1,14 @@
+# TPI-019 Post-Send State
+
+## Post-send state update
+
+- outbound_dispatch_sent: no
+- sent_timestamp_or_reference: not_applicable
+- sent_by: not_applicable
+- dispatch_channel_or_reference: not_applicable
+- exact_next_action: perform the fixed outbound dispatch and record concrete
+  send evidence immediately
+
+## Gate
+
+Post-send state update is not entered until `send_performed: yes`.
diff --git a/notes/tpi_019_post_send_state_update.md b/notes/tpi_019_post_send_state_update.md
new file mode 100644
index 0000000000..be6178685a
--- /dev/null
+++ b/notes/tpi_019_post_send_state_update.md
@@ -0,0 +1,14 @@
+# TPI-019 Post-Send State Update
+
+## After send
+
+If send is performed in this turn, update at least:
+- outbound_dispatch_sent: yes
+- sent_timestamp_or_reference
+- sent_by
+- dispatch_channel_or_reference
+- exact_next_action: wait for returned filled provider block
+
+## If send is not performed
+
+Keep the blocker explicit and record why send did not occur.