Skip to content

NC: guarded durability metric — make long-term erosion visible to rollback #407

Description

@mercurialsolo

Problem

exporter.rs tracks cost/task, retries, and verifier pass-rate — all task-completion proxies. Weng's post (bottleneck #6) warns that maintainability, migration cost, backwards-compat, and ownership boundaries are invisible to completion signals, and a self-improving loop optimizing only completion will silently erode them.

The NC counteractive-rollback guard (docs/niche-construction.md Safety Invariant #3) reverts on "regression on any guarded metric" — but if no guarded metric captures durability, the guard is blind to exactly the regressions the post warns about.

Proposal

  • Add at least one guarded durability metric to exporter.rs, e.g. post-merge revert rate, or "auto-applied edits that later required human rollback."
  • Wire it into the charter's [constraints] / guarded-metric set so Tier 0–2 auto-apply rolls back on durability regression, not just cost/pass-rate regression.

Why it matters

Without this, "verifier-confirmed improvement" can mean "completed the task while degrading the codebase." Required before trusting any auto-apply tier with real blast radius.

Part of epic #358. Relates to #360, #363.

Metadata

Metadata

Assignees

No one assigned

    Labels

    P3Low priorityenhancementNew feature or requestepic:niche-constructionAuto-improving local harness via niche constructionmetricsInstrumentation, measurement, and evaluation

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions