vrr/ouroboros
2
0
Fork 0
mirror of https://github.com/razzant/ouroboros.git synced 2026-10-03 12:18:39 +00:00
Code Issues Projects Releases Packages Wiki Activity Actions 5
ouroboros/devtools
History
Ouroboros 80d49bd7ca Live E2E stand: round-robin dispatch by attempt, no bench budget profile, per-round preflight worst case 
The verdict is pass-of PER scenario, so the dispatch order now maximises the
minimum admitted attempts per scenario: a1 of every scenario, then a2, then a3,
largest reservation first within a round (requested_task_ids keep the argument
order). At the owner's configuration (cap 300, per-task 50, attempts 3, pass-of 2,
3 lanes, --self-mod) with pessimistic spends, largest-first left SW1 with at most
one admitted attempt; round-robin keeps every scenario at two or more.

The cost_hard_stop_pct=100 projection is dropped (scenarios.STAND_BUDGET_PROFILE,
LaneContext.submit metadata, its pins and handbook text): with a reservation of
at least 2 x per-task the product's per-task axis already binds, and a bench
profile would change the pacing path under test. Every stand root runs under the
product's default ceiling, including the evolution root and SW1's UI-path root.

budget_preflight takes --lanes and records the per-round worst case (the lanes
largest reservations of one attempt per scenario at once); the handbook states
that outcomes among equal waiters depend on wake order, so a feasibility number
is a range at the margin. Docstrings now say rc.14 showed up to two evolution
cycles per lane (t=0 and post-task) and that the lane TOTAL_BUDGET is the fence.

Tests: the deterministic driver over the real RunBudget takes the dispatch order
and pins the owner configuration under realistic and pessimistic spends for
round-robin (admitted set, per-scenario counts, spend range) and shows the
rejected largest-first order leaving SW1 below pass-of; the run-wide cap manifest
pin is re-parametrised for round-robin (cap 16, pass-of 2); configuration A/B pins
and the projection pin are removed within the band ceiling.

Co-authored-by: Ouroboros <311266734+ouroboros-agent@users.noreply.github.com>
2026-09-05 17:22:43 +00:00
..
benchmarks e2e_live: cap the nested preflight xdist fan-out per lane (W4-preflight-workers) 2026-09-05 09:52:35 +00:00
e2e_live Live E2E stand: round-robin dispatch by attempt, no bench budget profile, per-round preflight worst case 2026-09-05 17:22:43 +00:00
__init__.py feat(devtools-benchmarks): add official benchmark harnesses and workspace executor 2026-06-06 12:03:30 +03:00
measure_review_pack.py devtools: measure the FULL scope input with the real assembler (P4) 2026-09-05 09:52:35 +00:00
README.md feat(devtools-benchmarks): add official benchmark harnesses and workspace executor 2026-06-06 12:03:30 +03:00

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 devtools only through a separate reviewed runtime plan.