TPI-010 eval-first monkey model execution-ready handoff packet

[gb250e]

Purpose

This is the TPI-010 internal review PR.

TPI-009 established a clean absent-state trusted remote gate. The next highest-value move is not to repeat that absent-state, but to define one execution-ready handoff packet that can be filled by the provider side and used immediately to start attach.

Thesis

Once trusted remote surfaces are restored, the workflow should require one minimal concrete handoff packet that is sufficient to begin attach and landing verification immediately, without reopening Git auth, environment, or model debates.

Scope

• define an execution-ready handoff packet
• define the acceptance gate for that packet
• define the first-command sequence after acceptance
• preserve the unchanged TPI-004 execution contract
• preserve public-safe monkey model framing

What is included

• packet template note
• acceptance gate note
• first-command note
• minimal stub for TPI-010 branch identity

What is intentionally not included yet

• an actual filled provider packet
• attach attempt
• landing verification result
• execution resume result
• new Git auth recovery work
• model or tokenizer changes

Expected next step

1. receive one filled execution-ready handoff packet
2. judge it against the acceptance gate
3. attach immediately if accepted
4. verify landing in /workspace/parameter-golf
5. resume the unchanged TPI-004 baseline/candidate contract

Public-facing safety

This branch uses monkey model framing only and is intended to avoid exposing proprietary architecture language.

[gb250e]

Codex review checkpoint for TPI-010

Current assessment

• この PR は execution-ready handoff packet の定義に集中してください。
• trusted remote / absent-state 境界は PR TPI-009 eval-first monkey model trusted remote handoff gate #8 までで確定済みです。
• current bottleneck は execution-ready な concrete provider-supplied handoff packet の不在のみです。

Evidence checked

• PR TPI-009 eval-first monkey model trusted remote handoff gate #8 で trusted remote handoff gate は成立済みです。
• PR TPI-010 eval-first monkey model execution-ready handoff packet #9 は packet template / acceptance gate / first-command sequence を扱う最小ループです。

Consequence

• Git auth / environment / model debate は reopen しません。
• filled packet を 1 回で attach に使える形へ正規化することがこのループの価値です。

Required next step

• packet template を provider-fillable な形に tighten してください。
• acceptance gate を yes/no 判定可能な形に tighten してください。
• acceptance 後の first-command sequence を landing verification まで明確化してください。

Control note

• generic provider advice、local SSH keys、old rediscovery は insufficient です。
• 破壊的 Git 操作は前提にしないでください。

[gb250e]

Codex review checkpoint for TPI-010

Current assessment

• trusted remote review surfaces are maintained
• the only lead blocker is the absence of one execution-ready provider-supplied handoff packet
• current label remains continue_sharpening

Evidence checked

• PR TPI-007 eval-first monkey model external handoff gate #6 is the latest trusted TPI-007 absent-handoff surface
• PR TPI-008 eval-first monkey model git auth recovery gate #7 is the trusted TPI-008 remote-reflection recovery surface
• PR TPI-009 eval-first monkey model trusted remote handoff gate #8 is the trusted TPI-009 handoff gate
• PR TPI-010 eval-first monkey model execution-ready handoff packet #9 defines the execution-ready packet surface but does not contain an actual filled packet
• notes/tpi_010_packet_template.md, notes/tpi_010_acceptance_gate.md, and notes/tpi_010_first_commands.md now fix the packet shape, gate, and first-command sequence

Consequence

• do not start attach, landing verification, or unchanged TPI-004 resume in this turn
• do not reopen Git auth, environment selection, or monkey model design debate
• keep the current branch as a packet-finalization surface only

Required next step

Receive one filled packet containing:

• pod_identifier_or_display_name
• landing_target: /workspace/parameter-golf
• workspace_confirmation
• one concrete route:
  • exact provider-supplied attach command, or
  • exact SSH tuple: host, username, port

Control note

• local SSH keys, generic Runpod instructions, and generic provider dashboard advice are insufficient
• if the packet is accepted, start immediately with the fixed verification sequence before any baseline or candidate command

[gb250e]

LLM review checkpoint for TPI-010

Current assessment

• continue_sharpening の維持で正しいです。
• TPI-010 は execution-ready handoff packet の完成形を十分に固定できています。
• current bottleneck は引き続き one filled packet の不在のみです。

Evidence checked

• PR TPI-010 eval-first monkey model execution-ready handoff packet #9 の差分は accepted packet final shape、acceptance gate、first-command sequence、resume condition を一貫して固定しています。
• attach / landing verification / unchanged TPI-004 resume を誤って始めない stop rule も明示されています。
• review checkpoint も trusted remote / no reopen 方針で整合しています。

Consequence

• TPI-010 は packet-finalization surface として妥当です。
• 次ループでは packet を定義し続けるのではなく、provider 側に一回で返送してもらう request form を固定するのが高価値です。

Required next step

• TPI-011 では provider-facing filled packet request を定義してください。
• 具体的には、相手がそのままコピペして埋められる返送テンプレート、受領時の yes/no intake check、accepted 後の即時 attach 開始条件を 1 つに束ねてください。

Control note

• generic provider advice / local SSH keys / old rediscovery は引き続き insufficient です。
• 破壊的 Git 操作は新ループでも前提にしないでください。