#Request and Use a Bounded Result from Another Practice

A.15.9 · Stable · Method pattern · Normative unless explicitly marked informative · Part A - Kernel Architecture Cluster

#About this pattern

This is a generated FPF pattern page projected from the published FPF source. It is canonical FPF content for this ID; it is not a FPF Reference product feature page.

#How to use this pattern

Read the ID, status, type, and normativity first. Use the content for exact wording, the relations for adjacent concepts, and citations to keep active work grounded without pasting the whole specification.

Type: Method pattern Status: Stable Normativity: Normative unless explicitly marked informative

Plain name. Get only the outside-practice result this decision needs, or reuse one that is already good enough.

#Relations

#Content

#Problem frame

Plain name. Get only the outside-practice result this decision needs, or reuse one that is already good enough.

Use this when. One decision or piece of Work can change because of a legal interpretation, safety limit, tax consequence, privacy condition, calculation, objection, observation, or another result governed by a different practice. The available source or request instead names a department, title, document, meeting, approval, provider, or tool, so the receiver still cannot tell what result is needed or how it may be used.

Primary reader. The person, team, organization, or other deciding System that owns the receiving decision or Work. The supplier may be any practice able to return the needed result; neither supplier, specialist, profession, nor professional result is a new FPF kind.

First useful result. Return one of three things, usually in two ordinary sentences:

• a bounded decision to use an already-available result for this receiving use;
• a request for the smallest still-missing result; or
• an honest blocker naming the missing source, Method, capability, authority, access, evidence, or other basis and the decision that cannot yet proceed.

What changes in practice. The receiver checks a result before commissioning more Work, asks for an answer rather than a department or document, and states where supplier judgement ends and the receiving decision begins. A usable existing answer can stop the work before any new request, assignment, meeting, delivery, or acceptance ceremony.

Cheap non-use. Do not open this pattern merely because another practice originally produced a source. If the current result, its limits, and its permitted use are already clear and no cross-practice boundary changes the next action, use the result under its direct pattern and stop. Use A.10 directly when the only open question is evidence, currentness, or bounded reliance. Use the RESULT-TO-NEXT-MOVE entry when a result already exists and only its next downstream question is open.

Not this pattern when. Use the supplier's domain Method for the specialist answer itself; A.2.2 for capability; A.13 for agency; A.15.1 for dated Work; A.2.9 for communication; C.11 for a live choice among an existing OptionSet; and C.38 only when the question has changed from one bounded contribution to several complete ways of obtaining the same receiving result.

#Problem

A receiver often asks for legal approval, a safety review, an architect sign-off, a tax memo, or an AI check. Those phrases identify a search direction or artifact, not the result that can change the receiving decision. They hide the subject, configuration, interval, assumptions, evidence, qualification, authority boundary, and non-use condition.

The opposite failure is to rebuild an organization around a small question. A reversible exchange acquires a fixed role catalogue, responsibility matrix, approval workflow, supplier account, and mandatory record even though an existing qualified answer could have closed the issue. The administrative apparatus grows while the result remains vague.

The missing move is small: start with the receiver's decision, inspect what already exists, request only the gap, preserve the supplier's Method and authority, and use the result only inside its supported boundary. The request, planned or actual Work, communication, result, evidence, acceptance, reliance, authority, and receiving decision remain different facts.

#Forces

#Solution

Begin with one receiving decision or piece of Work and one result that could change its next action. Inspect an available result before commissioning anything new. If a gap remains, request only that gap. Let the supplying practice govern how it answers, then assess and use the return without transferring either side's authority.

#Follow the nine-step bounded-result sequence

1. Name the receiving decision or Work. State who will use the result, what action can change, and the consequence of delay or error. Do not begin with a department, profession, meeting, or document.
2. Inspect an already-available result first. Identify the exact result or claim, its subject, conditions, source, date or window, qualification, and intended use. Apply A.10 only to the evidence, currentness, provenance, and bounded reliance actually needed. If the result is adequate for this use, state the reliance limit and stop. If it is stale, concerns another configuration, lacks support, or only looks authoritative, retain that exact gap.
3. Ask for the smallest new result only when it is still needed. Name the calculation, interpretation, limit, objection, observation, decision, or other result that would change the receiving action. Permit a supported result, a bounded objection, or a blocker as a useful return.
4. Bound the subject and use. State the subject, configuration or situation, interval, assumptions, important exclusions, acceptance condition, and non-use boundary at the grain that can change the answer.
5. Preserve the supplier's practice and Method. Name the supplying practice and applicable Method, source, or inquiry status when known. The request may state needed inputs and evidence, but it does not replace the supplier's Method. If no applicable Method or source is known, return the missing-method inquiry instead of fabricating assigned Work.
6. Recover performer and authority only when reliance needs them. A small exchange may not need either. When they matter, establish capability, access, conflict, assignment, permission, authority, responsibility, and commitment under their direct patterns. For actual supplier Work, recover each actual performer through A.13, let A.15.1 independently admit the dated Work, and use F.6 afterward only if the receiving use also needs to say exactly under which assignment the Work was performed. Failure of that attribution leaves the Work and its separately assessed result intact.
7. Keep request, Work, communication, and result distinct. A request is a claim-bearing episteme. A WorkPlan, assignment, commitment, communicative Work, dated supplier Work, source or returned result, evidence, delivery, acceptance, and later effect each require their own basis. Sending a file or holding a meeting establishes none of the stronger facts by itself.
8. Assess and use the result. Check the subject, conditions, provenance, evidence, uncertainty, qualification, dissent, currentness, and authority boundary that matter to this use. Then rely within a stated limit, reject, request repair, seek another contribution, or keep the blocker. The supplier does not make the receiving decision merely by supplying the result.
9. Reopen locally. Name the source, Method, subject configuration, use, capability, authority, conflict, evidence, or later observation whose change can alter the disposition. Reopen only the affected request, result, reliance, or receiving decision.

