Skip to content

TPI-016 eval-first monkey model send-or-wait decision card#15

Draft
gb250e wants to merge 4 commits intoexp/reply-capture-015from
exp/decision-card-016
Draft

TPI-016 eval-first monkey model send-or-wait decision card#15
gb250e wants to merge 4 commits intoexp/reply-capture-015from
exp/decision-card-016

Conversation

@gb250e
Copy link
Copy Markdown
Owner

@gb250e gb250e commented Mar 21, 2026

Purpose

This is the TPI-016 internal review PR.

TPI-015 fixed editable operational records for send state, reply capture, and intake handoff. The next highest-value move is to reduce hesitation by defining one send-or-wait decision card that tells the next actor which single branch to take from current reality.

Thesis

When the workflow is blocked on one returned filled provider block, the next loop should expose one decision card that maps current operational state to exactly one next branch: send now, wait, or hand to intake.

Scope

  • define one send-or-wait decision card
  • define one branch selection rule
  • preserve existing handoff / intake / verification boundaries
  • preserve public-safe monkey model framing

What is included

  • send-or-wait decision card 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. inspect current reality
  2. choose exactly one branch from the decision card
  3. follow only that branch
  4. update the editable operational record accordingly

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

Current assessment

  • TPI-015 で editable operational record は fixed です。
  • TPI-016 の役割は、その current reality から one branch を即決する decision card を与えることです。
  • current bottleneck は one returned filled provider block の不在のみです。
  • current label は continue_sharpening です。

Evidence checked

Consequence

  • 次 actor は 3 分岐のうち 1 つだけを選ぶ必要があります。
  • branch selection rule は first-match で固定します。
  • branch mixing は禁止します。
  • current reality が明示されていれば hesitation なく 1 手を選べます。

Required next step

  • editable operational record を確認する
  • first-match rule に従って 1 つだけ branch を選ぶ
  • chosen branch だけを実行する
  • operational record をその 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
    Read the editable operational record, apply the first-match rule, choose exactly one branch, and follow only that branch.

  4. send-or-wait decision card

  • Branch A: send now
    • use only when outbound_dispatch_sent: no and no returned filled block exists
  • Branch B: wait
    • use only when outbound_dispatch_sent: yes and returned_filled_block_present: no
  • Branch C: hand to intake
    • use only when returned_filled_block_present: yes, returned_block_matches_exact_shape: yes, and transition_rule_passed: yes
  1. branch selection rule
    Evaluate in this order and choose the first branch whose conditions are fully satisfied:

  2. Branch C: hand to intake

  3. Branch A: send now

  4. Branch B: wait
    Do not mix branches.

  5. current reality to chosen branch mapping

  • no dispatch sent and no reply present -> Branch A: send now
  • dispatch already sent and no reply present -> Branch B: wait
  • returned block present and both checks pass -> Branch C: hand to intake
  • returned block present but checks do not pass -> remain continue_sharpening, do not start intake

Turn DoD

  • branch conditions explicit
  • chosen branch explicit
  • no branch mixing
  • current bottleneck explicit
  • next action explicit

Copy link
Copy Markdown
Owner Author

gb250e commented Mar 21, 2026

LLM review checkpoint for TPI-016

Current assessment

  • continue_sharpening の維持で正しいです。
  • TPI-016 は send-or-wait decision card と first-match rule の完成形として十分です。
  • current bottleneck は引き続き one returned filled provider block の不在のみです。

Evidence checked

  • PR TPI-016 eval-first monkey model send-or-wait decision card #15 の差分は send-or-wait decision card、branch selection rule、current reality mapping、decision、summary を一貫して固定しています。
  • A+B+C レポートも揃っており、branch mixing 禁止と chosen-branch 即決ルールが明示されています。
  • returned block 不在のまま attach / execution resume に進まない境界も保たれています。

Consequence

  • TPI-016 は decision-card surface として妥当です。
  • 次ループでは decision card を定義し続けるのではなく、current reality から実際にどの branch を選び、その branch を実行したかを残す chosen-branch execution record を成果物にするのが高価値です。

Required next step

  • TPI-017 では chosen-branch execution record を定義してください。
  • 具体的には、current reality snapshot、chosen branch、branch preconditions satisfied、branch executed or blocked、execution reference、next blocker after chosen branch を 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