A.15.2:1 - Context (plain‑language motivation)

Before and during Work. Before Work begins, keep intended-work content in this WorkPlan. Use A.15.5 when the question is whether that Work is ready to start, and use C.11 only when a known chooser must compare an already formed OptionSet. Do not invent current Work for A.15.7. During Work, an A.15.7 answer remains separate from the plan. Revise the WorkPlan only when the intended-work content actually changes, and identify any later performed action under A.15.1 rather than back-filling the plan.

Intended operations are coordinated in time. Even with suitable performers, capabilities, and methods, no intended performance begins merely because it is forecast or described: a system must decide when and by whom possible future work is intended, under what constraints and budgets. Teams need a first-class concept for plans and schedules that does not get confused with:

• the semantic “way of doing” (that is U.Method),
• the written recipe (that is U.MethodDescription),
• the performed work occurrence (an individual admitted under U.Work), or
• the state-change model (that is U.Dynamics).

U.WorkPlan is that missing intended-work episteme.