Part III — Alternatives, Values, Uncertainty, Consequences and Robustness

PSD.8 - Generate Decision Alternatives

Type: DPF pattern body Status: Candidate

Primary working result: a finite candidate set for one decision-support question, with materially different alternatives, their supported and unresolved premises, and the exact candidate gaps that still matter.

PSD.8:1 - Problem frame

Use this when an inquiry has clarified what matters but the proposed decision still contains only the incumbent, a sponsor’s preferred project, or two labels such as “buy or build”. Also use it when a request for development advice names a course, provider, reorganization, or AI tool before the possible directions have been constructed.

Start by asking what different action could address each live formulation or concern. Change the mechanism, arrangement, combination, timing, or commitment being considered, then state enough of each resulting alternative for a fair consequence comparison. The practical gain is a choice worth examining, including an honest gap when no supported alternative is available.

The governed object is the candidate set, not a selected action. A candidate describes a possible intervention or commitment; its description does not establish feasibility, permission, performed Work, or benefit. Alternatives may address competing formulations rather than obtain exactly the same result. Preserve that difference instead of inventing parity.

Do not use this pattern when an adequate finite set already exists and only comparison or an authorized choice remains. Use the direct domain practice when it already owns the complete alternative-generation question. A population or lineage without a population-local recipient or chooser is not a recipient of development advice; an authorized researcher’s intervention is a different decision-support case.

PSD.8:2 - Problem

An apparently open choice can be closed before analysis begins. A list of pump models omits deployment arrangements; a list of training courses omits changing the Work that prevents capability expression; a list of AI models omits the tool, data, or operating configuration responsible for the failure.

Unrestricted ideation creates the opposite difficulty. Hundreds of names can repeat the same intervention, depend on unsupported capacities, or combine benefits that cannot coexist. Novelty does not make an alternative useful, and an attractive candidate does not become admissible because it survived a workshop.

PSD.8:3 - Forces

PSD.8:4 - Solution

Construct alternatives from the live decision question and useful differences in the inquiry. Make each candidate complete enough for its next use, separate qualification gaps from rejected directions, and stop with a bounded set or a precise missing-alternative result.

PSD.8:4.1 - Recover the receiving question and useful inputs

Name the recipient, holder or subject, horizon, current arrangement, later choice owner, and the commitment being considered. Recover the protected conditions and resource bounds that can change which alternatives are live. If the request still has no recoverable question or authority boundary, return that missing premise rather than inventing a development programme.

Use a PSD.3 formulation set only where its differences suggest different interventions. A formulation is not itself an action. Use the PSD.5 model account only where a model discriminates candidate mechanisms or exposes an omitted consequence. Use PSD.7 inquiry results where a shared or contested claim changes the alternatives; agreement is not required.

These are conditional contributions. Use a qualified direct result when it supplies the same needed premise. If the needed input is absent, stale, or incompatible with this subject and horizon, retain the precise gap. Neither adjacent PatternIDs nor a completed workshop supplies an alternative by itself.

PSD.8:4.2 - Vary the decision-changing contents

Ask what the proposal is meant to achieve, why that result matters, and what other way could address the concern. Generate some ideas independently before group discussion when early advocacy could anchor the whole inquiry. Then use differences and objections to construct additional candidates.

Useful prompts include changing the intervention mechanism, obtaining arrangement, scale, timing, resource allocation, or commitment. Consider combining compatible actions, retaining the present arrangement, declining a proposed change, and obtaining information before a larger commitment. These are prompts, not a mandatory taxonomy or a required number of options.

Describe “no new action” against a real baseline. It may still include already authorized maintenance, contractual duties, continuing costs, deterioration, or exposure. It is not a cost-free, consequence-free empty world.

For a staged direction, say what happens first, what later choice remains open, which observation could inform it, and what delay or irreversibility the first commitment introduces. Do not call a probe reversible merely because it is small; obtain the direct feasibility, consent, safety, and recovery premises when they matter.

PSD.8:4.3 - Turn labels into sufficiently complete candidates

For each material alternative, state the proposed change from the current arrangement, affected subjects, intended result, enabling conditions, major burdens, evidence basis, and unresolved premise. Distinguish what is supported now from what is proposed or unknown.

