Frozen source-rivals-v0 source and prospective launch record. The 120-attempt construction/assessment barrier remains active; this archive contains no task deliveries, provider prompts, active operation traces, grades, or credentials. The ten development identities were heavily exposed; this is exploratory, not clean held-out validation. Reproduction requires the unchanged Harness-Bench checkout at commit b8d89634c6f445fcc68ceb6744a59bef6cdf4863, official baseline sources, Docker, and the dedicated evaluation credential. Recreate the C-Clean reference from the attached reconstruction inputs and the public agent_harness_2 v1 supplement URL in ACQUISITION.json. Use the public reconstruction script with --verify-only. The supplied execution-evidence Dockerfile requires the external ecology-execution-evidence-base:e2cb5a5f5b5c image and installs strace; neither that base image nor image layers are included here. Build it as ecology-execution-evidence:prep-v0, then build the local C-Clean Dockerfile over the reconstructed source. The fourteen manifest hashes identify the latest public source, and the PREPARATION document records its earlier preparation status; the current STUDY adopts this reference. The local image is not claimed identical to a historical paper image. Run freeze/launch only in a new study directory; preserve the original once-only barrier and accounting rules. Full commands are in the frozen INTEGRATION.md; native.py holds the exact ordinary notice, both access policies and worker instructions; native.py acquires rivals through the same accounted Luna provider; executor.py confines each candidate/rival case separately. Preparation checks are engineering evidence, not benchmark capability evidence.
