Purpose

This is the TPI-006 internal review PR.

TPI-005 showed that local auth readiness is partially satisfied, but the selected Runpod path still lacks the concrete provider-supplied endpoint metadata needed to attach to the pod from the current workspace. TPI-006 isolates that provider-metadata problem.

Thesis

For the selected Runpod Parameter Golf path, the next highest-value move is to obtain the concrete provider-supplied attach route (pod identifier, host or endpoint, exact command, username, port) that lands in /workspace/parameter-golf, without changing the existing eval-first monkey-model execution contract.

Scope

• keep the selected Runpod path
• keep the existing eval-first mechanism unchanged
• focus only on provider metadata / endpoint discovery
• preserve public-safe monkey model framing

What is included

• provider metadata plan
• endpoint contract template
• provider checklist
• metadata decision surface
• PR summary placeholder for the next update

What is intentionally not included yet

• new model mechanism
• tokenizer changes
• runtime / val_bpb evidence
• environment reselection

Expected next step

1. obtain the exact provider-supplied attach or SSH command
2. obtain the explicit pod identifier / endpoint / username / port
3. verify landing in /workspace/parameter-golf
4. resume the TPI-004 evidence pass unchanged

Public-facing safety

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