Use C.38 only when several whole ways are intended to make the same receiving result available and labels still hide their different burdens. If the alternatives seek different results, retain the difference and let the decision-support comparison expose it. Do not force a same-result declaration merely to obtain a neat table.

A combination is another candidate when its interactions can change consequences. Check shared staff, facilities, money, dependencies, sequencing, and incompatible assumptions. Two independently attractive components do not establish an attractive combined arrangement. A provider’s advertised capability, a course title, or a benchmark score is not a qualified result for this holder.

PSD.8:4.4 - Distinguish exploration from a live commitment option

Keep a promising but unresolved proposal available for inquiry without presenting it as an admissible commitment. A short annotation is enough: “comparison-ready within these conditions”, “requires this qualification”, or “excluded for this stated reason”. These phrases describe the present use; they create no new universal status system.

Inspect an adequate existing specialist result before requesting more. Preserve useful directions and the exact limit on a stronger claim. A decision-changing cross-practice gap becomes a feasibility, allocation, transfer, security, or other request only when A.15.9 selects its obtainable contribution against the whole acquisition burden through C.11.DUA. A missing result may block one branch while others remain useful.

Use C.17 when a claim about novelty, diversity, or usefulness of the named candidates needs characterization. Use C.18 when open-ended generation, archive, or front stewardship is actually needed. Neither characterization nor archive membership chooses the decision alternative. Use C.19 only for an actual live-pool policy question; thin evidence alone supplies no default exploration policy.

PSD.8:4.5 - Challenge coverage and stop proportionately

Ask whether the set still reflects only one favored formulation, one available technology, or one powerful participant’s concern. Check whether a materially different mechanism, genuine no-change case, compatible combination, or bounded probe was omitted without reason. Merge labels that have the same decision-changing contents; retain differences that alter consequences or supported use.

Stop when the set is sufficient for the present comparison: material formulation differences have an addressed candidate or an explicit gap, each retained row is intelligible, protected-condition exclusions are visible, and additional search has no identified benefit worth the remaining effort. This is bounded sufficiency, not proof that all possible alternatives have been found.

If only one lawful direction survives, report that fact and its basis without manufacturing a rival. If none survives, return the missing qualification, infeasible requirement, or need to reopen the problem. A gap is a useful result; a decorative list is not.

PSD.8:4.6 - Return the set without making the choice

Return the question, subject and horizon; the exact candidate contents; their material differences; supported conditions and remaining gaps; excluded branches and reasons; and the observation that would add, remove, or change a candidate. Use the smallest readable form that lets another practitioner reconstruct those distinctions.

PSD.11 may use this set as the alternatives for its named consequence comparison. The comparison must still establish its own value, evidence, and scope basis. Use the set as an input to any further ranking or recommendation. The authorized chooser makes the choice. Any later programme or WorkPlan needs its own basis; support claims about performed work and achieved effects with evidence of those occurrences.

PSD.8:5 - Archetypal Grounding

PSD.8:5.1 - Flood-pump alternatives beyond a purchase contest

In this illustrative case, the board needs a pre-season return for the next flood season. The inquiry distinguishes nominal capacity, deployment reliability, unequal service, and downstream consequences. The model account says that nominal permanent and mobile capacity can meet the assumed inflow when the stated units are operating, but mobile arrival under road loss is not yet supported. Reachable assistance remains a separate service concern.

The inquiry turns those premises into three candidate descriptions and one unfinished proposal for staging:

The property-protection and reachable-assistance concerns remain distinct. They lead the team to ask whether each whole arrangement serves both; they do not establish an approved priority between them. No candidate is dropped because its proponent dissents from the majority.

Return N, F and M with their stated limits, and retain S as an unfinished proposal with a named construction question. The supported comparisons remain usable at their stated scope. If commitment-ready options are needed, identify the missing premise for M and the unfinished construction and qualification of S. Keep those gaps visible without claiming that the usable set exhausts all possibilities.

PSD.8:5.2 - A ninety-day development-direction question

An advisory team is asked which direction a service organization should consider for a ninety-day reliability horizon. “Train, outsource, or use AI” is not yet a set of comparable directions. The adviser resolves the labels into internal development with covered service duties, a qualified provider arrangement, and a mixed human–tool arrangement with specified oversight and fallback. A bounded mixed-arrangement probe is a separate candidate when its information and operating consequences differ from deployment.

