Ceiling

A maximum you should not exceed because more becomes toxic, fragile, or not worth its cost.

Your most conscientious team member now carries four "urgent" projects simultaneously, because every time something caught fire, she was the safe pair of hands. Her output looks heroic. Her error rate is climbing, and the organization is quietly converting its best person into its next resignation. Past a certain load, more is not more.

A ceiling is the reference shape for that turn: a maximum acceptable value, exposure, dose, cost, or duration that the system should not exceed, because beyond it, more becomes toxic, distorting, or not worth its marginal gain. Use it when limiting a resource protects the surrounding system. Applying it here: no employee carries more than two simultaneous urgent projects without an explicit reprioritization decision by whoever owns the portfolio. The ceiling converts silent overload into a forced conversation, which is the point. What changes: the invisible cost (burnout, error rates, resentment) gets a tripwire before it compounds, and "can she take one more?" becomes a decision rather than a default. The warning the spec attaches: a ceiling can quietly become a target people drive right up to, so distinguish maximum permitted from recommended. And revise the number when new evidence changes your risk model; a ceiling is a hypothesis about where harm starts, not scripture.