The recommended CHIP process here actually contains no detail of the process to follow in case of a problem that arises in a CHIP after November lock-in but before May activation.
I discovered this in considering requests from @lightswarm & @leo to delay Fablous, which seem at least somewhat motivated by concern about the community’s ability to handle an unexpected problem in this window (including the lack of both precedent and process for this - hopefully unlikely but always possible - scenario). I discussed this on Podcast Episode 194.
My “understanding” or assumption is like this:
As @rosco mentions on the Podcast, it’s often an undefinable thing where we can’t specify everything ahead of time (by definition, an unknown unknown can always be something we hadn’t considered or that becomes controversial) - but we should probably still try to have a plan.
I also raised it on Twitter which a couple of people chimed in on, mostly to say they likely had a similar undocumented assumption.
In the total absence of documentation, I am bringing it up here for consideration and feedback. It would be nice to have this agreed or at least pondered ahead of needing it, in the case that we ever did.
Doing so may also help to reassure all participants in the CHIP process as regards future upgrades and lock ins.