ME.8:0 - Use This When

Use this pattern when people need usable claims about an identified Method or a candidate account of a proposed way of working. The receiving use may concern planning, enactment, comparison, review, revision, publication or teaching; retain the claims’ actual status. Start from one named use: who needs to do or decide what, which Method claims that use consumes, and what can remain outside the edition.

The first useful result is a short use-coverage row. It names the Method or candidate account, the receiving use, the claims needed now, the claims deliberately omitted, and the stop. That row prevents a documentation project from expanding before its practical question is clear.

Do not use this pattern merely to publish, diagram, approve, schedule, or record Work. A U.MethodDescription is the claim-bearing episteme whose exact EntityOfConcern is one Method already admitted under A.3.1; its code, diagram, form, carrier, approval, WorkPlan, and dated Work remain different things. If the proposed whole is still a candidate account, improve that account without classifying it as a U.MethodDescription for the whole.