Each branch needs its own supplier result. Human capability evidence does not establish transfer to the representative later Work; provider evidence does not establish interface or security fit; model evaluation does not establish reliability of the mixed arrangement. If the organization-allocation comparison is missing, return that exact gap rather than ranking the three labels.

For advice about one person, the same move generates directions only from qualified human and target-Work premises. For an AI arrangement, it distinguishes parameter, data, scaffold, tool, code, and environment changes only where the case makes those objects live. Neither application imports the other’s mechanism or evidence.

PSD.8:5.3 - Cheap non-use

A recipient already has two complete, qualified ways of obtaining the same repair result and asks which to choose. Use the existing set and the applicable comparison or C.11 choice guidance. Another brainstorming exercise adds no candidate-changing result.

PSD.8:6 - Bias-Annotation

Scope: alternatives for bounded decision-support engagements. Lenses: Prag tests useful differences; Onto/Epist separates proposed arrangements from facts; Arch exposes combinations and dependencies; Gov preserves protected conditions and later authority; Did replaces label lists with intelligible candidates.

Incumbency, sponsor anchoring, technology availability, and novelty bias can each shrink or distort the set. Challenge the omitted mechanism and baseline, not merely the number of ideas. Counter the opposite bias toward endless variety by asking what additional candidate could actually change the present comparison.

PSD.8:7 - Conformance Checklist

• The recipient question, holder or subject, current arrangement, horizon, and separate choice boundary are recoverable.
• Formulations, models, and inquiry claims contribute only where they change the candidates.
• Alternatives differ in decision-changing contents, not merely names.
• The no-change case includes its actual continuing obligations and consequences.
• Combinations and staged directions expose interactions, delay, and unresolved enabling conditions.
• Supported, proposed, and unknown premises remain distinguishable.
• Qualification gaps and excluded branches have exact reasons; missing alternatives are not fabricated.
• The stopping point states bounded sufficiency, not exhaustive search.
• The returned set permits a later comparison without asserting selection, authority, Work, or benefit.

PSD.8:8 - Common Anti-Patterns and How to Avoid Them

PSD.8:9 - Consequences

The recipient gets a genuinely wider but finite decision question, with candidate gaps visible before scoring. The cost is some additional construction and qualification effort. Concentrate it on omitted differences that could change the decision; do not describe every possible arrangement in equal detail.

PSD.8:10 - Rationale

Structured inquiry becomes useful to choice when its differences change what can be done. Alternative construction preserves those differences while qualification prevents imagination from becoming an unsupported commitment. Keeping generation separate from comparison permits a promising proposal to remain investigable without calling it a winner.

PSD.8:11 - SoTA-Echoing

PSD.8:12 - Relations

• PSD.3 supplies formulation differences for candidate formation, not selected actions. PSD.5 supplies discriminating model claims, not the obtaining conditions they represent. PSD.7 supplies shared and contested inquiry claims only where they change the set; dissent remains explicit.
• PSD.11 may consume the candidate set for the same named comparison. It establishes its own comparison result; generation does not select.
• C.17, C.18, C.19, and C.38 supply characterization, generation stewardship, live-pool policy, and same-result construction only under their own use conditions.
• A.15.9 supplies bounded use of an outside-practice result and selection of a worthwhile further request. Direct holder and domain practices supply feasibility, mechanisms, protected conditions, and evidence.
• C.11 governs the later local choice over an adequate option set. A missing or incompatible input returns to its qualified direct source or remains an exact gap; no neighboring body is a compulsory prerequisite.

PSD.8:End

PSD.9 - Represent Values and Trade-Offs

Type: DPF pattern body Status: Candidate

Primary working result: a decision-usable value account: attributed concerns and objectives, their consequence measures, protected conditions, admitted trade-offs, unresolved disagreements, and limits for one named comparison.

PSD.9:1 - Problem frame

Use this when a scorecard’s criteria came from a template, “importance” weights have no stated meaning, or the same benefit appears under several headings. Also use it when people agree that reliability, development, safety, or fairness matters but mean different consequences for different subjects.

Begin with one concern: important to whom, about which subject and situation, and why? Trace it to a consequence that could distinguish the live alternatives. Then state how that consequence will be represented and whether it may be traded against another. The gain is a comparison whose value assumptions can be understood and challenged.

