mirror of
https://github.com/razzant/ouroboros.git
synced 2026-10-03 20:27:56 +00:00
A second human-facing label beside recommended_use rotted against route edits (the shipped 'Fast scout' name survived a re-route to a cursor session and misdescribed the row in the reviewer picker and the delegation prompt). The parser accepts legacy 'name' values and DROPS them — the next serialize omits the key, which is the whole migration; no fabricated title-case fallback either. The delegation catalog and dispatch snapshot carry facts first (subagent_id, route_class, requested target/model, effort) with recommended_use LAST as bounded owner intent; presets and the legacy-derived rows mint no names; committed bench profiles re-serialized through the SSOT. prompts/SYSTEM.md states the identity rule (facts true when description disagrees) and the LLM-first hygiene: an agent editing a row's route rewrites its recommended_use in the same change. |
||
|---|---|---|
| .. | ||
| 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.