Executed-assertion acquisition, 2026-11-15

Ten engineering checks pass on five invented programs,46 container executions,
zero model/benchmark/grader calls. This is not native integration or a policy result.
See notes/executed-constraint-acquisition-20261115.md for outcomes and limits.

Extract this archive into a new directory. Then extract the nested
engineering/candidate-contrasts-preparation-20261115.zip into that same directory
for methods/candidate_contrasts and its documented runtime/reconstruction dependencies.
No file from the new adapter overlaps the older methods/candidate_contrasts source.
Run: python -m methods.executed_constraints.check --out engineering/new-acquisition-run
The output directory must be absent. Requires Docker, the documented pinned image
and its /opt/nanobot/bin/python. Default host Docker path /home/harbench/bin/docker;
Executor accepts an alternate docker= path in the Python API (not exercised here).
DOCKER_HOST defaults to unix:///run/user/996/docker.sock; set for your own service.
Recorded absolute source paths are provenance, not required output locations.

The outer manifest binds all original source and execution records; the nested
core archive retains its separate old failure history and reconstruction limits.
A wrong expectation favors a wrong candidate; observed-prefix agreement leaves
a later assertion failing. No selected or installed patch, correctness certificate,
source adjudication, population prevalence or complete-work gain is established.

The original execution records are nested in engineering/executed-constraints-v0-records.zip. Extract that archive into the same root to inspect them. This avoids the platform outer archive entry limit; bytes are unchanged.
