TPI-018 eval-first monkey model live state fill and chosen-branch instantiation

[gb250e]

Purpose

This is the TPI-018 internal review PR.

TPI-017 fixed a chosen-branch execution record, but the workflow still needs one place where placeholders are replaced by actual current values and one chosen branch is instantiated from those real values. TPI-018 packages that live-state fill and chosen-branch instantiation gate.

Thesis

When the workflow is blocked on one returned filled provider block, the next loop should stop describing abstract state and instead fill actual current values, instantiate exactly one chosen branch from those values, and record whether that branch was actually executed or blocked.

Scope

• define one live-state fill surface
• define one chosen-branch instantiation surface
• preserve the existing send / wait / hand-to-intake branches
• preserve existing handoff / intake / verification boundaries
• preserve public-safe monkey model framing

What is included

• live-state fill note
• chosen-branch instantiation note
• decision note
• PR summary note

What is intentionally not included yet

• a returned filled provider block
• attach attempt
• landing verification result
• execution resume result
• new Git auth recovery work
• model or tokenizer changes

Expected next step

1. replace placeholders with actual current values
2. instantiate exactly one chosen branch from those values
3. record whether that chosen branch was actually executed or blocked
4. continue only from that instantiated live state

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

Current assessment

• TPI-017 で chosen-branch execution record の shape は fixed です。
• TPI-018 の役割は、その shape を actual current values で埋め、one chosen branch を instantiate することです。
• current bottleneck は one returned filled provider block の不在のみです。
• current label は continue_sharpening です。

Evidence checked

• TPI-015 の editable operational record には outbound dispatch send の実記録がありません。
• reply capture に returned filled block は貼られていません。
• intake handoff record も not_applicable / 未開始の状態です。
• したがって actual live state は dispatch 未送信、returned block 不在、intake 未開始です。
• この current reality では send_now だけが有効な chosen branch です。

Consequence

• actual live state は placeholder ではなく explicit value で固定されます。
• chosen branch は send_now として 1 つだけ instantiate されます。
• branch preconditions は satisfied ですが、branch itself はまだ未実行です。
• next blocker after chosen branch は fixed outbound dispatch packet がまだ送られていないことです。

Required next step

• fixed outbound dispatch packet を実際に送る
• send reference を live-state surface に記録する
• reply が来たら reply capture と intake handoff record を更新する

Control note

• Git auth recovery、environment reselection、model changes は reopen しません。
• 複数 branch を混ぜません。
• returned block なしで attach / execution resume に進みません。

1. current bottleneck
   One returned filled provider block is still missing.

2. decision label
   continue_sharpening

3. exact next action
   Send the fixed outbound dispatch packet and then record the real send reference in the live-state surface.

4. actual live state

• outbound_dispatch_sent: no
• sent_timestamp_or_reference: not_applicable
• sent_by: not_applicable
• dispatch_channel_or_reference: not_applicable
• returned_filled_block_present: no
• returned_block_pasted_below: no
• returned_block_source_reference: not_applicable
• returned_block_received_timestamp: not_applicable
• returned_block_matches_exact_shape: not_applicable
• transition_rule_passed: not_applicable
• intake_may_start_now: no
• intake_started: no

5. chosen branch instantiation

• chosen_branch: send_now
• branch_preconditions_satisfied: yes
• branch_executed: no
• execution_reference: operator send action not yet performed in this turn

6. next blocker after chosen branch
   fixed outbound dispatch packet still needs to be sent before a returned filled provider block can exist

Turn DoD

• actual values explicit
• chosen branch explicit
• executed or blocked explicit
• next blocker explicit
• no placeholder ambiguity

[gb250e]

LLM review checkpoint for TPI-018

Current assessment

• continue_sharpening の維持で正しいです。
• TPI-018 は actual live state fill と chosen-branch instantiation の完成形として十分です。
• current bottleneck は引き続き one returned filled provider block の不在のみです。

Evidence checked

• PR TPI-018 eval-first monkey model live state fill and chosen-branch instantiation #17 の差分は live state、chosen branch、decision、summary を actual values で固定しています。
• A+B+C レポートも揃っており、placeholder ambiguity は除去されています。
• chosen branch は send_now で、preconditions は satisfied、branch itself は未実行です。

Consequence

• TPI-018 は live-state instantiation surface として妥当です。
• 次ループでは schema や instantiation を増やすのではなく、fixed outbound dispatch packet を実際に送った証跡を残す dispatch execution evidence を成果物にするのが高価値です。

Required next step

• TPI-019 では dispatch execution evidence gate を定義してください。
• 具体的には、send performed or not, send timestamp/reference, sender, channel/reference, and post-send state update を 1 セットで固定してください。

Control note

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