The governed object is the value account for that comparison. An objective expresses what is wanted; a measure describes a characteristic; a preference orders consequences; a protected condition limits permissible trade-offs. They can be related without becoming the same thing. Neither an expressed preference nor a numerical weight supplies authority to waive a duty or another person’s rights.

Do not use this pattern when a current, qualified value account already answers the exact comparison question. Use the direct measurement practice for a missing measurement alone, the appropriate authority or domain practice for a condition’s current force, and C.11.DUA for a disputed requirement’s justification. Use the authorized choice owner for the later decision. This pattern does not determine universally correct values.

PSD.9:2 - Problem

Criteria can appear neutral while deciding the result. “Install more pumps” embeds an action in an objective. “Service quality” may count the same avoided outage again under reliability, satisfaction, and reputation. Equal weights may silently favor the concern represented by the largest number of criteria.

Numbers can conceal a second substitution. A budget amount, a probability, an ordinal judgement, and a protected condition become interchangeable entries in a spreadsheet. Normalizing each to zero–one does not establish comparable value. A mean of participants’ weights can erase a disagreement about who bears the consequence or what may be traded at all.

PSD.9:3 - Forces

PSD.9:4 - Solution

Recover the values behind the decision, organize them around consequences, and declare only the measurement and trade-off structure that the receiving comparison can support. Keep unresolved preferences and protected conditions visible rather than completing a score by assumption.

PSD.9:4.1 - Recover whose concern changes the comparison

Name the subject, affected people or Systems, configuration, horizon, and receiving question. Use PSD.2’s participation and concern account where it supplies relevant attributed concerns, duties, interests, missing voices, or representation limits. That input is not already a value model or a mandate to aggregate preferences.

For each material concern, ask who expresses or bears it, what consequence matters, and under what conditions. Recover an actual assignment, local system-role classification, or authority relation only where the concern’s meaning or governing force depends on it. A title such as resident, manager, or expert does not establish representation or decision rights.

If a needed concern or binding condition is unavailable, use a qualified direct source or return the exact gap. Do not treat non-response as indifference. Distinguish participants’ current statements from the analyst’s proposed interpretation and from an established obligation.

PSD.9:4.2 - Distinguish ends, means, and repeated consequences

Ask “Why does this matter here?” to identify the consequence sought. Ask “How might it be achieved?” to expose possible means. “Provide training” may be one means; reliable performance in representative later Work may be the relevant end. The distinction is local to the question: a process experience can itself be valued when participants actually care about it.

Organize objectives only as far as the structure helps. For a small decision, a few attributed statements may be enough. A hierarchy or means–ends map is useful when several levels or overlaps would otherwise be lost.

Test apparent duplicates through their meaning and consequence path. Avoid counting one consequence twice under different names. But statistical correlation alone is not duplication: service loss and distribution of that loss can remain different values even when their observed measures covary. Conversely, statistical independence does not prove that a preference model may add the values.

Retain an objective only if it represents a material value, protected condition, or decision-changing distinction. When simplifying, state the lost distinction and check that it cannot reverse the intended comparison. Do not delete a concern merely because it is difficult to measure.

PSD.9:4.3 - Give each measure a usable meaning

For every consequential measure, state the characteristic, subject or participant tuple, scale and unit where applicable, direction of preference, horizon, source, and missingness rule. Distinguish a direct measure from a proxy and say what the proxy cannot establish.

Use C.16 for measurement and A.19 when a declared multi-characteristic space or reusable predicate is needed. A.19 supplies coordinate and scale meanings; it does not perform scoring, aggregation, comparison, or selection. A number missing its subject or scope is not repaired by placing it in a common column.

Keep raw consequence descriptions alongside any value transformation that the comparison uses. A performance scale and a value scale answer different questions. If an ordinal judgement is used, preserve its ordering without assuming equal intervals or averaging categories. If a numerical value function is used, state the consequence range, anchors, interpolation or shape, and the elicitation basis that makes the transformation meaningful.

PSD.9:4.4 - Separate conditions from compensable objectives

Identify which conditions are binding, which are aspirations, and which are uncertain claims requiring a competent result. Record the source and use of each condition. A participant’s request for a minimum service level is a value claim; a separately established legal or safety requirement has its own governing basis.

