TPI-005 eval-first monkey model attachability pass

notes/pr4_update_summary.md

@@ -0,0 +1,23 @@
+# PR #4 Update Summary
+
+## What this PR adds
+
+- an attachability plan for the selected Runpod path
+- a partially concretized attach contract
+- a handoff checklist for the missing pod-access data
+- an access decision note that records what is now known vs still missing
+
+## What still remains
+
+- actual pod identifier / endpoint
+- actual attach or SSH command
+- verified landing path in `/workspace/parameter-golf`
+- resumption of the TPI-004 baseline/candidate evidence pass
+
+## First required handoff
+
+The next turn should begin with the concrete pod attach route (or SSH invocation) that lands in the selected Runpod environment.
+
+## Review state
+
+- review comments: none observed during this turn

notes/tpi_005_access_decision.md

@@ -0,0 +1,53 @@
+# TPI-005 Access Decision
+
+## Concrete handoff information obtained
+
+- Windows-side SSH key material exists:
+  - `/mnt/c/Users/eb245/.ssh/id_ed25519`
+  - `/mnt/c/Users/eb245/.ssh/id_rsa`
+- generic SSH client exists at `/usr/bin/ssh`
+- expected landing path remains `/workspace/parameter-golf`
+- first verification command set is fixed
+
+## Still missing
+
+- pod identifier or display name
+- exact attach command or SSH command
+- hostname / endpoint
+- username
+- port if non-default
+
+## Attachability status
+
+- `partial`
+
+## Interpretation
+
+- Auth preconditions are now less ambiguous because a concrete SSH key source exists.
+- Attachability is not confirmed because no endpoint or provider-specific command was found.
+- TPI-004 cannot be resumed yet from this workspace.
+
+## Can TPI-004 resume now?
+
+- No
+
+## First command once handoff is supplied
+
+```bash
+ssh -i /mnt/c/Users/eb245/.ssh/id_ed25519 <user>@<host> -p <port>
+```
+
+## First verification commands after attach
+
+```bash
+pwd
+ls /workspace
+cd /workspace/parameter-golf
+git rev-parse --abbrev-ref HEAD
+python3 -c "import torch, datasets, sentencepiece; print('deps-ok')"
+nvidia-smi
+```
+
+## Sharp blocker
+
+- The remaining blocker is missing pod-specific connection metadata, not missing local auth material.

notes/tpi_005_attach_contract.md

@@ -0,0 +1,64 @@
+# TPI-005 Attach Contract
+
+## Objective
+
+Describe the minimum reusable attach route needed to resume the TPI-004 Runpod evidence pass unchanged.
+
+## Required fields
+
+- pod identifier or pod display name: not yet obtained
+- SSH hostname or console attach route: not yet obtained
+- username: not yet obtained
+- port (if non-default): not yet obtained
+- expected landing path: `/workspace/parameter-golf`
+- auth material source: Windows-side SSH keys are present at `/mnt/c/Users/eb245/.ssh/`
+
+## Minimum attach command template
+
+```bash
+ssh -i /mnt/c/Users/eb245/.ssh/id_ed25519 <user>@<host> -p <port>
+```
+
+or the exact provider-specific attach command that lands in the pod shell.
+
+## Current concrete data
+
+- concrete auth material source exists:
+  - `/mnt/c/Users/eb245/.ssh/id_ed25519`
+  - `/mnt/c/Users/eb245/.ssh/id_rsa`
+- generic SSH client exists at `/usr/bin/ssh`
+- no SSH config file was present
+- no pod endpoint or saved attach command was found
+
+## Expected landing path
+
+Preferred:
+
+```bash
+/workspace/parameter-golf
+```
+
+If the attach route lands elsewhere, record the exact correction steps needed to reach the repo.
+
+## First verification commands
+
+```bash
+pwd
+ls /workspace
+cd /workspace/parameter-golf
+git rev-parse --abbrev-ref HEAD
+python3 -c "import torch, datasets, sentencepiece; print('deps-ok')"
+nvidia-smi
+```
+
+## Attach failure fallback
+
+- if direct SSH command is still missing, require one of:
+  - exact Runpod SSH command
+  - console attach route with pod identifier
+  - hostname/username/port tuple
+- until one of those is supplied, attachability remains partial rather than confirmed
+
+## Resume condition
+
+Once the attach route and first verification commands are known, the branch is ready to resume the TPI-004 baseline/candidate evidence pass without changing the eval-first monkey-model contract.

notes/tpi_005_attachability_plan.md

@@ -0,0 +1,37 @@
+# TPI-005 Attachability Plan
+
+## Objective
+
+Secure a concrete pod attach / SSH handoff for the selected Runpod path so that the existing eval-first monkey-model evidence pass can resume unchanged.
+
+## Public-facing name
+
+`MonkeyModel_EvalFirst_AttachabilityPass`
+
+## Required handoff data
+
+- pod identifier or endpoint
+- exact attach or SSH command
+- expected landing path (`/workspace/parameter-golf` or corrected equivalent)
+- auth preconditions (SSH key, token, console step, etc.)
+- first verification commands after attach
+
+## First checks after attach
+
+1. `pwd`
+2. `ls /workspace`
+3. `cd /workspace/parameter-golf`
+4. `git rev-parse --abbrev-ref HEAD`
+5. `python3 -c "import torch, datasets, sentencepiece; print('deps-ok')"`
+6. `nvidia-smi`
+
+## Success condition
+
+The attach route is concrete enough that a future turn can resume the TPI-004 baseline/candidate evidence pass without re-opening the environment-selection debate.
+
+## Non-goals
+
+- no model changes
+- no tokenizer changes
+- no environment reselection
+- no score claims

notes/tpi_005_handoff_checklist.md

@@ -0,0 +1,33 @@
+# TPI-005 Handoff Checklist
+
+## Goal
+
+Obtain the minimum reusable information needed to attach to the selected Runpod pod and resume the TPI-004 evidence pass unchanged.
+
+## Required handoff items
+
+- [ ] pod identifier or pod name
+- [ ] attach command or SSH command
+- [ ] hostname / endpoint
+- [ ] username
+- [ ] port (if needed)
+- [x] auth source (Windows-side SSH keys found at `/mnt/c/Users/eb245/.ssh/`)
+- [x] expected landing path
+- [x] first verification commands after attach
+
+## Unfilled items and why
+
+- pod identifier / pod name: no Runpod metadata was present in the workspace or PR body
+- attach command / SSH command: no saved command was found in shell history or config
+- hostname / endpoint: not present in local environment or known hosts
+- username / port: depend on the missing endpoint or provider command
+
+## Acceptance rule
+
+TPI-005 is successful only if a future turn can start with the concrete attach route rather than re-deriving access details.
+
+## Resume target
+
+After attach succeeds, the next turn should resume:
+- baseline run with `EVAL_STRIDE=1024`
+- candidate run with `EVAL_STRIDE=128`

runs/TPI-004/run_notes.md

@@ -35,12 +35,14 @@ Capture one real baseline/candidate evidence pair in the selected Runpod Paramet
 ## Runpod access checks
 
 - `~/.ssh`: not present
+- Windows-side SSH keys: present under `/mnt/c/Users/eb245/.ssh/`
 - Runpod-related environment variables: none observed
 - Runpod CLI helpers: none observed
 - generic SSH client: present at `/usr/bin/ssh`
 - `/workspace`: not present locally
 - `/workspace/parameter-golf`: not present locally
 - saved attach command in shell history: none observed
+- Windows PowerShell history: GitHub SSH tests present, but no Runpod endpoint or attach command found
 
 ## Baseline contract for the next runnable attempt