TPI-011 eval-first monkey model provider-facing handoff request form

[gb250e]

Purpose

This is the TPI-011 internal review PR.

TPI-010 fixed the execution-ready packet shape, but the workflow still lacks one actual filled packet. The next highest-value move is to define one provider-facing request form that can be copied, filled, and returned in one shot.

Thesis

Once the execution-ready packet shape is fixed, the workflow should minimize further ambiguity by issuing one returnable provider-facing form and accepting only a fully filled response before attach begins.

Scope

• define one provider-facing request form
• define the intake check for the returned form
• define the ready condition for immediate verification start
• preserve the unchanged TPI-004 execution contract
• preserve public-safe monkey model framing

What is included

• request form note
• intake check note
• ready condition note

What is intentionally not included yet

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

Expected next step

1. send one returnable request form to the provider side
2. receive one filled packet
3. judge it against the intake check
4. start the fixed verification sequence immediately if accepted
5. resume unchanged TPI-004 only after landing verification

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-011

Current assessment

• TPI-010 で execution-ready packet shape は fixed です。
• current bottleneck は still one filled provider packet の不在のみです。
• current label は continue_sharpening です。

Evidence checked

• PR TPI-009 eval-first monkey model trusted remote handoff gate #8 は trusted remote absent-state gate です。
• PR TPI-010 eval-first monkey model execution-ready handoff packet #9 は execution-ready packet finalization surface です。
• PR TPI-011 eval-first monkey model provider-facing handoff request form #10 は provider-facing request form / intake check / ready condition を扱うループです。
• PR TPI-011 eval-first monkey model provider-facing handoff request form #10 には actual filled packet はまだ含まれていません。

Consequence

• attach はまだ始めません。
• unchanged TPI-004 は landing verification の後ろに維持されます。
• Git auth / environment / model debate は reopen しません。

Required next step

• fixed request form を provider 側へ送る
• one fully filled packet を受け取る
• yes/no intake check を実行する
• accepted なら fixed verification sequence を即開始する

Control note

• generic provider advice、local SSH keys、old rediscovery は insufficient です。
• concrete filled packet なしで attach や execution resume に進みません。

[gb250e]

LLM review checkpoint for TPI-011

Current assessment

• continue_sharpening の維持で正しいです。
• TPI-011 は provider-facing handoff request form の完成形として十分です。
• current bottleneck は引き続き one filled provider packet の不在のみです。

Evidence checked

• PR TPI-011 eval-first monkey model provider-facing handoff request form #10 の差分は request form、intake check、ready condition、decision、PR summary を一貫して固定しています。
• attach / landing verification / unchanged TPI-004 resume を誤って始めない stop rule も明示されています。
• review checkpoint も trusted remote / no reopen 方針で整合しています。

Consequence

• TPI-011 は provider-facing request-form surface として妥当です。
• 次ループでは form を定義し続けるのではなく、provider 側へ実際に渡す outbound dispatch packet を固定するのが高価値です。

Required next step

• TPI-012 では provider-dispatch packet を定義してください。
• 具体的には、相手に送る本文、返送時にそのまま判定できる filled block、受領後の intake transition を 1 つに束ねてください。

Control note

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