The sequence is logical, not a compulsory workflow. Step 2 can close the use before any new request. Steps 5-9 open only when qualification, new Work, a return, or consequential reliance makes them current. Several independent contributions may proceed concurrently, and one receiver may accept one result while another remains blocked.

#Return the first result in ordinary language

For a small reversible use, write no more than the decision needs:

Receiving use: [decision or Work and what can change].

Disposition: [use this already-available result within these limits / ask for this smallest missing result about this subject and situation / stop because this exact basis is missing].

When a new request is needed, a compact request may read:

For [receiving decision], answer [smallest result question] about [subject and configuration] for [window and use]. State the supported result, a bounded objection, or the exact blocker; do not decide the receiving question for us.

Do not add a field merely because it appears in a larger case. Add the supplier, Method, performer, Work, evidence, authority, acceptance, or reopen detail only when it changes or supports the receiving use.

#Persist only what another use must recover

If several contributions, audit, dispute, or consequential reliance require a durable account, use one or more ordinary C.2.1 epistemes. Each account identifies its truthful EntityOfConcern and effective reference scheme, then designates only the request, Work, result, relation, evidence, disposition, and reopen facts actually used. This pattern adds no professional-contribution kind, universal account schema, profession taxonomy, or approval record.

Keep incompatible focuses separate. An account about the receiving decision is not the supplier Work; an account about a returned result is not the world-side subject it concerns; a file carrying either account is not the result or authority. Use A.10 for any relied-on evidence relation and the direct subject pattern for the result's own identity and validity.

#Separate recognition from assurance

• Recognition. A title-, department-, document-, approval-, or tool-shaped request that cannot yet name the result and receiving use is enough to open A.15.9. One available-result check or two-sentence request can be enough to change the next action.
• Assurance. Safety-, release-, compliance-, irreversible-, or high-impact use adds the applicable domain Method, evidence, authority, independence, assurance, acceptance, and stop rules. A concise request does not lower those burdens, and a fluent answer does not satisfy them.

#Worked cases

#Reuse closes a payroll scheduling question

An administrator asks whether moving one contractor submission from Thursday to Friday will miss the current pay run. Before requesting new payroll Work, the administrator finds a dated payroll result for the same payroll entity, contractor batch, cutoff, and calendar edition. The source is current for employee payments but explicitly excludes the contractor batch.

The bounded disposition is: “Use the current result for employee items only. The contractor item remains blocked because the checked result does not cover that batch.” No new payroll assignment, meeting, Work occurrence, delivery, or approval is invented. The administrator either keeps the contractor date unchanged or requests the missing contractor-cutoff result.

#A heat-pump choice needs one acoustic result

An engineering team is choosing a compressor operating region. It already has a general product noise rating, but the decision concerns tonal noise in a named room, mounting configuration, and speed range. The general rating is useful source material but is not qualified for that use.

The team requests: “For the controller decision, return the observed tonal-noise and vibration limits for this compressor, mounting, room, and speed range, with the tested conditions and unsupported region. A supported limit, objection, or missing-test blocker is useful; the acoustics result does not choose the controller.” The acoustics practice keeps its Method and evidence rules; the engineering team keeps the architecture decision. If the question later becomes which complete internal, provider, reuse, or redesign way can make the same accepted control result available, leave this one-contribution question and use C.38.

#A fluent tool output is not specialist approval

A case worker receives a generated summary labelled verified legal review. The summary cites no governing edition, jurisdiction, case configuration, performing Agent, Method, or authority. It may help locate sources, but it cannot support the current eligibility decision.

The honest first result is a blocker: “The generated summary is not qualified for this case and jurisdiction. Obtain a dated legal result for the named eligibility question, or stop the decision.” If later evidence supports the tool or another Agent as the actual performer of bounded legal-research Work, those facts still do not create legal authority or make the receiving administrative decision.

#Precision restoration

Bias check. Institutional prestige, official status, publication recency, ubiquity, and academic praise are retrieval cues, not proof that a result is the best current answer or fits this use. Prefer the result that repairs known shortcomings and survives the receiving question's evidence and applicability checks. An official standard may be the best available basis, but not because it is official.

