Skip to content

Add overlay revalidation, invalidation, and rollback #123

Description

@nisavid

Parent

Task

Implement overlay startup revalidation, invalidation, rollback, and lifecycle fencing.

Revalidate the active root at startup and before profile-backed plans against catalog, model, backend, dependency, device, driver, topology, configuration, workload, generation, expiry, digest, and health identities. Known drift or expiry must transition to stale and restore the bundled method/fallback. Corruption, ambiguous pointer/object state, ownership uncertainty, or effect ambiguity must quarantine conservatively and retain maximum plausible claims. If an invalidated overlay supplied capacity credit, re-evaluate existing residents and fence new growth rather than assuming residency remains safe.

Manual rollback and reset must be privileged, generation-bearing, append-only operations. Add tests for every invalidation class, clock/restart behavior, copied stores, bound exceedance, active-plan fencing, resident suspension/quarantine, rollback replay, and recovery after failed publication.

Activity

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

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or requestready-for-agentFully specified and ready for an AFK agentwayfinder:taskTask that unblocks a Wayfinder decision

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions