Skip to main content

Decision record

Every non-obvious choice in the framework has an architecture decision record: the context, the decision, the alternatives rejected and why. There are 44 of them. They are internal working documents and are not published; the design pages on this site describe the system as built, and this index summarises the decisions those pages rest on. The ones cited on this site:

ADRdecisionrejected
0002a single gateway tier (LiteLLM, replicated behind a load balancer) in the VPC for every callper-harness provider keys; trusting harness usage counters
0006SQS-backed job dispatch with a hand-written closed-loop autoscaler (superseded for the harness pool by 0030 and 0041; still the shape of the eval pool)ECS managed scaling
0012harness workers on Fargate, eval workers on EC2one consolidated fleet
0017uv for dependency management with a committed lockfilepip
0018scale shape for 20k concurrent instances: live state in Valkey, VPC sizing, dashboard designPostgres as the live store
0019a local proxy shim per task for budget enforcementpolling the gateway spend log
0020per-instance eval images cached in a private registry by a dedicated warm jobpulling from Docker Hub per worker
0024an S3-dropped run config triggers dispatch, alongside POST /runsAPI-only launches
0025 / 0029repository content served by a VPC-internal git mirror over git daemon, resolved by nameEFS; HTTP CGI
0028 / 0033harness network isolation: no egress, one always-isolated posture, interface endpoints on the eval tierallow-listed egress; a switchable posture
0030 / 0032one Fargate task per instance, launched by sharded dispatchers; the task receives a job reference and reads the instance itselfa pooled worker per harness; the full job in the queue message
0035 / 0044per-run keys; the spend cap is the provider key's limit, the gateway key carries no max_budgetshared keys with soft budgets; a budget monitor that observes rather than enforces
0037measurement is a first-class plane: the shim meters every harnesstrusting each harness's own counters
0038contamination detection per instance, and the denominator rule (both denominators always, with intervals)a single headline rate
0041arrival-paced admission for shared-pool LLM capacity, seeded by a discovery probefixed concurrency; provider retry-after alone
0042empty-judgment recovery cascade for a reasoning-model judgedropping empty verdicts silently
0043track upstream SWE-bench 5, pin dataset revision and image digestsstaying on 4.1
note

The records themselves stay internal. What the system was required to do is on the Requirements page; how it is built is on the design pages.