Document every archive's run settings, and which are superseded

README.md

@@ -13,201 +13,313 @@ evolved interface code, every agent trajectory, the builder logs, the evolution
 database, the run configuration, and derived result tables. Each archive is
 meant to be readable by someone with no access to the machine that produced it.
 
-## Which archive to take
-
-| file | size | contents |
-|---|---|---|
-| `archives/qwen_syn30v15_128k-redacted.zip` | 3.1 GB | everything, including the 270 raw `claude_trajectory.jsonl` agent transcripts |
-| `archives/qwen_syn30v15_128k-slim.zip` | 78 MB | byte-identical apart from those 270 transcripts, which are omitted |
-
-Take the slim archive to read results or redo analysis — all scores, code,
-configuration and derived tables are in it. Take the full one only to replay
-what the agent actually did, step by step.
-
-> **Credentials are redacted.** An OSWorld agent explores the VM it is given,
-> and one that runs `env` records the harness's API keys into its own
-> transcript. Every text file here has been passed through a redactor that
-> replaces such values with `<REDACTED>` while keeping the variable name, so
-> the record still shows what was present. For this run that rewrote 22
-> occurrences each of four provider keys plus 730 generic `*_TOKEN` /
-> `*_SECRET` assignments. Both archives were scanned before upload and contain
-> no credential-shaped strings.
+Three experiments are archived here. They differ in **exactly one intended
+variable each**, and the differences are listed before the numbers because most
+of the numbers are not comparable across them.
 
 ---
 
-# Archive structure
+# Which archive to take
 
-Every archive unpacks to one directory named `<namespace>-<UTC timestamp>/`.
-Sizes below are uncompressed, from the `qwen_syn30v15_128k` full archive
-(2,191 files).
+| file | size | contents | status |
+|---|---|---|---|
+| `archives/qwen_syn30v15_128k-step15-slim.zip` | 95 MiB | **no scratch VM**, 16 variants, steps 0–15 — scores, code, config, derived tables | **current** |
+| `archives/qwen_syn30v15_128k-step15-redacted.zip` | 13.8 GiB | the same plus all 5,630 raw agent transcripts | **current** |
+| `archives/qwen_syn30v15_128k_scratch-step10-slim.zip` | 94.9 MiB | **with scratch VM**, 11 complete variants | **current** |
+| `archives/qwen_syn30v15_128k_scratch-step10-redacted.zip` | 5.6 GiB | the same plus transcripts, **plus a partial 12th variant** (see below) | **current** |
+| `archives/qwen_syn30v15_128k-bare-redacted.zip` | 1.0 GiB | **no shadow interface at all** — the baseline floor | **current** |
+| `archives/qwen_syn30v15_128k-step12-redacted.zip` | 10.6 GiB | no scratch VM, steps 0–12 | superseded by `step15` |
+| `archives/qwen_syn30v15_128k-step12-slim.zip` | 96 MiB | no scratch VM, steps 0–12 | superseded by `step15` |
+| `archives/qwen_syn30v15_128k-redacted.zip` | 3.3 GiB | no scratch VM, steps 0–5 | superseded by `step15` |
+| `archives/qwen_syn30v15_128k-slim.zip` | 81 MiB | no scratch VM, steps 0–5 | superseded by `step15` |
+
+The four superseded archives are kept for link stability. `step15` is a strict
+superset of both `step12` and the unsuffixed pair — same namespace, same
+config, more steps. Take `step15` unless you need a byte-identical copy of what
+an earlier analysis read.
+
+Take a **slim** archive to read results or redo analysis: all scores, code,
+configuration and derived tables are in it. Take a **redacted** (full) archive
+only to replay what the agent actually did, step by step.
+
+### Integrity
 
 ```
-qwen_syn30v15_128k-20260920T005457Z/
-├── MANIFEST.json                8 KB    provenance and self-description
-├── config/                      6 KB    what was run
-├── db/                        204 KB    the evolution state
-├── results/                     2 KB    derived tables (read these first)
-├── interfaces/                 75 MB    the evolved code, per variant
-├── builder_logs/               25 MB    how each variant was written
-├── logs/                       26 KB    orchestrator console log
-└── trajectories/              5.9 GB    what the agent did, per variant per task
+5ccfa693ba3e37d2122e32f6fffe2d3eb0573d4623cdffc763132afcbc832b9f  qwen_syn30v15_128k-step15-redacted.zip
+3f97ecd726d0c38a61aa1b6d795c74c53a070594d865fdc484114617174c82a9  qwen_syn30v15_128k-step15-slim.zip
+bbc2b8258d64cda3c0167e826bf3c512f52fa99ec81dc837e3395a71676997f9  qwen_syn30v15_128k_scratch-step10-redacted.zip
+8a31ac3f19cd00d2668c1456f62fb92088135aea3ebc7b228fe67fe260209f38  qwen_syn30v15_128k_scratch-step10-slim.zip
+095c08ab479f0efaf1235db50186a693275369fe12e63698d0e4696d6d897c48  qwen_syn30v15_128k-bare-redacted.zip
 ```
 
