mirror of
https://github.com/razzant/ouroboros.git
synced 2026-10-03 20:27:56 +00:00
- The alarm no longer re-arms on the owner's own direct turn ending (B13) nor on a project digest of a tree consciousness started; notify keeps the boot floor after a restart (max(last wake, boot) + floor). - A wake carries what is left of its allowance as the tree's GRACEFUL ceiling (`root_cost_ceiling_usd`, now honored for the root itself by the in-task stop) instead of narrowing the ledger fence: one Main attempt reserves ~$8 up front, and the narrowed fence refused every wake of a nearly spent day before its first call, posting a budget error into Main at each heartbeat (stand: 15 such wakes). A remainder at or below the planning margin is skipped as allowance_exhausted. - A wake the lane could not admit backs off like a failed wake; a closed budget door is retried quietly at the interval, a transient door at the floor. - The wake message lists unanswered cards of any task, the previous wake's own included (an expired_terminal card still takes a late answer). - Only an owner's stop is sticky against toggle_evolution: a stop the agent placed remembers its source (`evolution_stop_source`) and stays undoable by the agent. - The status snapshot carries `unknown_unmetered`/`integrity_degraded`; the allowance line says "at least $X" and "ledger integrity degraded" when they apply. - Docs: a Presence cycle a wake starts is outside the allowance; benchmark profiles drop the retired OUROBOROS_BG_MAX_ROUNDS key. Co-authored-by: Ouroboros <311266734+ouroboros-agent@users.noreply.github.com> |
||
|---|---|---|
| .. | ||
| benchmarks | ||
| e2e_live | ||
| __init__.py | ||
| measure_review_pack.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.