mirror of
https://github.com/razzant/ouroboros.git
synced 2026-08-04 16:19:50 +00:00
a947a9310f
Forensics against the leader's own published per-task dump put the gap at 19 tasks, 8 of them one class: the work was done and never checked against the surface the grader reads. The worker now writes the task's obligations as a numbered checklist BEFORE its first mutating action and closes each item as observed-satisfied / not-verified / impossible before it may finish, repairing per item. Plural instructions still cover every element; only a singular referent resolving to several candidates forces a justified single choice, and the contract is revisable on new observation. Three infeasibility shapes are named (discovery outside a stated means restriction; a named mode the app does not ship; a trigger narrower than the task states), framed on the END STATE rather than the route, with the brake the gate already had: a wrong verdict scores zero even when the machine is already correct. The desktop environment's own gsettings/dconf is a legitimate surface for STORED values only — if the task wants something DISPLAYED and the device does not exist, writing the key is not a workaround. Two adversarial reviews corrected this change three times, and each correction is the interesting part: - The colour motivation I had deleted as false is TRUE: replaying the real grader shows 8472fece's own gold (palette 2A6099) scores 0 against its own evaluator, which measures distance to pure 0000FF. No palette entry can win it; deleting the motivation gained nothing and endangered 04578141, a live 1.0 won because of it. Restored and tightened to the exact colour name. - An earlier draft wrote the per-task proxy config — which carries the account password — into all 361 result directories, i.e. the tree we archive and publish. It now lives in lane-private state and is unlinked after the task. - The session tag keyed on run_dir.parent.name, which is the DOMAIN, so the two concurrent campaigns would have shared one exit IP per task. Keyed on the campaign root instead. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> |
||
|---|---|---|
| .. | ||
| benchmarks | ||
| __init__.py | ||
| README.md | ||
Ouroboros Devtools
devtools/ contains operator-side and benchmark support code that should be
versioned with Ouroboros without becoming part of the runtime core.
Rules:
- Generated logs, datasets, run outputs, Docker layers, and secrets do not live here.
- Default benchmark outputs go under
/Users/anton/Ouroboros/bench_runs/. - Runtime modules must not import
devtools. - This is not an immune-system bypass: touched files are reviewed normally.
- Promote code out of
devtoolsonly through a separate reviewed runtime plan.