After receiving abundant feedback on how stagnancy might interact with sealing research, we want to make the following tentative statements about how we'll handle the interaction. As with stagnancy as a whole, these are all things that we're trialing – and if they end up producing unfun or unintended results, we'll simply change or remove them.
First, Hazō does not necessarily need to finish a project to remove stagnancy. Similarly, a single project may not necessarily be enough to remove stagnancy, if the complexity is low. Fewer rolls will be required the harder the project is.
Second, Hazō can roughly tell whether a project is likely to challenge him, and to what degree. For projects that he has more veterancy in, he'll only know after an infusion roll. For other projects in completely new domains, he may know after only a single prep day. This is because in newer domains, he can more easily understand what all he doesn't know and needs to learn, whereas in areas where he has veterancy, he needs to get more in the weeds to discern whether there's any new experiences for him to learn from.
Third, if you pick some axes of variation (e.g. numerical bonus, # of activations) and request that Hazō adjusts the project along the axes so that it removes stagnancy, we'll try our best to pick appropriately so that the project is difficult enough to remove stagnancy. Example:
- Research Reusable Rocket Boots (vary bonus, # of activations to remove stagnancy)
Finally, in the interest of good faith, Hazō can remove the XP penalty associated with one Sealing stagnancy barrier while he is working on an appropriately difficult project. This is meant to match combat stagnancy, where we said we'd suspend penalties as soon as Hazō took a combat mission that was likely to remove his stagnancy.
An additional note: Hazō should try to remove sealing and combat stagnancy with his main body. Due to the inefficiency of SC memory-transfer, it will be much harder to remove stagnancy through Shadow Clones.