-## `MANIFEST.json`
+> **Credentials are redacted.** An OSWorld agent explores the VM it is given,
+> and one that runs `env` records the harness's API keys into its own
+> transcript. This is not an occasional accident: grounding runs as a *tool*,
+> so the agent's model credentials are deliberately readable by any bash action
+> it takes. Every text file here has been passed through a redactor that
+> replaces such values with `<REDACTED>` while keeping the variable name. For
+> `step15` that rewrote 4,099 generic assignments, 2,367 Hugging Face tokens,
+> 109 Anthropic / 99 OpenRouter / 99 LiteLLM-proxy / 98 Parasail keys, and 55
+> private-key blocks or headers. Every archive was scanned before upload with a
+> detection list wider than what the redactor rewrites, and none contains a
+> credential-shaped string.
 
-The archive describing itself. Read this before anything else — it records how
-the archive was built, not just what it holds.
+---
 
-| key | meaning |
-|---|---|
-| `namespace`, `created_utc`, `eval_model` | which run, packaged when, scored by which model |
-| `variants` | 6 rows straight from the DB: `id`, `origin`, `step`, `parent_id`, `parent_b_id`, `score`, `val_score`, `tag` |
-| `val_task_ids` | the 15 graded task ids for this run |
-| `task_cap_seconds` | the per-task wall clock (7200) used to flag truncated runs |
-| `counts` | files written, split by kind |
-| `truncated_val_runs` | how many val runs hit the wall clock (22) |
-| `redacted`, `redactions` | whether redaction ran, and how many substitutions per rule |
-| `slim`, `recordings_included` | which variant of the archive this is |
-| `run_config` | the full launch configuration, 36 keys |
-| `layout`, `caveats` | a short version of this document |
+# The settings
 
-## `config/` — what was run
+All three runs share this. Deviations are called out per run.
 
-| file | contents |
+| | value |
 |---|---|
-| `run_config.json` | the orchestrator's launch record: full command line, builder/eval models and timeouts, scheduler spec, parent selection, VM concurrency, AWS region/subnet/security group, seed file SHA-256s |
-| `eval_sets/osworld_v2_val_15.json` | the 15 **graded** val task ids |
-| `eval_sets/synthetic_train_30.json` | the 30 synthetic train task ids — **ungraded**, see caveats |
-| `seed_context_compaction.json` | the seed's compaction policy: `context_window_tokens`, `reserve_tokens`, `keep_recent_tokens` |
+| harness | Prime Agent (`--builder-harness prime_agent`, `evaluator_harness=prime_agent`) |
+| builder model | `openai/simular-qwen-3p8-27b-evolving-agents` (self-hosted Qwen 3.8-27B) |
+| eval model | the same deployment — a variant is written and graded by one model |
+| **grounding model** | **also the same deployment.** The evaluator exports `SHADOW_GROUNDING_MODEL=<eval model>`, so the interface's UI-grounding helper calls the island's own model. There is no separate grounding model. (Earlier project runs used Parasail UI-TARS; `PARASAIL_API_KEY` survives in the tool allowlist.) |
+| context window | **131,072 (128K)**, declared in `shadow_interface/context_compaction.json` with `context_window_source = interface` |
+| train set | `synthetic_train_30.json` — 30 synthetic `s_*` tasks, **UNGRADED** |
+| val set | `osworld_v2_val_15.json` — 15 graded tasks: `007 010 014 019 041 046 048 058 064 069 072 079 083 105 108` |
+| selection signal | `val` |
+| parent selection | `tournament` |
+| scheduler | `deterministic:0,2,0` (alternating mutation / crossover) |
+| elimination count | 5 — **no elimination event was ever recorded**; every variant stays in the pool |
+| per-task wall clock | 7,200 s builder, 7,200 s eval |
+| max agent steps | 300 |
+| env concurrency | 45 |
+| region | `us-east-1`, public IP |
+| website deployment | `52.91.237.94.nip.io` — a **self-hosted substitute**, not the pinned `site.hku.icu` |
+| egress proxy | `allow_placeholder_proxy=1` — the proxy config holds placeholder credentials |
+
+### Two settings that bound what these numbers can support
+
+**The proxy is not configured.** With placeholder credentials, 6 train tasks
+(`037 055 062 075 098` and `056`) and 2 test tasks (`036 050`) fail for lack of
+an egress proxy. Those failures are indistinguishable from genuine interface
+failures, so they bias every selection step. The orchestrator says so itself on
+every launch: *"This run is a diagnostic, not a reportable result."*
+
+**The websites are a substitute stack.** 40 of the tasks are website-backed.
+Scores on them are comparable only to other runs on this same substitute
+deployment — not to any run measured against the pinned `site.hku.icu` host.
 
-## `db/` — the evolution state
+---
 
-`shadow_evolution_osworld_v2_<namespace>.db`, SQLite. Tables: `variants`
-(lineage and scores), `eval_results` (per variant per task), `cost_events`,
-`dispatch_log`, `history`, `islands`, `eval_sets`, `val_set`.
+# Run 1 — `qwen_syn30v15_128k`: no scratch VM
+
+`--no-scratch-vm`: the builder writes the interface without a VM to try it in.
+`--max-steps 30`, so **this archive is a mid-run snapshot at step 15**, not a
+finished run.
+
+16 variants. `val partial` is the summed raw score over the 15 val tasks;
+`val binary` counts only full credit.
+
+| step | variant | op | parent(s) | val partial | val binary |
+|---|---|---|---|---|---|
+| 0 | seed | — | — | 5.375 / 15 = 35.8% | 1/15 |
+| 1 | if-001 | mutation | seed | 5.851 / 15 = 39.0% | 1/15 |
+| 2 | if-002 | crossover | if-001 × seed | 5.540 / 15 = 36.9% | 1/15 |
+| 3 | if-003 | mutation | if-002 | 5.255 / 15 = 35.0% | 1/15 |
+| 4 | if-004 | crossover | if-002 × if-001 | 5.200 / 15 = 34.7% | 3/15 |
+| 5 | if-005 | mutation | seed | 4.575 / 15 = 30.5% | 3/15 |
+| 6 | if-006 | crossover | if-001 × seed | 5.600 / 15 = 37.3% | **4/15** |
+| 7 | if-007 | mutation | if-001 | 7.045 / 15 = 47.0% | 2/15 |
+| 8 | **if-008** | crossover | if-001 × seed | **7.180 / 15 = 47.9%** | 3/15 |
+| 9 | if-009 | mutation | if-008 | 6.070 / 15 = 40.5% | 3/15 |
+| 10 | if-010 | crossover | if-001 × if-009 | 5.965 / 15 = 39.8% | 3/15 |
+| 11 | if-011 | mutation | if-002 | 6.731 / 15 = 44.9% | **4/15** |
+| 12 | if-012 | crossover | if-001 × if-010 | 4.738 / 15 = 31.6% | 2/15 |
+| 13 | if-015 | mutation | if-012 | 5.607 / 15 = 37.4% | 3/15 |
+| 14 | if-016 | crossover | — | 6.645 / 15 = 44.3% | 3/15 |
+| 15 | if-017 | mutation | — | 6.673 / 15 = 44.5% | 3/15 |
+
+**`if-013` and `if-014` do not exist.** On 2026-09-22 an expired AWS SSO token
+made VM allocation fail for all 45 tasks of both variants. The harness wrote
+those retry-exhausted tasks as real `0.000` scores with
+`infrastructure_failed: 0`, so they entered the DB as legitimate worst-in-pool
+individuals. They were purged and the two steps re-dispatched; the `if-`
+counter did not rewind, so step 13/14/15 carry `if-015/016/017`.
+
+Other facts for this run: 5,630 trajectory files, 4,186 held-out files across
+101 held-out tasks / 671 runs / **42 rerun pairs**, and **65 of 240 val runs
+(27.1%) truncated** by the 2 h wall clock.
 
-```sql
-select id, origin, step, parent_id, parent_b_id, round(val_score,4)
-from variants order by rowid;
-```
+---
 
-## `results/` — derived tables
+# Run 2 — `qwen_syn30v15_128k_scratch`: with scratch VM
+
+Identical to Run 1 **except** that the scratch VM is enabled (the builder gets
+a VM to try the interface in while writing it) and `--max-steps 15`. Every
+other flag matches, which makes these two runs a clean A/B on the scratch VM.
+
+`dispatch_log` records steps 1–10 complete. The `variants` table holds only 6
+rows: **seed, if-003, if-008, if-009, if-010 and if-011 were evaluated but
+their DB rows never landed.** Their trajectories, git tags and builder logs are
+all present, so they are fully auditable; their lineage below was recovered
+from each tag's commit subject, and they are listed in
+`MANIFEST.json → db_orphan_variants`. Their `step` and `val_score` fields are
+empty in the DB-derived tables — the real scores are in
+`results/val_matrix.csv`, computed from `result.txt`.
+
+| step | variant | op | parent(s) | val partial | val binary | DB row |
+|---|---|---|---|---|---|---|
+| — | seed | — | — | 5.375 / 15 = 35.8% | 1/15 | missing |
+| 1 | if-001 | mutation | seed | 5.485 / 15 = 36.6% | 1/15 | ✅ |
+| 2 | if-002 | crossover | if-001 × seed | 6.125 / 15 = 40.8% | 3/15 | ✅ |
+| — | if-003 | mutation | if-001 | 4.375 / 15 = 29.2% | 1/15 | missing |
+| 4 | if-004 | crossover | if-001 × seed | 6.561 / 15 = 43.7% | 3/15 | ✅ |
+| 5 | if-005 | mutation | if-004 | 5.790 / 15 = 38.6% | **4/15** | ✅ |
+| 6 | if-006 | crossover | if-001 × if-004 | 6.220 / 15 = 41.5% | 3/15 | ✅ |
+| 7 | **if-007** | mutation | if-001 | **7.197 / 15 = 48.0%** | 3/15 | ✅ |
+| — | if-008 | crossover | if-005 × if-007 | 5.050 / 15 = 33.7% | **0/15** | missing |
+| — | if-009 | mutation | if-006 | 4.895 / 15 = 32.6% | 1/15 | missing |
+| — | if-010 | crossover | if-005 × if-002 | 5.150 / 15 = 34.3% | 2/15 | missing |
+
+There is no step 3 row in `dispatch_log`'s variant output either; `if-003` is
+the step-3 child.
+
+### The full archive holds one extra, incomplete variant
+
+`qwen_syn30v15_128k_scratch-step10-redacted.zip` contains a **12th** variant,
+`if-011`, with only **2 of 45** `result.txt` files. It appeared on disk between
+the slim and full packaging runs and was picked up mid-evaluation. **Do not read
+it as a result.** The slim archive holds the 11 complete variants only. The
+archive name reflects the last completed dispatch step (10).
+
+Other facts: 3,932 trajectory files, 458 held-out files across 52 tasks / 133
+runs / 0 rerun pairs, and **37 val runs truncated**.
 
-Generated at packaging time from the trajectories, so they agree with the raw
-files by construction.
+---
 
-**`val_matrix.csv`** — 15 rows, one per val task, one column per variant:
+# Run 3 — `qwen_syn30v15_128k-bare`: no shadow interface
 
-```
-task,…-seed,…-if-001,…-if-002,…-if-003,…-if-004,…-if-005
-007,0.6,0.6,0.6,0.6,0.6,0.4
-```
+The floor the whole experiment is measured against. Prime Agent with **nothing
+deployed to the VM**: no shadow interface, no `setup.sh`, no eval constraints,
+and the stock `NO_TOOL_SYSTEM_PROMPT` instead of `TOOL_SYSTEM_PROMPT`.
+
+Three consequences:
 
-**`variants.csv`** — 6 rows, the lineage and final scores:
+1. `--no_tool` moves the action space, and with it the output directory, to
+   `shadow_eval_no_tool/`. A reader that hardcodes the `shadow_eval/` prefix
+   reports this run as empty.
+2. The leak guard is off. A baseline has no training set to leak from, and the
+   point is to cover `val_15` too, so the number is comparable to the 108-task
+   denominator.
+3. **The proxy is off** for this run, unlike Runs 1 and 2 — the orchestrator is
+   already in the US, and a controlled probe showed the proxy changes no score
+   while placeholder credentials only force failures.
 
 ```
-id,origin,step,parent_id,parent_b_id,score,val_score
-qwen_syn30v15_128k-seed,seed,0,,,0.0,5.375
+108 held-out tasks | 190 runs | 6 rerun pairs | 935 files
+115 runs carry a score: mean 0.3845, 17 at full credit
 ```
 
-**`truncated_runs.csv`** — 22 rows. **Read this before interpreting any zero.**
+Batches: `osworld_v2_full_108` (55), `osworld_v2_bare_remaining` (92),
+`osworld_v2_bare_imputed_rerun` (1), and `_aborted_hku` (42 — an abandoned
+attempt against the pinned host, kept and prefixed).
 
-```
-variant,task,exit,elapsed_s,score
-qwen_syn30v15_128k-seed,064,0,10929.3,0.0
-```
+**Read this before claiming the evolution works.** The bare floor's partial
+mean of 0.3845 sits inside the 0.29–0.48 band that every evolved variant in
+Runs 1 and 2 occupies. The task sets and denominators differ, so this is not a
+head-to-head — but `results/heldout_matrix.csv` now carries a bare column, and
+aligning on the shared tasks is the comparison that decides whether an evolved
+interface beats having no interface at all.
 
-## `interfaces/` — the evolved code
+---
 
-```
-interfaces/
-├── <namespace>-<timestamp>.bundle          75 MB   git bundle, all 6 variant tags
-├── qwen_syn30v15_128k-seed/shadow_interface/
-│   ├── __init__.py  __main__.py  cli.py  setup.sh
-│   ├── context_compaction.json
-│   └── helpers/{__init__,atree,browser,cli_ops,gui}.py
-├── qwen_syn30v15_128k-if-001/shadow_interface/…
-└── … if-002 … if-005
-```
+# Archive structure
 
-The per-variant directories are flat snapshots, convenient for reading or
-diffing. The **bundle** is the authoritative copy: it carries every tag *and*
-the commit graph, so it shows how each variant was derived from its parent,
-which the snapshots cannot.
+Every archive unpacks to one directory named `<namespace>-<UTC timestamp>/`.
 
-```bash
-git clone -b evol <namespace>-<timestamp>.bundle evolved
-cd evolved && git log --oneline --graph --all
-git diff evol/<ns>/seed evol/<ns>/if-001 -- shadow_interface
+```
+<namespace>-<timestamp>/
+├── MANIFEST.json            provenance and self-description — read this first
+├── config/                  what was run
+├── db/                      the evolution SQLite database
+├── results/                 derived tables (read these second)
+├── interfaces/              the evolved code, per variant, plus a git bundle
+├── builder_logs/            one JSONL per builder invocation
+├── logs/console.log         the orchestrator's own output
+├── trajectories/            <variant>/<task>/ — val + synthetic-train runs
+└── trajectories_heldout/    <variant>/<task>/<eval set>__<stamp>/ — held-out runs
 ```
 
-## `builder_logs/` — how each variant was written
-
-One JSONL per builder invocation, named `<variant>_<operation>.jsonl`:
+## `MANIFEST.json`
 
-| file | size |
+| key | meaning |
 |---|---|
-| `…-if-001_mutation.jsonl` | 5.9 MB |
-| `…-if-002_crossover.jsonl` | 5.5 MB |
-| `…-if-003_mutation.jsonl` | 4.8 MB |
-| `…-if-004_crossover.jsonl` | 2.4 MB |
-| `…-if-005_mutation.jsonl` | 6.1 MB |
+| `namespace`, `created_utc`, `eval_model` | which run, packaged when, scored by which model |
+| `variants` | rows from the DB: `id`, `origin`, `step`, `parent_id`, `parent_b_id`, `score`, `val_score`, `tag` |
+| `db_orphan_variants` | variants archived from disk that have **no DB row** (Run 2) |
+| `val_task_ids` | the 15 graded task ids |
+| `task_cap_seconds` | the per-task wall clock (7200) used to flag truncated runs |
+| `truncated_val_runs` | how many val runs hit that wall clock |
+| `held_out_tasks` / `_runs` / `_rerun_pairs` | held-out coverage; rerun pairs are the only direct measure of harness noise here |
+| `redacted`, `redactions` | whether redaction ran, and how many substitutions per rule |
+| `slim`, `recordings_included` | which variant of the archive this is |
+| `run_config` | the full launch configuration |
 
-Same event schema as the agent trajectories below. The seed has no builder log
-— it was not built by anything.
+## `config/`
 
-## `logs/`
+`run_config.json` (full command line, models, timeouts, scheduler, parent
+selection, concurrency, AWS region/subnet/security group, seed SHA-256s),
+`eval_sets/osworld_v2_val_15.json`, `eval_sets/synthetic_train_30.json`, and
+`seed_context_compaction.json` (`context_window_tokens`, `reserve_tokens`,
+`keep_recent_tokens`).
 
-`console.log` — the orchestrator's own output: step dispatches, parent
-selection (`Selected … via tournament`), builder start/finish, per-variant
-`scored X/30 (val: Y/15)` lines, and the final `Driver stopping at step=N`.
+## `db/`
 
-## `trajectories/` — what the agent did
+`shadow_evolution_osworld_v2_<namespace>.db`, SQLite. Tables: `variants`,
+`eval_results` (per variant per task), `cost_events`, `dispatch_log`,
+`history`, `islands`, `eval_sets`, `val_set`.
 
-```
-trajectories/<variant>/<task>/
+```sql
+select id, origin, step, parent_id, parent_b_id, round(val_score,4)
+from variants order by rowid;
 ```
 
-6 variants × 45 tasks = 270 task directories. The 45 tasks are the 15 graded
-val ids (`007 010 014 019 041 046 048 058 064 069 072 079 083 105 108`) and 30
-synthetic `s_001`…`s_030`.
-
-| file | present | contents |
-|---|---|---|
-| `claude_trajectory.jsonl` | 270 | **the raw agent transcript** — omitted from the slim archive |
-| `result.txt` | 270 | the final score, one float |
-| `env_spec.json` | 270 | the VM spec the task ran on |
-| `instruction.txt` | 267 | the task prompt as given to the agent |
-| `traj.jsonl` | 267 | one-line run summary (below) |
-| `claude_stderr.log` | 264 | agent stderr |
-| `exit_code.txt` | 264 | process exit code — **124 means the wall clock killed it** |
-| `result.json` | 216 | grading detail, including safety checks |
-| `phase_results.json` | 6 | per-phase scores for multi-phase tasks |
-| `exit_code_phase_N.txt` | 6/6/3/2 | per-phase exit codes; these tasks have no single `exit_code.txt` |
-| `failure.json` | 3 | infra failure record — see caveats |
-
-**`traj.jsonl`** — a single JSON object summarising the run:
+`eval_sets` is empty in these runs — that table was never written; the task
+sets live in `val_set` and in `config/eval_sets/`.
 
-```json
-{"agent": "shadow_eval", "model": "openai/simular-qwen-3p8-27b-evolving-agents",
- "instruction": "…", "elapsed_seconds": 2148.36, "no_tool": false,
- "phase_count": 1, "hitl_turns": 0}
+## `results/`
+
+Generated at packaging time from the trajectories, so they agree with the raw
+files by construction.
+
+| file | contents |
+|---|---|
+| `val_matrix.csv` | 15 rows, one per val task, one column per variant |
+| `variants.csv` | lineage and final scores |
+| `truncated_runs.csv` | **read this before interpreting any zero** |
+| `heldout_runs.csv` | one row per (variant, run, task) — reruns included |
+| `heldout_matrix.csv` | each task resolved to one score per variant, latest run wins |
+| `heldout_reruns.csv` | tasks run more than once, with `abs_delta` |
+
+## `interfaces/`
+
+A git bundle carrying every variant tag **and the commit graph**, plus flat
+per-variant snapshots of `shadow_interface/`. The bundle is authoritative — it
+shows how each variant was derived from its parent, which the snapshots cannot.
+
+```bash
+git init evolved && cd evolved
+git fetch ../<namespace>-<timestamp>.bundle 'refs/tags/*:refs/tags/*'
+git log --oneline --graph --all
+git diff evol/<ns>/seed evol/<ns>/if-001 -- shadow_interface
 ```
 
-`elapsed_seconds` is the agent's own clock, started after the VM was ready.
-`hitl_turns` counts ASK_USER round trips with the simulated user.
+The bundles here record a complete history, including the upstream OSWorld
+commits the seed was cut from.
 
-**`claude_trajectory.jsonl`** — one JSON event per line, in order. Event types
-in a typical 128-turn episode:
+## `trajectories/` and `trajectories_heldout/`
 
-| `type` | count | meaning |
-|---|---|---|
-| `session` / `agent_start` / `agent_end` | 1 each | episode framing; `agent_end` carries the full message list |
-| `turn_start` / `turn_end` | 128 each | one model turn — **counting `turn_start` gives the step count** |
-| `message_start` / `message_end` | 257 each | streaming boundaries |
-| `tool_execution_start` / `_update` / `_end` | 128 / 1314 / 128 | tool calls and their incremental output |
+Each task directory holds `result.txt` (the score, one float), `result.json`
+(grading detail including safety checks), `traj.jsonl` (one-line run summary
+with `elapsed_seconds`, `hitl_turns`), `claude_trajectory.jsonl` (**the raw
+transcript** — omitted from slim archives), `claude_stderr.log`,
+`exit_code.txt` (**124 means the wall clock killed it**), `instruction.txt`,
+`env_spec.json`, and sometimes `phase_results.json` or `failure.json`.
 
-Token accounting lives on `turn_end`:
+Token accounting lives on each `turn_end` event:
 
 ```json
 {"input": 5179, "output": 137, "cacheRead": 0, "cacheWrite": 0,
@@ -215,85 +327,58 @@ Token accounting lives on `turn_end`:
 ```
 
 `cost` is zero throughout: the model is a self-hosted deployment that declares
-zero per-token price. That is structural, not a measurement gap. Summing
-`totalTokens` over turns gives a cumulative billing-style figure — each turn
-re-counts the whole growing prompt.
-
-**`result.json`** — grading detail, richer than the bare `result.txt`:
-
-```json
-{"score": 1.0,
- "safety": {"checks": [{"name": "document_integrity", "result": "PASS",
-                        "penalty": 0.0}],
-            "total_penalty": 0.0}}
-```
+zero per-token price. That is structural, not a measurement gap. Counting
+`turn_start` events gives the step count.
 
-**`failure.json`** — written when an attempt failed on infrastructure:
-`task_id`, `attempt` / `max_attempts`, `failure_type`, `error`, `status`, and
-`valid_for_fitness` (false — the harness excludes these from scoring). A
-`failure.json` **next to a `result.txt`** means a later retry succeeded and the
-failure record is stale; only a `failure.json` with **no** `result.txt` is a
+A `failure.json` **next to a `result.txt`** means a later retry succeeded and
+the failure record is stale; only a `failure.json` with **no** `result.txt` is a
 real gap.
 
 ---
 
 # Caveats
 
-Three things are easy to read wrong. All three are also recorded in
-`MANIFEST.json`.
+Beyond the two setting-level limits above, five things are easy to read wrong.
+All are recorded in `MANIFEST.json`.
+
+**1. Synthetic `s_*` tasks are UNGRADED** — constant zero by construction,
+`verification: dummy_constant_zero`. Their `result.txt` is always `0.0`, so the
+`train` score is `0.000` for every variant in Runs 1 and 2 and carries no
+information. Only the 15 val ids are graded, and the denominator is the full
+val set even when fewer finished.
 
-**1. A truncated run is not a capability zero.** A task cut off by the 2 h
+**2. A truncated run is not a capability zero.** A task cut off by the 2 h
 per-task wall clock exits **124** (or reports `elapsed_seconds` above 7200),
 writes a **real score** — almost always `0.000` — and writes **no
-`failure.json`**, so infra-failure checks cannot see it. In this run **22 of 90
-val runs (24%)** were truncated, concentrated on tasks `064` and `108` (all six
-variants), `079` (five), and `083`/`058`/`014`/`048`. A zero on those means
-"was not allowed to finish", not "cannot do it". `results/truncated_runs.csv`
-lists every one.
-
-**2. The seed ran on a different clock.** Its results were imported from a
-standalone evaluation that used `--no-time-limit`, while `if-001`…`if-005` ran
-under `--eval-timeout 7200`. The seed's `064` ran 10,929 s and its `108` ran
-8,381 s without being cut. Both still scored 0.000, so its total is unaffected,
-but the seed row is not comparable to its children on the truncation axis.
-
-**3. Synthetic `s_*` tasks are UNGRADED**, constant zero by construction. Their
-`result.txt` is always `0.0` and carries no signal; a `train` score of 0.000 is
-expected. Only the 15 val ids are graded, and the denominator is the full val
-set even when fewer tasks finished.
+`failure.json`**, so infra-failure checks cannot see it. 27.1% of Run 1's val
+runs were truncated. `results/truncated_runs.csv` lists every one.
+
+**3. The context window is inside the evolvable interface.** Because
+`context_window_tokens` lives in `shadow_interface/context_compaction.json` and
+that file is listed as evolvable, **a child variant can change its own context
+window.** Neither run is a fixed-window single-variable experiment.
+
+**4. The seed was not re-evaluated.** Its 45 task directories were copied in
+from two earlier 128K runs rather than measured again, so the seed row is not
+comparable to its children on the truncation axis. Both runs' seeds report the
+same 5.375, which is that same cached measurement.
+
+**5. `val` at n=1 cannot resolve this ladder.** Each variant's fitness is one
+run of 15 tasks. Across this project's earlier runs the spread between repeated
+evaluations of the *same* parent pair reached 1.64 points on the same 15-task
+scale — wider than most of the gaps in the tables above. Independent evidence:
+in the project's `prime25v15r4` run, the two variants that also received a
+68-task held-out evaluation ranked **in the opposite order** on the larger set
+(`if-006` 62.4% vs `if-008` 51.7%) from how they ranked on `val_15`. Treat
+single-variant val differences here as noise unless a held-out set confirms
+them.
 
 ---
 
-# Runs
-
-## `qwen_syn30v15_128k` — 5 evolution steps at a 128K context window
-
-Qwen 3.8-27B as both builder and evaluator, Prime Agent harness, 45 tasks per
-variant, 45-VM concurrency, 2 h per-task wall clock. 16.5 h wall clock, 270
-episodes, clean exit. Compaction was healthy throughout: 290 compactions, **0
-skipped**, at a 131,072-token window with `keep_recent_tokens = 20000`.
+# Adding a run to this repo
 
-| variant | op | parent(s) | val partial | val binary |
-|---|---|---|---|---|
-| seed | — | — | 5.3750 / 15 = 35.83% | 1/15 |
-| **if-001** | mutation | seed | **5.8508 / 15 = 39.01%** | 1/15 |
-| if-002 | crossover | if-001 × seed | 5.5400 / 15 = 36.93% | 1/15 |
-| if-003 | mutation | if-002 | 5.2550 / 15 = 35.03% | 1/15 |
-| if-004 | crossover | if-002 × if-001 | 5.2001 / 15 = 34.67% | **3/15** |
-| if-005 | mutation | seed | 4.5750 / 15 = 30.50% | **3/15** |
-
-`val partial` is the mean raw score over the 15 val tasks; `val binary` counts
-only full credit. The two disagree: **if-001** leads on partial, while
-**if-004** and **if-005** each solve three tasks outright against everyone
-else's one.
-
-Capabilities the evolution opened that the seed did not have:
-
-| task | best before | opened by | new score |
-|---|---|---|---|
-| 010 | 0.000 (all five others) | if-005 | **1.000** |
-| 105 | 0.350 (four variants tied) | if-004 | 0.970 |
-| 069 | 0.871 | if-004 | 1.000 |
-| 046 | 0.990 | if-004 | 1.000 |
-| 079 | 0.000 | if-002 | 0.220 |
-| 058 | 0.000 | if-004 | 0.100 |
+The archives are produced by the `evo-archive` skill in the source repository:
+`package_experiment.py` builds the zip from an allowlist of filenames (never a
+directory sweep) with redaction on by default, and `upload_experiment.py`
+scans the result and refuses to upload if it finds a credential shape.
+Archives are keyed by namespace and name, so adding one overwrites nothing.