TPI-012 eval-first monkey model provider outbound dispatch packet

notes/pr11_update_summary.md

@@ -0,0 +1,20 @@
+# PR #11 Update Summary
+
+## Outbound dispatch packet
+
+The branch now defines one exact outbound message that can be sent directly to
+the provider side.
+
+## Exact return block
+
+The branch now defines one exact reply block that the provider must fill and
+return without changing its shape.
+
+## Reply to intake transition
+
+The branch now defines the exact conditions under which a returned reply may be
+handed to the TPI-011 intake gate.
+
+## Current label
+
+`continue_sharpening`

notes/tpi_012_decision.md

@@ -0,0 +1,20 @@
+# TPI-012 Decision
+
+## Current bottleneck
+
+The only blocker is the absence of one returned filled provider block.
+
+## Decision label
+
+`continue_sharpening`
+
+## Exact next action
+
+Send the fixed outbound dispatch packet, receive one returned filled block, and
+pass it into the TPI-011 intake check only if the transition rule is satisfied.
+
+## Branch 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_012_provider_dispatch_packet.md

@@ -0,0 +1,31 @@
+# TPI-012 Provider Dispatch Packet
+
+## Outbound message
+
+Send this exact message to the provider side.
+
+```md
+Please return one fully filled handoff reply in the exact block below.
+Do not send generic instructions or partial metadata.
+The target workspace must remain `/workspace/parameter-golf`.
+
+Reply block:
+
+pod_identifier_or_display_name: <fill>
+landing_target: /workspace/parameter-golf
+workspace_confirmation: <fill>
+route_type: provider_attach_command | ssh_tuple
+
+if route_type == provider_attach_command:
+  exact_attach_command: <fill>
+
+if route_type == ssh_tuple:
+  host: <fill>
+  username: <fill>
+  port: <fill>
+```
+
+## Purpose
+
+The provider should be able to copy this message, fill one exact return block,
+and hand it back into the trusted intake flow without reopening old debates.

notes/tpi_012_return_block.md

@@ -0,0 +1,20 @@
+# TPI-012 Return Block
+
+The provider reply must use this exact block.
+
+```md
+pod_identifier_or_display_name: <fill>
+landing_target: /workspace/parameter-golf
+workspace_confirmation: <fill>
+route_type: provider_attach_command | ssh_tuple
+
+if route_type == provider_attach_command:
+  exact_attach_command: <fill>
+
+if route_type == ssh_tuple:
+  host: <fill>
+  username: <fill>
+  port: <fill>
+```
+
+Any missing field means this is not yet a returned filled packet.

notes/tpi_012_transition_rule.md

@@ -0,0 +1,23 @@
+# TPI-012 Transition Rule
+
+## Transition to TPI-011 intake
+
+Move the reply into TPI-011 intake only when all of the following are true:
+
+- the exact return block is present
+- pod identity is filled
+- landing target is confirmed as `/workspace/parameter-golf`
+- workspace confirmation is filled
+- one concrete route is filled:
+  - `exact_attach_command`, or
+  - `host` + `username` + `port`
+
+## After transition
+
+If the returned block passes the TPI-011 intake check, start the fixed
+verification sequence immediately.
+
+## Reject path
+
+If any required field is missing, do not transition to attach. Keep the label
+at `continue_sharpening`.