Skip to content

Epic: validated auto-loosening for auto-tune.ts's tuning advisor, gated on a clean backtest #8121

Description

@JSONbored

Problem

src/review/auto-tune.ts's tuning advisor (computeTuningRecommendations) already computes what a loosening recommendation would be (e.g. lowering a confidence floor, raising a scope cap) — the code just refuses to ever apply one. OverridePayload's own doc comment states it plainly: "a loosening recommendation never carries a payload (autonomous loosening is the regression risk the loop exists to avoid)." #8082's Pareto-floor backtest is exactly the missing risk-measurement that comment names as the reason loosening was never allowed to be automatic. Once a proposed loosening change can be backtested against real historical ground truth and shown to regress nothing, the original justification for refusing it no longer straightforwardly applies.

Area

src/review/auto-tune.ts (computeTuningRecommendations, OverridePayload, the apply path) + #8082's calibration/backtest primitives.

Proposal

Deliverables

Deliberately none yet — decision-and-design only until #8105 resolves and the bigger step is explicitly approved.

Resources

Boundaries

No autonomous config change of any kind happens as part of this epic without an explicit, later, maintainer-approved design — this is tracking the DIRECTION, not committing to the mechanism yet.

maintainer-only — a significant trust/safety-critical architecture direction, not a build task for contributors.

Metadata

Metadata

Assignees

Labels

maintainer-onlyOwner-only work — yields no Gittensor points.roadmapOn the Wave-2 agent-layer roadmap board (project 9)

Projects

Status
Done
Status
Done

Relationships

None yet

Development

No branches or pull requests

Issue actions