#Conformance and practical checks

A use conforms only when the checks needed by its claimed result pass:

1. The receiving decision or Work, receiver, and action that can change are recognizable to a cold reader.
2. An already-available result is inspected before new supplier Work is requested, unless none can reasonably be found at the required cost.
3. The first result is a bounded reuse disposition, smallest missing-result request, or exact blocker; it can remain two sentences for a low-consequence case.
4. Subject, configuration or situation, interval, assumptions, intended use, and non-use boundary are present at the grain that can change the answer.
5. The supplying practice keeps its Method, evidence standards, qualification, and domain authority; the receiver keeps its own decision authority unless a separate relation says otherwise.
6. Request, WorkPlan, assignment, communicative Work, dated Work, result, evidence, delivery, acceptance, reliance, authority, and receiving decision are not collapsed.
7. A performer, capability, assignment, authority, or Work claim appears only when its direct basis is current. Actual performer recovery follows A.13, independent Work admission follows A.15.1, and assignment-bound attribution through F.6 is optional and later.
8. A.10 governs evidence, provenance, currentness, and bounded reliance rather than being copied here.
9. A supported result, bounded objection, and honest blocker are all usable returns; an approval-looking label cannot erase a blocker.
10. The reopen condition names the smallest changed fact that can alter this use, not a ritual periodic review.

Recognition check. Give a reader a department-, document-, approval-, or tool-shaped request. The reader should be able to name the receiving decision and return one of the three first-result forms without designing an organization.

Assurance check. For consequential reliance, ask which direct domain Method, evidence, source edition, independence or conflict condition, authority, acceptance rule, applicability window, and stop are required. Missing assurance narrows or blocks reliance; it does not erase a separately identified source or result.

#Anti-patterns

• Request the artifact. “Send a report” replaces the question and receiving use.
• Mandatory fresh work. A current qualified result is ignored because the workflow expects a new review.
• Approval by appearance. A title, logo, signature, provider label, dashboard state, or verified tag is treated as authority or acceptance.
• Receiver takeover. The request dictates the supplier's Method or rewrites the professional conclusion to fit the desired decision.
• Supplier takeover. Supplying one result is treated as making the receiver's decision.
• One contribution account as ontology. Request, assignment, Work, communication, result, evidence, acceptance, and authority become fields of one invented world-side object.
• Tool exceptionalism. AI output is either accepted by fluency or rejected by species rather than assessed under the same direct result, evidence, Work, and authority rules.
• Local change, global reopen. One changed source or condition forces every contribution and decision to be repeated.

#Consequences and trade-offs

#Rationale and SoTA use

The best-known current line for this problem is result-first and use-bounded: define what the receiving decision needs, reuse a qualified result when possible, request only the gap, and preserve the supplier's Method and authority separately from the receiver's decision. Current SYSE.9 demonstrates this move in engineering; the unlike administration, finance, and governance cases show that the boundary transfers while their domain content does not.

This pattern does not select a professional standard, role framework, maturity model, organization chart, or review regime because it is official, new, popular, or widely taught. Such sources matter only when a distinction they supply changes the nine-step move, one direct domain result, or its limits. A source with institutional authority can still be obsolete for the live problem; a less famous source can be stronger when it identifies and repairs the older line's failure.

A.10 already owns evidence, provenance, currentness, and bounded reliance, while RESULT-TO-NEXT-MOVE already routes an obtained result to the downstream question that is current. Repeating either Method here would create a shadow specification. A.15.9 contributes only the cross-practice receiving-decision boundary, the existing-result stop, the smallest missing-result request, the supplier/receiver authority split, and local reopen.

#Relations

• Builds on: A.15 for System-role-Method-Work separation; A.10 for evidence, provenance, currentness, and bounded reliance; A.13 and A.15.1 when actual performer and Work facts matter; A.2.2 for capability; A.2.1 and F.6 only when assignment and later assignment-bound Work attribution are needed; A.2.9 for communication; C.2.1 for any persistent claim-bearing account; and the direct subject pattern for the result itself.
• Coordinates with: the supplying DPF or domain Method for the answer; E.18.1 for accepted-problem carry-through; A.15.7 when a qualified result becomes one fact in ongoing Work steering; and RESULT-TO-NEXT-MOVE when the result exists and a later downstream question becomes current.
• Question-change boundary with C.38: stay in A.15.9 when one receiving decision needs one bounded result from another practice. Move to C.38 only when the new question is how several complete ways could make the same receiving result available. From C.38, return here only for one missing or unqualified outside-practice result inside a way.
• Keeps outside: supplier-domain ontology and Methods, organization design, procurement and service arrangements, fixed role catalogues, universal approval workflows, the receiving choice, actual realization, and authority transfer.

#A.15.9:End

---

Last Updated: 2026-09-03 — this section last modified in upstream FPF commit 59c45532 (github.com/ailev/FPF)