C.19.2:4.4 - Perform the bounded application

1. State the practical use, direct result kind, claimed guarantee, constraints, horizon, and current apparatus state.
2. If one apparatus is already selected, test its credible adaptation path without inventing choice. If candidates are missing, use C.39 for an unexplained way to obtain the result or C.40 for feasible variation and examination of usable material. Add C.18 only when a generation account or archive/front claim is needed.
3. Name available alternatives by their direct kinds and apply the shared eligibility predicate.
4. For each current path, state the smallest adaptation/configuration work and the useful-result threshold: what must be learned, evidenced, integrated, or reviewed before the path can improve the use.
5. Compare available time and budget, prior exposure, post-threshold efficiency, transfer, retention, interoperability, downside, reversibility, and expected reuse using values supplied by their subject patterns. Do not compress them into an undeclared scalar.
6. If choice is current, consume one lawful C.11 ChoiceResult; otherwise continue on the one-apparatus path.
7. On a branch that proceeds to application, prepare the needed A.15.2 plan or, for tool-call enactment, C.24 call plan. Have the admitted system perform A.15.1 work.
8. Inspect the separately governed problem-facing result. Keep an application/configuration note only when reuse, dispute, automation, or consequence makes it useful.