ouroboros/devtools
Ouroboros 4e82bc57b1 measure_review_pack: offline by construction, exact zero-diff headroom, one checkout
Closes the second-absorption review findings on the F3-A pack meter:
- reviewer windows are read cache-only through capability_evidence.probe(
  allow_fetch=False); an unknown window is disclosed and sized at the fit
  ladder's default instead of probed, so the meter never fetches provider
  metadata nor writes capability evidence (proved byte-identical output
  with and without network, no state/capability_evidence.json created);
- the o200k tokenizer never downloads: a cache miss is a typed
  TokenizerUnavailable disclosed in the report;
- headroom is derived from the exact zero-diff serialized message
  (constitutional preamble + BIBLE, stable prefix, dynamic scaffolding with
  an empty pack, the fixed user turn) in the fit ladder's units, with the
  parts the ladder itself does not count named separately;
- --repo controls every corpus read (BIBLE, checklist + archive, docs).
tests/test_measure_review_pack.py pins the cache-only seams, the tokenizer
refusal, the headroom formula and the --repo selection.

Co-authored-by: Ouroboros <311266734+ouroboros-agent@users.noreply.github.com>
2026-09-04 23:24:29 +00:00
..
benchmarks Merge upstream ouroboros db6d7cf8 into the v7 line: absorb PR #609 net-resilience and PR #614 update letter 2026-09-04 22:53:15 +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 measure_review_pack: offline by construction, exact zero-diff headroom, one checkout 2026-09-04 23:24:29 +00:00
README.md feat(devtools-benchmarks): add official benchmark harnesses and workspace executor 2026-06-06 12:03:30 +03:00

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.