Do not compensate for a failed protected condition by adding benefits elsewhere. If its meaning, applicability, or authority is disputed, retain that dispute and ask for the exact interpretation rather than choosing a convenient threshold. A comparison may proceed on an explicitly narrower slice while the whole-decision conclusion remains blocked.

When the live question is whether the requirement itself should be retained or changed, use C.11.DUA §4.3 with the competent domain contribution. Identify the protected person or System and interest, unwanted outcome, governed quantity or activity, conditions and horizon. Distinguish background, attributable increment and total exposure where they affect the judgement. Examine the causal and measurement basis, uncertainty, threshold or precision choice, marginal protection, full burden and displaced protective work. Compare retention, tightening, revision, replacement or removal only where they are meaningful alternatives. A safety label does not supply that basis, and expense alone does not defeat a protective requirement.

Return the supported requirement recommendation and the reason or limit the recipient needs, together with its present force, amendment authority and feasible time window. The appraisal can finish even when amendment is unavailable; the currently binding condition still constrains action. State a resulting impasse when no acceptable alternative or timely amendment is feasible. A later correction does not restore an already lost opportunity. Use this return only for the disputed requirement; an adequate ordinary value account needs no new appraisal.

Some thresholds are preference choices rather than prohibitions: an aspiration level, budget preference, or tolerated inconvenience. Say which they are and whose judgement they express. A threshold crossing is not automatically a decision or permission to act.

PSD.9:4.5 - Elicit trade-offs over consequences, not criterion labels

Before assigning weights, ask which concrete consequence profiles the value holder prefers and why. For an additive value model, a weight concerns the value of an improvement over a stated consequence range, not the abstract importance of the criterion’s name. Changing that range can require elicitation again.

Test whether a proposed compensatory model fits the expressed preferences. If one consequence’s value depends on another, retain that interaction or use a suitable model. If a participant refuses the trade-off, do not encode refusal as an extreme but negotiable weight unless that faithfully represents the judgement.

Several forms can be useful: qualitative preference statements, a priority order, threshold rules, an additive or non-additive value model, or an outranking relation that can preserve incomparability. Choose the least burdensome form that preserves the decision-changing distinction. The domain Method supplies its elicitation and validity conditions; naming MCDA does not satisfy them.

Keep each materially different value account attributable. A common account requires an explicit and legitimately governed way to combine or reconcile the judgements. Voting, averaging, or a sponsor’s preference is not a default aggregation rule. Where several preference models remain compatible with the expressed judgements, retain that family rather than fitting one arbitrary point estimate.

PSD.9:4.6 - Return the account and its exact incompleteness

Return the attributed concerns and objectives; consequence meanings and measures; protected conditions and their sources; admitted trade-offs or preference relations; material interactions and dissent; unsupported transformations; and what would change the account. When a requirement’s merits were in question, include the bounded appraisal return and the limit imposed by its current force from §4.4.

PSD.11 may use it only for the named comparison. The account can support a partial order or leave a comparison unresolved. Missing preference information is not automatically missing empirical evidence: a further experiment may estimate consequences without deciding how they should be valued.

Recognition needs only a material ambiguity, duplication, or unexplained trade-off. Consequential reliance additionally needs qualified measurements, faithful elicitation, a justified aggregation Method when used, direct authority for binding conditions, and the applicable domain assurance. A readable value table satisfies none of those stronger claims by itself.

PSD.9:5 - Archetypal Grounding

PSD.9:5.1 - Two meanings of flood service

In the illustrative flood-pump engagement, a residents’ association emphasizes property protection, while a separately heard group of mobility-constrained residents emphasizes reachable assistance. The board is the later choice owner, not an assumed representative of every value judgement.

The analyst replaces a generic “service quality” score with this account:

The analyst removes a second “reliability benefit” entry that merely repeats the same pumping-service hours. Reachable assistance stays separate even if failures often occur in the same storms. That is not duplicate value.

If the board adopts a trade-off between operating-service hours and budget units for a narrow analytical slice, the account names that value judgement, range, and limit. It does not present the slice as the residents’ common value function. If the association and the other group reject a common trade-off, the return carries separate accounts and a stated disagreement; another hydraulic simulation cannot resolve that disagreement.

PSD.9:5.2 - Development directions do not share a universal improvement score

For the ninety-day service-organization case, a qualified strategy result gives reliability priority over throughput for the current horizon. That premise helps frame the comparison but does not supply numerical weights or a causal effect estimate.

The adviser keeps those premises in their own meanings. A common service-level comparison is possible only after qualified domain results connect each direction to that same service and horizon. Without that connection, “human 4, organization 4, AI 4” is not a meaningful equal score. The return requests the missing consequence relation rather than normalizing the three numbers.

PSD.9:5.3 - Cheap non-use

Two qualified replacement parts have the same relevant consequences except for a directly comparable resource cost, and the authorized recipient’s cost preference is already explicit. Reuse that account. An objectives hierarchy and a fresh weighting workshop would add no value distinction.

PSD.9:5.4 - Retain a protective restriction or revise a redundant control

These constructed variants concern a service team’s proposed use of an external inference provider. In the first, a qualified configuration result shows that the proposed route exposes identifiable confidential incident records to provider staff who have no part in serving those clients. An available internal route meets the current service need within its support budget. The restriction prevents that disclosure; relaxing it for the faster external route would expose those clients without a corresponding needed service gain. The value account therefore supports retaining the restriction and excludes this external route for the current use. It does not infer that all provider configurations are unsuitable.

In the second variant, the configuration and access protection remain adequate. The disputed rule additionally requires three hours of manual transcription of an access log. Assume the competent review has established that the retained, inspectable electronic log covers the same events and that transcription adds no omitted event or distinct check. The same three hours would otherwise test a newly exposed, unreviewed access path to the same protected records. On these facts, retaining the extra transcription displaces more protective work without an identified protective gain. Recommend revising that requirement to use the qualified electronic record while keeping the actual access controls. If a missing event or an independent check is found, that premise changes the recommendation.

The rule owner cannot amend the transcription requirement before this decision. The recommendation is still complete, but it is not an exemption: present options must satisfy the rule or remain deferred. The lost testing opportunity remains a consequence of the present constraint. The contrasted results follow from the stipulated contribution and burden, not from the words security, digital or redundant.

PSD.9:6 - Bias-Annotation

Scope: value representation for one bounded comparison. Lenses: Onto/Epist separates concern, measure, preference, and obligation; Prag preserves decision relevance; Gov exposes representation and authority; Did makes trade-offs concrete.

Template bias imports irrelevant criteria. Proxy bias rewards what is easy to count. Splitting one objective into many criteria can change its apparent importance. Sponsor averaging can conceal who bears a loss. Counter these by returning to attributed consequences, inspecting overlaps, and retaining disagreement and missingness. Do not replace one template with a mandatory elaborate hierarchy.

PSD.9:7 - Conformance Checklist

• Values are attributed to the relevant subjects and receiving comparison, with representation limits intact.
• Objectives and possible means remain distinct at the grain that changes the decision.
• Repeated consequences are not counted twice; correlation alone does not justify deletion.
• Measures retain subject, scale, unit, horizon, evidence, proxy limits, and missingness.
• Binding conditions, aspirations, and unresolved authority questions are distinguished. A live merits question receives an appraisal of protective contribution and burden, with a supported recommendation and unchanged current force.
• Value transformations and weights have declared ranges and an elicitation basis.
• Interactions and refusals to compensate are preserved.
• Any collective aggregation has an explicit basis; incompatible accounts remain visible otherwise.
• The return states partiality, dissent, direct-source gaps, and exact reopen conditions.
• A value account is not a comparison result, authorization, or claim of effect.

PSD.9:8 - Common Anti-Patterns and How to Avoid Them

PSD.9:9 - Consequences

The comparison becomes open about what it values and what it cannot exchange. Simplifying the account can reduce burden without losing material distinctions. Some decisions remain partially ordered or disputed; that is a truthful result, although it may be less convenient than a single score.

PSD.9:10 - Rationale

Value representation makes consequences decision-relevant without confusing description with preference or preference with permission. Concrete trade-off questions expose assumptions hidden by criterion labels. Preserving multiple admissible accounts lets later comparison show where a conclusion is shared and where it depends on a disputed judgement.

PSD.9:11 - SoTA-Echoing

PSD.9:12 - Relations

