TPI-020 eval-first monkey model external send required gate

notes/pr19_update_summary.md

@@ -0,0 +1,18 @@
+# PR #19 Update Summary
+
+## External send required gate
+
+The branch now states explicitly that no further execution-distance progress is possible until the fixed outbound dispatch packet is actually sent.
+
+## Acceptable send evidence
+
+The branch now defines what does and does not count as real send evidence.
+
+## No-further-schema-only-loop rule
+
+The branch now states explicitly that further schema-only loops do not count as
+meaningful progress beyond this gate.
+
+## Current label
+
+`continue_sharpening`

notes/tpi_020_acceptable_send_evidence.md

@@ -0,0 +1,17 @@
+# TPI-020 Acceptable Send Evidence
+
+## Accept as real send evidence only if at least one concrete trace exists
+
+- sent_timestamp_or_reference
+- sent_by
+- dispatch_channel_or_reference
+- sent_artifact_reference
+- or an equivalent concrete trace that proves the fixed outbound dispatch was
+  actually sent
+
+## Insufficient as send evidence
+
+- intention to send
+- chosen branch equals send_now
+- placeholders only
+- schema updates without a concrete send trace

notes/tpi_020_decision.md

@@ -0,0 +1,19 @@
+# TPI-020 Decision
+
+## Current bottleneck
+
+One returned filled provider block is still missing.
+
+## Decision label
+
+`continue_sharpening`
+
+## Exact next action
+
+Perform the real outbound send and record acceptable send evidence. Without that evidence, remain blocked at the external-send-required gate.
+
+## Branch rule
+
+- actual send evidence absent -> `continue_sharpening`
+- returned block accepted + landing verified -> `promote_to_execution_resume`
+- returned block accepted + attach/landing failure -> `move_to_failure_ledger`

notes/tpi_020_external_send_required.md

@@ -0,0 +1,13 @@
+# TPI-020 External Send Required Gate
+
+## Gate
+
+No further execution-distance progress is possible until the fixed outbound dispatch packet is actually sent.
+
+## Manual external action requirement
+
+The next actor must perform the real outbound send outside this repository workflow if needed, then record concrete send evidence back into the operational record.
+
+## Rule
+
+Do not treat schema-only refinement as progress once this gate is reached.

notes/tpi_020_external_send_required_gate.md

@@ -0,0 +1,18 @@
+# TPI-020 External Send Required Gate
+
+## Gate statement
+
+No further execution-distance progress may be claimed until the fixed outbound
+dispatch packet is actually sent and concrete send evidence is recorded.
+
+## Current gate state
+
+- external_send_required: yes
+- actual_send_evidence_present: no
+- progress_claim_allowed: no
+- blocker: fixed outbound dispatch packet has not yet been sent
+
+## Rule
+
+Schema refinement beyond TPI-020 does not count as meaningful progress unless
+it is accompanied by actual send evidence.

notes/tpi_020_no_further_schema_only_loop.md

@@ -0,0 +1,5 @@
+# TPI-020 No Further Schema-Only Loop Rule
+
+Once TPI-020 is reached, a loop that does not add concrete send evidence or a returned filled provider block should not be counted as meaningful execution-distance progress.
+
+If no send evidence is added, keep the blocker explicit and avoid presenting the turn as a new operational breakthrough.

notes/tpi_020_no_further_schema_only_loop_rule.md

@@ -0,0 +1,17 @@
+# TPI-020 No-Further-Schema-Only-Loop Rule
+
+## Rule
+
+After TPI-020, schema-only refinement is not sufficient progress on its own.
+
+## What counts as progress beyond this gate
+
+- real outbound dispatch performed
+- acceptable send evidence recorded
+- operational record updated from that evidence
+
+## What does not count as progress beyond this gate
+
+- another schema-only loop
+- another placeholder-only note
+- another branch that claims forward motion without real send evidence