Skip to content

TPI-017 eval-first monkey model chosen-branch execution record#16

Draft
gb250e wants to merge 4 commits intoexp/decision-card-016from
exp/chosen-branch-017
Draft

TPI-017 eval-first monkey model chosen-branch execution record#16
gb250e wants to merge 4 commits intoexp/decision-card-016from
exp/chosen-branch-017

Conversation

@gb250e
Copy link
Copy Markdown
Owner

@gb250e gb250e commented Mar 21, 2026

Purpose

This is the TPI-017 internal review PR.

TPI-016 fixed a send-or-wait decision card, but the workflow still needs one record that shows which branch was actually chosen from current reality and whether that chosen branch was truly executed or blocked. TPI-017 packages that chosen-branch execution record.

Thesis

When the workflow is blocked on one returned filled provider block, the next loop should expose one record that captures current reality, the single chosen branch, whether its preconditions were satisfied, and whether that chosen branch was actually executed or blocked.

Scope

  • define one chosen-branch execution record
  • preserve the existing send / wait / hand-to-intake branches
  • preserve existing handoff / intake / verification boundaries
  • preserve public-safe monkey model framing

What is included

  • chosen-branch execution record 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. snapshot current reality
  2. choose exactly one branch from TPI-016
  3. record whether the branch preconditions were satisfied
  4. record whether the chosen branch was actually executed or blocked
  5. continue only from that chosen-branch execution record

Public-facing safety

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

@gb250e
Copy link
Copy Markdown
Owner Author

gb250e commented Mar 21, 2026

Codex review checkpoint for TPI-017

Current assessment

  • TPI-016 で send-or-wait decision card は fixed です。
  • TPI-017 の役割は、その決定を chosen-branch execution record として残すことです。
  • current bottleneck は one returned filled provider block の不在のみです。
  • current label は continue_sharpening です。

Evidence checked

Consequence

  • current reality は snapshot として explicit である必要があります。
  • chosen branch は 1 つだけ explicit である必要があります。
  • branch preconditions satisfied と branch executed or blocked は explicit である必要があります。
  • next blocker after chosen branch は explicit である必要があります。

Required next step

  • current reality snapshot を更新する
  • TPI-016 から one branch を選ぶ
  • chosen branch の preconditions satisfied を記録する
  • chosen branch が executed か blocked かを記録する
  • next blocker after chosen branch を記録する

Control note

  • Git auth recovery、environment reselection、model redesign は reopen しません。
  • 複数 branch を混ぜません。
  • returned block なしで attach を始めません。
  1. current bottleneck
    One returned filled provider block is still missing.

  2. decision label
    continue_sharpening

  3. exact next action
    Record current reality, choose exactly one branch from TPI-016, and record whether that chosen branch was actually executed or blocked.

  4. current reality snapshot
    An explicit snapshot with at least:

  • outbound_dispatch_sent
  • returned_filled_block_present
  • returned_block_matches_exact_shape
  • transition_rule_passed
  • current_reality_reference
  1. chosen branch
    One explicit value only:
  • chosen_branch: send_now | wait | hand_to_intake | not_selected
  1. chosen-branch execution record
    A record with at least:
  • branch_preconditions_satisfied
  • branch_executed
  • execution_reference
  • next_blocker_after_chosen_branch

Turn DoD

  • current reality explicit
  • chosen branch explicit
  • branch preconditions explicit
  • executed or blocked explicit
  • next blocker explicit

Copy link
Copy Markdown
Owner Author

gb250e commented Mar 21, 2026

LLM review checkpoint for TPI-017

Current assessment

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

Evidence checked

  • PR TPI-017 eval-first monkey model chosen-branch execution record #16 の差分は current reality snapshot、chosen branch、branch preconditions、executed or blocked、next blocker を一貫して固定しています。
  • A+B+C レポートも揃っており、chosen branch を 1 つだけ持つ運用境界が明示されています。
  • returned filled block 不在のまま attach / execution resume に進まない境界も保たれています。

Consequence

  • TPI-017 は chosen-branch execution-record surface として妥当です。
  • 次ループでは record schema を定義し続けるのではなく、actual current values を埋めた live state として instantiate するのが高価値です。

Required next step

  • TPI-018 では live state fill / chosen-branch instantiation gate を定義してください。
  • 具体的には、placeholder ではなく actual values を入れた current reality、chosen branch、branch executed or blocked、next blocker を 1 セットで確定してください。

Control note

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants