agent-s4 0.1.0__tar.gz

agent_s4-0.1.0/LICENSE

@@ -0,0 +1,201 @@
+                                 Apache License
+                           Version 2.0, January 2004
+                        http://www.apache.org/licenses/
+
+   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+   1. Definitions.
+
+      "License" shall mean the terms and conditions for use, reproduction,
+      and distribution as defined by Sections 1 through 9 of this document.
+
+      "Licensor" shall mean the copyright owner or entity authorized by
+      the copyright owner that is granting the License.
+
+      "Legal Entity" shall mean the union of the acting entity and all
+      other entities that control, are controlled by, or are under common
+      control with that entity. For the purposes of this definition,
+      "control" means (i) the power, direct or indirect, to cause the
+      direction or management of such entity, whether by contract or
+      otherwise, or (ii) ownership of fifty percent (50%) or more of the
+      outstanding shares, or (iii) beneficial ownership of such entity.
+
+      "You" (or "Your") shall mean an individual or Legal Entity
+      exercising permissions granted by this License.
+
+      "Source" form shall mean the preferred form for making modifications,
+      including but not limited to software source code, documentation
+      source, and configuration files.
+
+      "Object" form shall mean any form resulting from mechanical
+      transformation or translation of a Source form, including but
+      not limited to compiled object code, generated documentation,
+      and conversions to other media types.
+
+      "Work" shall mean the work of authorship, whether in Source or
+      Object form, made available under the License, as indicated by a
+      copyright notice that is included in or attached to the work
+      (an example is provided in the Appendix below).
+
+      "Derivative Works" shall mean any work, whether in Source or Object
+      form, that is based on (or derived from) the Work and for which the
+      editorial revisions, annotations, elaborations, or other modifications
+      represent, as a whole, an original work of authorship. For the purposes
+      of this License, Derivative Works shall not include works that remain
+      separable from, or merely link (or bind by name) to the interfaces of,
+      the Work and Derivative Works thereof.
+
+      "Contribution" shall mean any work of authorship, including
+      the original version of the Work and any modifications or additions
+      to that Work or Derivative Works thereof, that is intentionally
+      submitted to Licensor for inclusion in the Work by the copyright owner
+      or by an individual or Legal Entity authorized to submit on behalf of
+      the copyright owner. For the purposes of this definition, "submitted"
+      means any form of electronic, verbal, or written communication sent
+      to the Licensor or its representatives, including but not limited to
+      communication on electronic mailing lists, source code control systems,
+      and issue tracking systems that are managed by, or on behalf of, the
+      Licensor for the purpose of discussing and improving the Work, but
+      excluding communication that is conspicuously marked or otherwise
+      designated in writing by the copyright owner as "Not a Contribution."
+
+      "Contributor" shall mean Licensor and any individual or Legal Entity
+      on behalf of whom a Contribution has been received by Licensor and
+      subsequently incorporated within the Work.
+
+   2. Grant of Copyright License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      copyright license to reproduce, prepare Derivative Works of,
+      publicly display, publicly perform, sublicense, and distribute the
+      Work and such Derivative Works in Source or Object form.
+
+   3. Grant of Patent License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      (except as stated in this section) patent license to make, have made,
+      use, offer to sell, sell, import, and otherwise transfer the Work,
+      where such license applies only to those patent claims licensable
+      by such Contributor that are necessarily infringed by their
+      Contribution(s) alone or by combination of their Contribution(s)
+      with the Work to which such Contribution(s) was submitted. If You
+      institute patent litigation against any entity (including a
+      cross-claim or counterclaim in a lawsuit) alleging that the Work
+      or a Contribution incorporated within the Work constitutes direct
+      or contributory patent infringement, then any patent licenses
+      granted to You under this License for that Work shall terminate
+      as of the date such litigation is filed.
+
+   4. Redistribution. You may reproduce and distribute copies of the
+      Work or Derivative Works thereof in any medium, with or without
+      modifications, and in Source or Object form, provided that You
+      meet the following conditions:
+
+      (a) You must give any other recipients of the Work or
+          Derivative Works a copy of this License; and
+
+      (b) You must cause any modified files to carry prominent notices
+          stating that You changed the files; and
+
+      (c) You must retain, in the Source form of any Derivative Works
+          that You distribute, all copyright, patent, trademark, and
+          attribution notices from the Source form of the Work,
+          excluding those notices that do not pertain to any part of
+          the Derivative Works; and
+
+      (d) If the Work includes a "NOTICE" text file as part of its
+          distribution, then any Derivative Works that You distribute must
+          include a readable copy of the attribution notices contained
+          within such NOTICE file, excluding those notices that do not
+          pertain to any part of the Derivative Works, in at least one
+          of the following places: within a NOTICE text file distributed
+          as part of the Derivative Works; within the Source form or
+          documentation, if provided along with the Derivative Works; or,
+          within a display generated by the Derivative Works, if and
+          wherever such third-party notices normally appear. The contents
+          of the NOTICE file are for informational purposes only and
+          do not modify the License. You may add Your own attribution
+          notices within Derivative Works that You distribute, alongside
+          or as an addendum to the NOTICE text from the Work, provided
+          that such additional attribution notices cannot be construed
+          as modifying the License.
+
+      You may add Your own copyright statement to Your modifications and
+      may provide additional or different license terms and conditions
+      for use, reproduction, or distribution of Your modifications, or
+      for any such Derivative Works as a whole, provided Your use,
+      reproduction, and distribution of the Work otherwise complies with
+      the conditions stated in this License.
+
+   5. Submission of Contributions. Unless You explicitly state otherwise,
+      any Contribution intentionally submitted for inclusion in the Work
+      by You to the Licensor shall be under the terms and conditions of
+      this License, without any additional terms or conditions.
+      Notwithstanding the above, nothing herein shall supersede or modify
+      the terms of any separate license agreement you may have executed
+      with Licensor regarding such Contributions.
+
+   6. Trademarks. This License does not grant permission to use the trade
+      names, trademarks, service marks, or product names of the Licensor,
+      except as required for reasonable and customary use in describing the
+      origin of the Work and reproducing the content of the NOTICE file.
+
+   7. Disclaimer of Warranty. Unless required by applicable law or
+      agreed to in writing, Licensor provides the Work (and each
+      Contributor provides its Contributions) on an "AS IS" BASIS,
+      WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+      implied, including, without limitation, any warranties or conditions
+      of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
+      PARTICULAR PURPOSE. You are solely responsible for determining the
+      appropriateness of using or redistributing the Work and assume any
+      risks associated with Your exercise of permissions under this License.
+
+   8. Limitation of Liability. In no event and under no legal theory,
+      whether in tort (including negligence), contract, or otherwise,
+      unless required by applicable law (such as deliberate and grossly
+      negligent acts) or agreed to in writing, shall any Contributor be
+      liable to You for damages, including any direct, indirect, special,
+      incidental, or consequential damages of any character arising as a
+      result of this License or out of the use or inability to use the
+      Work (including but not limited to damages for loss of goodwill,
+      work stoppage, computer failure or malfunction, or any and all
+      other commercial damages or losses), even if such Contributor
+      has been advised of the possibility of such damages.
+
+   9. Accepting Warranty or Additional Liability. While redistributing
+      the Work or Derivative Works thereof, You may choose to offer,
+      and charge a fee for, acceptance of support, warranty, indemnity,
+      or other liability obligations and/or rights consistent with this
+      License. However, in accepting such obligations, You may act only
+      on Your own behalf and on Your sole responsibility, not on behalf
+      of any other Contributor, and only if You agree to indemnify,
+      defend, and hold each Contributor harmless for any liability
+      incurred by, or claims asserted against, such Contributor by reason
+      of your accepting any such warranty or additional liability.
+
+   END OF TERMS AND CONDITIONS
+
+   APPENDIX: How to apply the Apache License to your work.
+
+      To apply the Apache License to your work, attach the following
+      boilerplate notice, with the fields enclosed by brackets "[]"
+      replaced with your own identifying information. (Don't include
+      the brackets!)  The text should be enclosed in the appropriate
+      comment syntax for the file format. We also recommend that a
+      file or class name and description of purpose be included on the
+      same "printed page" as the copyright notice for easier
+      identification within third-party archives.
+
+   Copyright [yyyy] [name of copyright owner]
+
+   Licensed under the Apache License, Version 2.0 (the "License");
+   you may not use this file except in compliance with the License.
+   You may obtain a copy of the License at
+
+       http://www.apache.org/licenses/LICENSE-2.0
+
+   Unless required by applicable law or agreed to in writing, software
+   distributed under the License is distributed on an "AS IS" BASIS,
+   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+   See the License for the specific language governing permissions and
+   limitations under the License.

agent_s4-0.1.0/PKG-INFO

@@ -0,0 +1,182 @@
+Metadata-Version: 2.4
+Name: agent-s4
+Version: 0.1.0
+Summary: Agent S4: evolving tool interfaces for computer-use agents
+Author: Simular AI
+License-Expression: Apache-2.0
+Project-URL: Source, https://github.com/simular-ai/Agent-S
+Project-URL: Paper, https://arxiv.org/abs/2610.28601
+Project-URL: Issues, https://github.com/simular-ai/Agent-S/issues
+Keywords: ai,llm,agent,computer-use,evolution
+Classifier: Programming Language :: Python :: 3
+Classifier: Programming Language :: Python :: 3.12
+Classifier: Operating System :: POSIX :: Linux
+Classifier: Topic :: Scientific/Engineering :: Artificial Intelligence
+Requires-Python: >=3.12
+Description-Content-Type: text/markdown
+License-File: LICENSE
+Requires-Dist: boto3
+Requires-Dist: python-dotenv[cli]
+Requires-Dist: requests
+Requires-Dist: playwright
+Dynamic: license-file
+
+# agent_s4
+
+The Agent S4 package, from the paper
+[Evolving Agent Interfaces](https://arxiv.org/abs/2610.28601). It evolves a
+**shadow interface**: a small Python tool library that a computer-use agent
+imports to operate a desktop. Each step, a **Builder** agent edits an
+interface on the host. A **task agent** then runs benchmark tasks on fresh AWS
+VMs with that interface installed, and its score becomes the variant's
+fitness.
+
+This file describes the code. For setup, credentials and the launch scripts
+behind the published runs, see the workspace READMEs in the
+[Agent-S repository](https://github.com/simular-ai/Agent-S):
+
+- [`osworld_setup/s4/README.md`](https://github.com/simular-ai/Agent-S/blob/main/osworld_setup/s4/README.md):
+  OSWorld-V2, which is the default benchmark.
+- [`scienceboard_setup/s4/README.md`](https://github.com/simular-ai/Agent-S/blob/main/scienceboard_setup/s4/README.md):
+  ScienceBoard.
+
+## Install
+
+`agent-s4` is its own package; installing `gui-agents` does not include it.
+
+The package contains only the code. A run also reads setup files from the
+Agent-S repository: the Builder prompts, the seed interface, the task splits
+and the pinned Prime Agent runtime, all under `osworld_setup/s4/`. So you
+need a clone of the repository either way. Install the package from the
+clone:
+
+```bash
+git clone https://github.com/simular-ai/Agent-S.git
+cd Agent-S
+pip install -e ./agent_s4
+```
+
+or install it from PyPI and point it at the clone:
+
+```bash
+pip install agent-s4
+export SHADOW_EVOL_SHARED_ROOT=/path/to/Agent-S/osworld_setup/s4
+```
+
+Without those files, `python -m agent_s4.cli run` stops and says what to set.
+The benchmark itself (the OSWorld-V2 checkout, AWS and model credentials) is
+set up as described in the workspace READMEs above.
+
+## Entry points
+
+| Command | What it does |
+|---|---|
+| `python -m agent_s4.cli run ...` | Starts or resumes an experiment (`--help` lists the options). |
+| `python -m agent_s4.cli rerun --config-path runs/<timestamp>/config.json` | Runs again from a saved config. |
+| `python -m agent_s4.osworld_v2_preflight` | Runs the offline OSWorld-V2 workspace checks on their own. |
+| `python -m agent_s4.eval.osworld_v2 ...`, `python -m agent_s4.eval.scienceboard_prime ...` | Eval workers. The evaluator harness normally starts these; they can also be run by hand on chosen tasks. |
+
+`run` defaults to `--benchmark osworld_v2`, which uses the splits pinned in
+`config/osworld_v2_release_pin.json`: `osworld_v2_train_50.json`,
+`osworld_v2_val_25.json` and `osworld_v2_test.json` as the held-out set. No
+train or val splits ship for `--benchmark osworld` (the original OSWorld) or
+`--benchmark scienceboard`, so both require `--train-set` and `--val-set`.
+
+## How a run works
+
+**1. Bootstrap** (`orchestrator.run`):
+- If Prime Agent is used, checks its pinned runtime. For OSWorld-V2 it also
+  runs the workspace preflight and checks the configured splits against the
+  release pin.
+- Makes one clone of the benchmark's Evol checkout per island, named
+  `<template>_<island>` (for example `OSWorldV2_Evol_<island>`).
+- Copies the seed interface into the clone's `shadow_interface/` directory,
+  which has its own git repository, and records it as the seed variant.
+- Evaluates the seed on every island in parallel, writes the resolved config
+  to `runs/<timestamp>/config.json`, and hands over to the driver.
+
+**2. Driver loop** (`driver.Driver`):
+- Keeps one global step counter.
+- Each step, the scheduler (`config/scheduler.py`) picks one operator, which
+  runs on every island in parallel. The step ends only when all islands have
+  finished.
+- Every dispatch is logged in the database, so a step interrupted by a crash
+  is resumed rather than run twice.
+- Validation reevaluation runs every `--reevaluation-interval` steps.
+- The loop stops at `--max-steps` or `--max-cost`.
+
+**3. Operators** (`operators/`): each step runs one of these.
+
+| Operator | What it does |
+|---|---|
+| `mutation` | The usual step; see the sequence below. |
+| `crossover` | The Builder combines two parents from the same island into one child, which is then evaluated like a mutation. |
+| `migration` | Two phases: each island sends a tournament pick to another island, and the receiving island evaluates the migrant with its own task agent before adding it. `--migration-mode` and `--migration-topology` control the details. |
+| `elimination` | Removes the lowest-ranked variants from each island. |
+| `reevaluation` | Evaluates each island's current leaders on validation again and averages the results with their earlier scores. It creates no new variants. |
+
+A mutation runs these steps:
+1. A tournament picks the parent (`tournament.py`).
+2. The parent is checked out, and its task trajectories are staged for the
+   Builder to read.
+3. Optionally, a scratch VM is started (`scratch_vm.py`) so the Builder can
+   try things in a live app.
+4. The Builder harness edits `shadow_interface/`. For OSWorld-V2 and
+   ScienceBoard it runs inside a Landlock sandbox, because the Base checkout
+   next to the clone holds the benchmark's gated evaluators.
+5. Edits outside the allowed scope are reverted, and the child is tagged
+   `evol/<island>/if-NNN`.
+6. The evaluator harness runs the child on the train and val splits. The
+   per-task results, scores and costs go into the database.
+
+## Module map
+
+| Area | Modules |
+|---|---|
+| Configuration | `cli.py` (argument parsing), `config/experiment.py` (`ExperimentConfig`, default splits per benchmark), `config/island.py`, `config/scheduler.py` |
+| Control loop | `orchestrator.py` (bootstrap and seed eval), `driver.py`, `state.py` (`LoopState`, passed to each operator), `operators/`, `tournament.py`, `scoring.py` |
+| State | `db.py` (SQLite tables: variants, per-task eval results, islands, history, cost events, dispatch log, reevaluation samples), `costs.py`, `git_utils.py` (variant tags and checkouts in each island's `shadow_interface/` repo) |
+| Builder side | `harness/builder_common.py` (shared Builder subprocess and log parsing), `builder_sandbox.py` (Landlock), `builder_scratch_vm.py`, `scratch_vm.py` |
+| Agent harnesses | `harness/prime/`, `harness/opencode/`: each has the Builder (`builder.py`), the task-agent install and VM command (`evaluator.py`), a runner, and pin checks (`source.py`); see the README in each directory. `harness/__init__.py` is the registry. |
+| Evaluation | `harness/ubuntu_vm.py` (`UbuntuVMEvaluator`: starts an eval worker as a subprocess), `eval/osworld.py` (worker code shared by every benchmark), `eval/osworld_v2.py`, `eval/scienceboard_prime.py`, `eval/grader_image_limit.py` |
+| Benchmarks | `benchmark_spec.py` (template and base checkout names, how run artefacts are named), `osworld_v2_preflight.py`, `synthetic_tasks.py`, `scienceboard_synthetic_runtime.py` |
+| VMs | `vm/utils.py` (shared VM helpers), `vm/owner_tag.py` (adds an `Owner` tag to every EC2 instance) |
+| Paths | `paths.py`, `constants.py`, `utils.py` |
+
+## Where files go
+
+`paths.py` sets two roots:
+
+- **Shared root** (`SHADOW_EVOL_SHARED_ROOT`; defaults to `osworld_setup/s4/`):
+  the vendored Prime runtime, `vm_assets/`, the seed interfaces and the generic
+  Builder prompts.
+- **Project root** (`SHADOW_EVOL_PROJECT_ROOT`; defaults to the shared root):
+  the run workspace. It holds the benchmark's prompts, splits, data, release
+  pin, checkouts and every run artefact. The ScienceBoard launchers set it to
+  `scienceboard_setup/s4/`.
+
+Run artefacts are named per benchmark (and per `SHADOW_EVOL_RUN_NAMESPACE`) by
+`benchmark_spec.ns()`. For example, OSWorld-V2 uses
+`shadow_evolution_osworld_v2_<ns>.db`, `eval_cache_osworld_v2_<ns>/` and
+`builder_logs_osworld_v2_<ns>/`.
+
+## Extending
+
+**Add an agent harness:**
+- Subclass `BuilderHarness` (`harness/base.py`) in `harness/<name>/builder.py`.
+- Put the VM install and task-agent command in `harness/<name>/evaluator.py`.
+- Register the key in both `BUILDER_HARNESSES` and `EVALUATOR_HARNESSES`.
+- Teach `UbuntuVMEvaluator` and `eval/osworld.py` to dispatch on the key. Both
+  currently accept only `prime_agent` and `opencode`.
+- Pin and verify the upstream release in a `source.py`, and record it in a
+  README, as the existing two harnesses do.
+
+**Add a benchmark:**
+- Add an entry to `benchmark_spec.BENCHMARKS`, and to `_DEFAULT_SPLITS` in
+  `config/experiment.py` if it ships default splits.
+- Write an eval worker that plugs into `eval.osworld.main(impl=...)`, as
+  `eval/scienceboard_prime.py` does.
+- The benchmark-specific branches in `harness/ubuntu_vm.py` and
+  `orchestrator.py` (search for `config.benchmark ==`) cover how the base
+  checkout is chosen, which prompt addenda are added and how splits are
+  checked.

agent_s4-0.1.0/README.md

@@ -0,0 +1,159 @@
+# agent_s4
+
+The Agent S4 package, from the paper
+[Evolving Agent Interfaces](https://arxiv.org/abs/2610.28601). It evolves a
+**shadow interface**: a small Python tool library that a computer-use agent
+imports to operate a desktop. Each step, a **Builder** agent edits an
+interface on the host. A **task agent** then runs benchmark tasks on fresh AWS
+VMs with that interface installed, and its score becomes the variant's
+fitness.
+
+This file describes the code. For setup, credentials and the launch scripts
+behind the published runs, see the workspace READMEs in the
+[Agent-S repository](https://github.com/simular-ai/Agent-S):
+
+- [`osworld_setup/s4/README.md`](https://github.com/simular-ai/Agent-S/blob/main/osworld_setup/s4/README.md):
+  OSWorld-V2, which is the default benchmark.
+- [`scienceboard_setup/s4/README.md`](https://github.com/simular-ai/Agent-S/blob/main/scienceboard_setup/s4/README.md):
+  ScienceBoard.
+
+## Install
+
+`agent-s4` is its own package; installing `gui-agents` does not include it.
+
+The package contains only the code. A run also reads setup files from the
+Agent-S repository: the Builder prompts, the seed interface, the task splits
+and the pinned Prime Agent runtime, all under `osworld_setup/s4/`. So you
+need a clone of the repository either way. Install the package from the
+clone:
+
+```bash
+git clone https://github.com/simular-ai/Agent-S.git
+cd Agent-S
+pip install -e ./agent_s4
+```
+
+or install it from PyPI and point it at the clone:
+
+```bash
+pip install agent-s4
+export SHADOW_EVOL_SHARED_ROOT=/path/to/Agent-S/osworld_setup/s4
+```
+
+Without those files, `python -m agent_s4.cli run` stops and says what to set.
+The benchmark itself (the OSWorld-V2 checkout, AWS and model credentials) is
+set up as described in the workspace READMEs above.
+
+## Entry points
+
+| Command | What it does |
+|---|---|
+| `python -m agent_s4.cli run ...` | Starts or resumes an experiment (`--help` lists the options). |
+| `python -m agent_s4.cli rerun --config-path runs/<timestamp>/config.json` | Runs again from a saved config. |
+| `python -m agent_s4.osworld_v2_preflight` | Runs the offline OSWorld-V2 workspace checks on their own. |
+| `python -m agent_s4.eval.osworld_v2 ...`, `python -m agent_s4.eval.scienceboard_prime ...` | Eval workers. The evaluator harness normally starts these; they can also be run by hand on chosen tasks. |
+
+`run` defaults to `--benchmark osworld_v2`, which uses the splits pinned in
+`config/osworld_v2_release_pin.json`: `osworld_v2_train_50.json`,
+`osworld_v2_val_25.json` and `osworld_v2_test.json` as the held-out set. No
+train or val splits ship for `--benchmark osworld` (the original OSWorld) or
+`--benchmark scienceboard`, so both require `--train-set` and `--val-set`.
+
+## How a run works
+
+**1. Bootstrap** (`orchestrator.run`):
+- If Prime Agent is used, checks its pinned runtime. For OSWorld-V2 it also
+  runs the workspace preflight and checks the configured splits against the
+  release pin.
+- Makes one clone of the benchmark's Evol checkout per island, named
+  `<template>_<island>` (for example `OSWorldV2_Evol_<island>`).
+- Copies the seed interface into the clone's `shadow_interface/` directory,
+  which has its own git repository, and records it as the seed variant.
+- Evaluates the seed on every island in parallel, writes the resolved config
+  to `runs/<timestamp>/config.json`, and hands over to the driver.
+
+**2. Driver loop** (`driver.Driver`):
+- Keeps one global step counter.
+- Each step, the scheduler (`config/scheduler.py`) picks one operator, which
+  runs on every island in parallel. The step ends only when all islands have
+  finished.
+- Every dispatch is logged in the database, so a step interrupted by a crash
+  is resumed rather than run twice.
+- Validation reevaluation runs every `--reevaluation-interval` steps.
+- The loop stops at `--max-steps` or `--max-cost`.
+
+**3. Operators** (`operators/`): each step runs one of these.
+
+| Operator | What it does |
+|---|---|
+| `mutation` | The usual step; see the sequence below. |
+| `crossover` | The Builder combines two parents from the same island into one child, which is then evaluated like a mutation. |
+| `migration` | Two phases: each island sends a tournament pick to another island, and the receiving island evaluates the migrant with its own task agent before adding it. `--migration-mode` and `--migration-topology` control the details. |
+| `elimination` | Removes the lowest-ranked variants from each island. |
+| `reevaluation` | Evaluates each island's current leaders on validation again and averages the results with their earlier scores. It creates no new variants. |
+
+A mutation runs these steps:
+1. A tournament picks the parent (`tournament.py`).
+2. The parent is checked out, and its task trajectories are staged for the
+   Builder to read.
+3. Optionally, a scratch VM is started (`scratch_vm.py`) so the Builder can
+   try things in a live app.
+4. The Builder harness edits `shadow_interface/`. For OSWorld-V2 and
+   ScienceBoard it runs inside a Landlock sandbox, because the Base checkout
+   next to the clone holds the benchmark's gated evaluators.
+5. Edits outside the allowed scope are reverted, and the child is tagged
+   `evol/<island>/if-NNN`.
+6. The evaluator harness runs the child on the train and val splits. The
+   per-task results, scores and costs go into the database.
+
+## Module map
+
+| Area | Modules |
+|---|---|
+| Configuration | `cli.py` (argument parsing), `config/experiment.py` (`ExperimentConfig`, default splits per benchmark), `config/island.py`, `config/scheduler.py` |
+| Control loop | `orchestrator.py` (bootstrap and seed eval), `driver.py`, `state.py` (`LoopState`, passed to each operator), `operators/`, `tournament.py`, `scoring.py` |
+| State | `db.py` (SQLite tables: variants, per-task eval results, islands, history, cost events, dispatch log, reevaluation samples), `costs.py`, `git_utils.py` (variant tags and checkouts in each island's `shadow_interface/` repo) |
+| Builder side | `harness/builder_common.py` (shared Builder subprocess and log parsing), `builder_sandbox.py` (Landlock), `builder_scratch_vm.py`, `scratch_vm.py` |
+| Agent harnesses | `harness/prime/`, `harness/opencode/`: each has the Builder (`builder.py`), the task-agent install and VM command (`evaluator.py`), a runner, and pin checks (`source.py`); see the README in each directory. `harness/__init__.py` is the registry. |
+| Evaluation | `harness/ubuntu_vm.py` (`UbuntuVMEvaluator`: starts an eval worker as a subprocess), `eval/osworld.py` (worker code shared by every benchmark), `eval/osworld_v2.py`, `eval/scienceboard_prime.py`, `eval/grader_image_limit.py` |
+| Benchmarks | `benchmark_spec.py` (template and base checkout names, how run artefacts are named), `osworld_v2_preflight.py`, `synthetic_tasks.py`, `scienceboard_synthetic_runtime.py` |
+| VMs | `vm/utils.py` (shared VM helpers), `vm/owner_tag.py` (adds an `Owner` tag to every EC2 instance) |
+| Paths | `paths.py`, `constants.py`, `utils.py` |
+
+## Where files go
+
+`paths.py` sets two roots:
+
+- **Shared root** (`SHADOW_EVOL_SHARED_ROOT`; defaults to `osworld_setup/s4/`):
+  the vendored Prime runtime, `vm_assets/`, the seed interfaces and the generic
+  Builder prompts.
+- **Project root** (`SHADOW_EVOL_PROJECT_ROOT`; defaults to the shared root):
+  the run workspace. It holds the benchmark's prompts, splits, data, release
+  pin, checkouts and every run artefact. The ScienceBoard launchers set it to
+  `scienceboard_setup/s4/`.
+
+Run artefacts are named per benchmark (and per `SHADOW_EVOL_RUN_NAMESPACE`) by
+`benchmark_spec.ns()`. For example, OSWorld-V2 uses
+`shadow_evolution_osworld_v2_<ns>.db`, `eval_cache_osworld_v2_<ns>/` and
+`builder_logs_osworld_v2_<ns>/`.
+
+## Extending
+
+**Add an agent harness:**
+- Subclass `BuilderHarness` (`harness/base.py`) in `harness/<name>/builder.py`.
+- Put the VM install and task-agent command in `harness/<name>/evaluator.py`.
+- Register the key in both `BUILDER_HARNESSES` and `EVALUATOR_HARNESSES`.
+- Teach `UbuntuVMEvaluator` and `eval/osworld.py` to dispatch on the key. Both
+  currently accept only `prime_agent` and `opencode`.
+- Pin and verify the upstream release in a `source.py`, and record it in a
+  README, as the existing two harnesses do.
+
+**Add a benchmark:**
+- Add an entry to `benchmark_spec.BENCHMARKS`, and to `_DEFAULT_SPLITS` in
+  `config/experiment.py` if it ships default splits.
+- Write an eval worker that plugs into `eval.osworld.main(impl=...)`, as
+  `eval/scienceboard_prime.py` does.
+- The benchmark-specific branches in `harness/ubuntu_vm.py` and
+  `orchestrator.py` (search for `config.benchmark ==`) cover how the base
+  checkout is chosen, which prompt addenda are added and how splits are
+  checked.

agent_s4-0.1.0/__init__.py

@@ -0,0 +1,32 @@
+"""Shadow interface evolution framework.
+
+Side-effect on import: set PROXY_CONFIG_FILE to an OSWorld template copy
+if the env var isn't already set and one of the templates carries it.
+
+This has to happen BEFORE `desktop_env` is imported anywhere under
+agent_s4/, because desktop_env.controllers.setup initializes its
+global ProxyPool from PROXY_CONFIG_FILE at module-import time. The
+default is a cwd-relative path that only resolves when run from inside
+a clone — the orchestrator runs from the repo root, one level up.
+
+Both OSWorld templates ship the same dataimpulse.json, so the first one
+present wins; a checkout with only one of them still resolves.
+"""
+
+import os
+
+from agent_s4.paths import PROJECT_ROOT as _REPO_ROOT
+
+if "PROXY_CONFIG_FILE" not in os.environ:
+    for _template in ("OSWorld_Evol", "OSWorldV2_Evol"):
+        _proxy = (
+            _REPO_ROOT
+            / _template
+            / "evaluation_examples"
+            / "settings"
+            / "proxy"
+            / "dataimpulse.json"
+        )
+        if _proxy.is_file():
+            os.environ["PROXY_CONFIG_FILE"] = str(_proxy)
+            break