Skip to content

overengineering: scheduled/delta lane — recurring audit runs that surface only what changed #2898

Description

@kyle-sexton

Deferred lane from the overengineering-detection-skill interview (Brief: docs/topics/overengineering-detection-skill/PLAN.md, Q5/Q11).

V1 of the planned overengineering plugin is on-demand and human-in-the-loop. The interview decided the scheduled/autonomous lane is deferred but designed for: the audit's findings report is a persisted, diffable Markdown artifact with stable ordering/ids precisely so a later recurring lane can diff two runs and surface only deltas (new clutter, verdict changes, evidence updates) instead of re-reporting the full surface.

Scope for this follow-up:

  • A recurring entry point (routine/loop/cron per consumer preference) that runs overengineering:audit, diffs against the previous findings artifact, and reports deltas only.
  • Read-only always — the scheduled lane never enters realign; verdict changes queue for the human.
  • Noise budget: define what delta magnitude is worth surfacing so the lane doesn't become the nagging automation the plugin exists to retire.

Blocked until the V1 enforcement-surface lane ships and the findings-artifact format stabilizes.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions