KCAE.COMPOSE:4.4 - Check joint constraints and scheduling

Collect the resources shared across the whole: a person, permission, device, context window, budget, time interval, data store or physical capacity. Add simultaneous demands where addition has the right meaning; do not add incomparable quantities. Check global conditions as well as pairs.

In CedarBench, three exports each reserve 2 GB and the cache has 5 GB. Every pair needs 4 GB and fits. The whole needs 6 GB and does not. A schedule with two concurrent exports followed by the third removes that particular conflict, provided the first pair releases its reservation. It can still violate a deadline. If each export takes ten minutes and the window is fifteen, this schedule needs twenty minutes and is infeasible. The recommendation must then reduce concurrency demand, change capacity or change the accepted completion condition; simply ordering the steps has not solved the original problem.

Check interference that is not a scalar sum: two methods may mutate the same source, require incompatible configurations or use one judgement as if it were independent evidence for the other. Include transition and cleanup work. “Each method is applicable” and “this whole is feasible now” are different conclusions.

Consider a ten-minute serial work window. The receiving operation B takes four minutes and requires result R. Candidate A obtains R in nine minutes. A followed by B takes thirteen minutes and fails the window. Preserve B and its unsupplied need; search for another way to obtain an equivalent R in at most six minutes, including the joins and preparation. Candidate C supplies the same R under the case’s source conditions in five minutes, so C followed by B takes nine and fits. This search constructs an alternative that rejecting A+B alone cannot produce. It does not establish that C is the best possible supplier.

If a new source edition makes C take seven minutes, reopen the partial arrangement whose feasibility used that estimate. C+B now takes eleven minutes. Retain B’s still-valid contribution, seek another supplier or a permitted change of schedule, and return the unsatisfied window if neither is available. Do not reuse the earlier nine-minute judgement merely because the method names stayed the same. The durations in this example are constructed assumptions, not measurements of a deployed system.