TPI-015 eval-first monkey model operator send record and reply capture

notes/pr14_update_summary.md

@@ -0,0 +1,19 @@
+# PR #14 Update Summary
+
+## Operator send record
+
+The branch now provides one editable surface for whether the outbound dispatch
+was sent and how it was referenced.
+
+## Reply capture surface
+
+The branch now provides one explicit place to paste the returned filled block.
+
+## Intake handoff record
+
+The branch now provides one editable handoff record for exact-shape,
+transition, and intake readiness state.
+
+## Current label
+
+`continue_sharpening`

notes/tpi_015_decision.md

@@ -0,0 +1,23 @@
+# TPI-015 Decision
+
+## Current bottleneck
+
+The only blocker is still the absence of one returned filled provider block.
+
+## Decision label
+
+`continue_sharpening`
+
+## Exact next action
+
+Keep the operator send record explicit, paste any returned filled block into the
+reply capture surface, and update the intake handoff record before any attach
+begins.
+
+## Turn DoD
+
+- dispatch state explicit
+- reply presence explicit
+- shape check explicit
+- transition state explicit
+- intake readiness explicit

notes/tpi_015_intake_handoff_record.md

@@ -0,0 +1,21 @@
+# TPI-015 Intake Handoff Record
+
+## Editable fields
+
+- returned_block_matches_exact_shape: yes | no | not_applicable
+- transition_rule_passed: yes | no | not_applicable
+- intake_may_start_now: yes | no
+- intake_started: yes | no
+- intake_handoff_reference: <fill or not_applicable>
+- decision_label: continue_sharpening | promote_to_execution_resume | move_to_failure_ledger
+
+## Rule
+
+Use this record to decide whether the pasted returned block may move into
+TPI-011 intake immediately.
+
+## Decision rule
+
+- returned filled 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`

notes/tpi_015_operator_send_record.md

@@ -0,0 +1,20 @@
+# TPI-015 Operator Send Record
+
+## Editable fields
+
+- outbound_dispatch_sent: yes | no
+- sent_timestamp_or_reference: <fill or not_applicable>
+- sent_by: <fill or not_applicable>
+- dispatch_channel_or_reference: <fill or not_applicable>
+- current_bottleneck: one returned filled provider block missing
+- exact_next_action: <fill>
+
+## Usage
+
+Update this note whenever the fixed TPI-012 outbound dispatch packet is sent,
+re-sent, or confirmed as not yet sent.
+
+## Rule
+
+This record is the editable operator surface for whether the fixed outbound
+dispatch packet was actually sent.

notes/tpi_015_reply_capture.md

@@ -0,0 +1,17 @@
+# TPI-015 Reply Capture
+
+## Editable fields
+
+- returned_filled_block_present: yes | no
+- returned_block_pasted_below: yes | no
+- returned_block_source_reference: <fill or not_applicable>
+- returned_block_received_timestamp: <fill or not_applicable>
+
+## Paste exact returned block below this line
+
+<none>
+
+## Rule
+
+If no returned filled block exists yet, keep `returned_filled_block_present: no`
+and leave the pasted section as `<none>`.