Jump to text
On this page
Copy and source
Published source confirmed at last check

Source changed 2026-11-18 21:11:39 UTC · snapshot created 2026-11-18 21:12:35 UTC · last check 2026-11-18 22:30:10 UTC

CMP.16:4.2 - Try the whole before fixing the units

Sketch the computation at a level where its intended effect can be followed. Treat a proposed higher operation as a temporary obligation: say what it receives, what it must return or change, and why the rest of the construction needs it. Do not yet assume that the operation exists or costs one step.

Suppose each proposed part has supplied exactly its promised result. Attempt the next join or continuation. At the first missing contribution, identify the distinction or action that would make the join possible. Typical remedies have different grounds:

  • Enrich a returned summary when the join needs information the part discarded. CMP.2 develops this for recursive construction.
  • Introduce a compound unit when a relation between smaller items must be preserved by every permitted assembly. Check that the new constructor still covers the required cases.
  • Change the operation boundary when separately exposed updates permit invalid states or repeated repair. Include the boundary’s interruption and visibility assumptions.
  • Pass context or postpone a choice when a part cannot correctly decide without information available at the join.
  • Change the decomposition when obtaining the missing contribution would repeat the original difficulty or exceed the resource limit.

Try a simple alternative alongside the favored design. Keeping the original units and checking the final result can be cheaper when invalid assemblies are rare and harmless. A stronger constructor is useful when it makes repeated use or reasoning materially easier.