• PSD.2 may supply the participation and concern account that changes the value question. That contribution is not already a weight set or a collective mandate.
• PSD.11 consumes the value account only for the named comparison. The account does not silently scalarize or authorize its result.
• C.16 governs measurements; A.19 supplies a declared characteristic space or predicate when needed. Scoring, aggregation, comparison, and selection remain separate direct operations.
• Direct ethics, law, safety, governance, finance, and holder practices supply the particular conditions and claims they own. A.15.9 helps obtain a missing qualified contribution without transferring that authority.
• If a required value or source premise is absent, stale, or incompatible, use a qualified direct result or return its exact gap. A completed model, candidate list, or workshop does not fill it by adjacency.

PSD.9:End

PSD.10 - Represent Decision-Relevant Uncertainty and Evidence Limits

Type: DPF pattern body Status: Candidate

Primary working result: bounded decision claims and unresolved discriminating questions: what the evidence supports about the live alternatives, what could change that comparison, and which uncertainty cannot presently be resolved.

PSD.10:1 - Problem frame

Use this when a point estimate, “high confidence” label, or model output makes a decision look more settled than its evidence permits. Also use it when a long uncertainty list does not say which unknown could reverse, narrow, defer, or invalidate the decision-support return.

Take one relied-on claim and ask: if this claim were different within its supported limits, what would change about these alternatives or their admissibility? State the supported claim and the remaining question together. The gain is a useful uncertainty account, not the impossible removal of all uncertainty.

The governed object is that decision-linked account. A claim about an uncertain consequence, an attributed belief, a model assumption, missing evidence, and a disputed value are different inputs. Their relevance to one decision does not turn them into one probability or a common confidence score.

Do not use this pattern when the only question is a source’s provenance or currentness and no decision-support comparison changes; use A.10 or the direct source practice. If the uncertainty account already supports the present use, reuse it. Direct domain practices retain their own measurement, forecasting, causal, safety, and evidential conclusions.

PSD.10:2 - Problem

A numerical estimate can hide the conditions under which it is meaningful. An access model may estimate arrival time only when the road is open; a training study may concern an immediate test rather than later Work; an AI evaluation may concern a previous version or operating distribution. Averaging the results does not repair their missing applicability.

Conversely, a demand for certainty can stop every useful return. Some uncertainty cannot change the ordering, while another can show that all alternatives fail a protected condition. A useful account distinguishes those cases. It also separates a question that better evidence can answer from a disagreement about values or authority that evidence alone cannot settle.

PSD.10:3 - Forces

PSD.10:4 - Solution

Connect each material uncertainty to the exact claim and decision it can change. Use a representation justified by the available knowledge, retain dependencies and limits, and return a bounded claim, discriminating question, narrowed use, or blocker.

PSD.10:4.1 - Start from a comparison that could change

Name the subject, configuration, horizon, receiving question, considered alternatives, and result currently being claimed. Ask which premise could change their consequences, relative standing, eligibility, or the need for a probe. If the alternatives themselves are unclear, return that candidate question.

Use PSD.5’s model account only where its evidence or assumptions bear on this same configuration and horizon. The model can expose an uncertainty without resolving it. A current qualified direct result can supply the same premise without requiring a model-building exercise.

Check both relative and absolute consequences. An uncertainty shared by all alternatives can leave their order unchanged yet show that none meets a required service or safety condition. Do not dismiss it as irrelevant merely because it is not a ranking discriminator.

PSD.10:4.2 - Represent what is unknown at its actual kind

Choose a form that answers the live question without claiming more knowledge than exists.

These are use choices, not a universal taxonomy of uncertainty. Different forms may coexist in one account. Distinguish a physical or behavioral variability claim from uncertainty about its model, data, or applicability whenever the distinction changes the return.

If a probability is useful but unsupported, state the conditional comparison it would enable and identify the needed basis. Do not assign equal probabilities to scenarios simply to make an expected-value calculation run.

PSD.10:4.3 - Qualify the relied-on claims

For each decision-bearing source result, keep the claim, subject, supplying result kind, source edition or effective window, assumptions, evidence, intended use, exclusions, and material dissent recoverable. Use A.10 for the actual bounded reliance question; its disposition does not establish the source claim’s truth or authorize the decision.

