mirror of
https://github.com/razzant/ouroboros.git
synced 2026-08-25 19:11:44 +00:00
d6210b1a05
The pre-implementation gate reviewed an unbounded prose plan with a ~100k-token governance pack, planning-scout subagents and an Atlas, and every rewritten plan minted a fresh fingerprint that bought a whole new paid wave from cold reviewers. Convergence was structurally impossible: the reviewer was asked to author a competing plan every wave, REVISE_PLAN could not be dispositioned, and nothing capped the cycles. plan_task now reviews an INTENTION — the same organ whether the work is code, research, a deliverable or an action in the world: - a typed domain-neutral SPEC (goal, in_scope, non_goals, acceptance_claims, invariants, decisions with rejected alternatives, deferred, affected_resources, evidence) with host-minted ids that are the only valid `breaks` targets; - ONE structural fact tiers the governance pack: `constitutional` iff a declared target resolves under the system repo (never prose, never a plan-kind taxonomy); - agent-declared evidence, bounded, with EVERY absence named, the runtime data plane denied outright, and the exploration log redacted through the same SSOT task acceptance uses; - typed findings (blocking with a `breaks` id | note | need_evidence) with the HOST computing the aggregate through adaptive_quorum — no reviewer emits GREEN as authority, none writes a competing plan; - ONE owner setting OUROBOROS_REVIEW_MAX_CYCLES (default 2, unlimited available) bounds paid cycles for plan review, task acceptance (passes = cycles - 1) and the commit gate's identical-diff attempt cap; an identical envelope replays for free and a DEGRADED wave costs nothing; - under blocking, an open plan holds implementation and a spent cap escalates with a typed review_cycles_exhausted reason and an honest blocked terminal; under advisory the agent may proceed with the wave open and a loud disclosure. Deleted: planning scouts, the plan Atlas, plan_class, context_level, the governance mega-pack, the generative reviewer stance, the hidden 32-wave limit and the api_chat-only pin. Net effect on the tree is negative. Co-authored-by: Ouroboros <311266734+ouroboros-agent@users.noreply.github.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.