Ask whether the evidence concerns the same holder, intervention, environment, and horizon. Separate observed results, forecasts, expert judgements, and unsupported extrapolations. An observation of a benefit is not automatically a causal effect; the direct causal or domain Method supplies that support.

Use an already-qualified result within its limit. If a consequential cross-practice result is still missing, A.15.9 supports the smallest request or blocker. Do not ask another practice to “remove the uncertainty”; ask for the specific claim, bound, interpretation, or test that could change this comparison.

PSD.10:4.4 - Preserve dependency and model disagreement

Recover shared data, common causes, conditional assumptions, and other dependencies when they affect the consequence comparison. Evidence repeated by several models is not several independent confirmations. Expert or model aggregation needs its own justified Method; the number of voices alone does not determine a probability.

Keep incompatible assumptions separate until a direct result supports their combination. For example, a scenario with a failed access route and a scenario with a functioning route can test different claims; combining their most favorable outcomes produces no realizable case.

Where alternative models disagree, identify the overlapping proposition and what explains the difference: scope, input, representation, mechanism, or unresolved evidence. A new measurement may discriminate the models; sometimes the honest answer is that the present use must retain both. Do not turn disagreement into a narrow average solely because a downstream table expects one number.

PSD.10:4.5 - Form a discriminating question

Write the question in terms of its possible consequences for the current return:

For this subject and horizon, establish whether this premise lies inside the region supporting alternative A, outside it, or remains unresolved; state the evidence and limits needed for that use.

The requested result may concern eligibility rather than ranking. It may also show that no available alternative works, that a different formulation is needed, or that only a reversible analytical use is supported.

Name a feasible observation, calculation, interpretation, or comparison that might answer the question, its supplying practice, and the relevant time or access limit. If no feasible inquiry can answer before the decision window closes, say so. Do not promise that more data will settle structural ignorance.

This pattern identifies decision-linked questions. PSD.12 can later examine reversals and information priorities; C.11 or the direct choice owner decides whether an actual next probe is worth its cost and authorized. A question with high uncertainty is not automatically the best probe.

PSD.10:4.6 - Return the strongest supported claim and no stronger

A short return states:

• what claim about which alternatives is supported, for which configuration and horizon;
• its uncertainty representation, source limits, and dependencies;
• what different answer could change the comparison, admissibility, or receiving use;
• the exact unanswered question or blocker; and
• what source, observation, candidate, value, or configuration change would reopen the account.

Return “unchanged within the tested bounds” only when those bounds cannot alter the stated result. Return a conditional or narrowed claim when support covers only part of the use. If a required protected-condition premise is unsupported, preserve the direct domain stop rather than compensating with confidence elsewhere.

Recognition may begin with one unexplained estimate. Consequential reliance requires the evidence and assurance demanded by the direct practice, including its independent checks when applicable. This pattern supplies no universal evidence score or acceptable uncertainty threshold.

When a relied-on source actually changes, revalidate the affected use. Use G.11 for a currentness question and A.10.1 when the changed claim must be traced through several actual uses. Do not discard unrelated claims merely because they share a source file.

PSD.10:5 - Archetypal Grounding

PSD.10:5.1 - Which flood-pump uncertainty matters now?

In the illustrative pre-season inquiry, nominal permanent and mobile capacity meets the assumed inflow only with the stated units operating. The model omits arrival delay. The team cannot turn that conditional result into “mobile service is reliable”.

If a direct deployment result later supports a bounded arrival range, the account changes only the affected claim and its uses. If the range still spans service failure, the result is a discriminating question for robustness, not an unconditional feasibility claim. If all arrangements share an unsupported power-supply assumption, that common uncertainty can invalidate all of them even while their relative order stays fixed.

PSD.10:5.2 - Development evidence with three different limits

For a ninety-day organization recommendation, suppose the adviser has an immediate human assessment, a queue model for the current team, and an offline AI benchmark. Each can inform a different bounded claim.

The human assessment does not establish retention or transfer to later service Work. The queue model does not establish the performance of a reallocated or mixed arrangement without its staffing and interaction premises. The benchmark does not establish current-version service reliability under the operating distribution and oversight arrangement.

The return names three possible supplier questions at their own grain: representative later-Work capability, changed-arrangement service consequences, and exact-version operating evaluation. Only questions that could change the live recommendation are pursued. Averaging the three “confidence” labels would repair none of these gaps.