PSDA.2 - Set and Reopen the Problem Boundary
Type: Method pattern body Status: Stable
Primary working result. A usable problem scope identifies what this inquiry includes, what it leaves out or uncertain, why that boundary suits the receiving use and what could justify changing it. Include the formulations, affected participants or Systems, concerns, relations, conditions, horizons and possible responses that matter to the question.
PSDA.2:1 - Problem frame
Use this pattern when an inquiry either expands toward everything connected with the situation or excludes a concern, bearer, relation, horizon, or intervention family that could reverse the usefulness of the result. Use it after or alongside PSDA.1 when plural formulations imply different boundaries.
Choose the smallest boundary that supports the required result. Identify consequential exclusions and the conditions under which the inquiry would need a different scope. The recipient can use that boundary and see which conclusions it leaves open.
For exact membership of a U.ContextSlice in a declared U.Scope, use A.2.6. Document scope, organizational jurisdiction, an engineering System boundary and a settled project charter have their own questions. If the receiving use remains unclear, establish it from available evidence or report the missing premise. Use PSDA.11 when the gap concerns a professional engagement.
PSDA.2:1.1 - Working Distinctions
| Working term | Meaning in this pattern |
|---|---|
| engagement boundary | The PSDA.11 boundary around the decision-support return, recipient, subject, horizon, receiving use, and authority. |
| problem boundary | The provisional cut that determines which formulations, bearers, concerns, relations, conditions, horizons, evidence, and intervention families are treated as material now. |
| material exclusion | An omitted or deferred item that could change the current result and therefore must remain visible with a reason, uncertainty, and reopen condition. |
| usable scope | The smallest current problem boundary adequate for a named next result and its assurance burden. Reconsider it if that use or its premises change. |
| reopen basis | An observable change or newly recoverable value that can make the current boundary too narrow, too broad, or otherwise unfit for the receiving use. |
U.Scope | A declared scope for exact U.ContextSlice membership, governed by A.2.6. An ordinary problem boundary need not be reified as one. |
Every formulation makes a cut. It foregrounds some participants, Systems, concerns, causal or modal paths, operating conditions, time horizons, evidence, and intervention families while leaving others outside. In ill-structured situations those cuts are often contested and revisable rather than simply discovered.
Choose or explain the boundary warranted for this use. Identify exclusions or observations that could require revision. One plausible change that would reverse the conclusion can justify examining the boundary. Establish consequential claims about inclusion, relations, harm, authority, law, ethics, safety or facts through the relevant practice.
PSDA.2:2 - Problem
A sponsor’s implicit boundary can hide which participants or concerns the inquiry leaves out. An unbounded map can consume the available effort before producing a usable result. A precise scope declaration can still leave its suitability for the inquiry in dispute.
Once models and data collection begin, their available variables make the boundary appear natural. Excluded concerns then vanish rather than remaining explicit deferrals. A later observation is treated as noise instead of evidence that the inquiry should widen, narrow, or change formulation.
PSDA.2:3 - Forces
| Force | Tension |
|---|---|
| Actionability | A current cut is needed to proceed, while premature closure can reverse the result. |
| Completeness | Wider scope can reveal consequences, while unlimited scope destroys affordability and accountability. |
| Explicit exclusion | Material omissions must stay visible, while a boundary register should not become an encyclopedia. |
| Stability and revision | Dependent work needs a current scope, while new evidence can legitimately reopen it. |
| Exact membership | Exact contextual membership sometimes matters, while ordinary problem boundaries need not become U.Scope values. |
| Authority | A boundary can inform later work, while it does not authorize the later decision or erase specialist jurisdiction. |
PSDA.2:4 - Solution
Set the problem boundary relative to one receiving use and one or more current formulations. Name what is included, material exclusions or unknowns, and the observable changes that can reopen the cut. Keep the reason for its adequacy where the recipient needs it to judge or use the scope. Use A.2.6 only when a receiving claim depends on exact U.ContextSlice membership in a declared U.Scope.
PSDA.2:4.1 - Fix the receiving use and current formulations
Recover the subject, receiving use and horizon from a source that fits this inquiry. Identify any recipient and any holder of a subsequent choice. A suitable PSDA.11 engagement account can supply those premises. Use the formulations whose differences matter, including results from PSDA.1 where relevant. An already adequate single formulation can support the scope. Retain any contested inclusion or exclusion that affects the answer or its grounds.
Use a qualified PSDA.12 account or other suitable evidence where affected participants, concerns, duties, interests, dissent, representation limits or consequence paths may challenge the cut. Explain material exclusions even when a concern appears in a participation account. If a necessary input is unavailable or incompatible, obtain an applicable result or identify the premise that remains unresolved. Establish current representation and authority from responsible sources where the inquiry relies on them.
PSDA.2:4.2 - State the boundary through decision-bearing dimensions
Identify the dimensions that can affect the answer or its grounds.
- subject, configuration, place, population, and operating condition;
- included formulations and affected bearers;
- concerns, duties, interests, relations, dependencies, and consequence paths;
- evidence interval, uncertainty, and time horizon;
- intervention, adaptation, restraint, and no-action families; and
- participating, receiving, implementing, and choice-authority positions where material.
Carry forward the object distinctions recovered with the concerns. If “business trip” names both remote repair and administrative provision, say which work this inquiry concerns and which dependencies it includes. A boundary around expense processing cannot support a conclusion that the remote repair was completed. Several concerns about one identified journey can instead share that object boundary.
State the boundary in ordinary language. Add a declared U.Scope when the receiving use requires an exact membership claim.
PSDA.2:4.3 - Keep material exclusions and unknowns alive
For a material exclusion, identify what was left out, why, the available evidence, the consequence of an error and what evidence could justify revisiting the cut. Keep the following distinctions where they affect the result.
- outside for this receiving use from irrelevant in general;
- deferred from rejected;
- unknown membership from supported non-membership;
- absent evidence from evidence of absence; and
- a practical stopping decision from a claim that no relation or consequence exists.
Give exclusions the attention their possible consequence warrants. A high-consequence result that could reverse needs appropriate assurance or a stated limit before reliance.
PSDA.2:4.4 - Challenge the cut before accepting it
Use the challenges that could expose a consequential error in this cut.
- bearer challenge: could a participant or affected System outside the cut undergo a material change?
- formulation challenge: would another retained formulation include a different mechanism, value, horizon, or intervention family?
- action challenge: does the cut make one alternative appear necessary by excluding feasible restraint, adaptation, or no-action branches?
- evidence challenge: are data availability or model convenience defining the boundary?
- authority challenge: does the cut silently transfer a duty, jurisdiction, implementation burden, or later choice?
- reversal challenge: which observation, if available, could change the conclusion or show that the scope is inadequate?
If the challenge exposes a defect, revise the affected dimension and the conclusions that depend on it.
PSDA.2:4.5 - Use exact scope membership only when needed
When a downstream claim depends on whether one exact U.ContextSlice belongs to one declared U.Scope, use A.2.6. Distinguish an evaluation result of true, false, or unknown. An unknown result means the available evidence does not settle membership. Use a suitable existing result, obtain a missing input when warranted, or report the limit or narrower conclusion. Changing the extension creates a new scope; a refit that preserves the extension does not.
PSDA.2 judges whether the problem boundary suits the inquiry. A.2.6 governs exact contextual membership. A C.2.3 formality threshold concerns how strictly a claim is expressed and is selected separately, only when the receiving use needs it.
PSDA.2:4.6 - Return the usable scope and reopen basis
Return the scope in the smallest form that answers the current question. Use the applicable entries below. A local clarification can finish with the scope itself.
| Result position | Content needed by the recipient |
|---|---|
| receiving use | Subject, receiving question or Work and horizon, with any recipient and holder of a subsequent choice. |
| formulation basis | Current formulations and the material differences the boundary preserves. |
| included scope | Bearers, concerns, relations, conditions, horizons, evidence, and intervention families included now. |
| exclusions and unknowns | Material omissions or uncertainties, reasons, consequences of error, and direct assurance still needed. |
| adequacy reason, where needed | Why this is the smallest usable scope, when the recipient needs that basis to judge the cut or avoid mistaking an exclusion for a settled fact. |
| dependent uses | Models, facilitation, alternatives, value treatment, comparison, recommendation, or inquiry results that consume the scope. |
| reopen basis | Conditions that would justify widening, narrowing, replacing or reformulating a dimension, and any observation that could establish them. |
If no defensible boundary is available, identify the premise that prevents a defensible cut and return the narrower supported conclusion or a reason to abstain.
PSDA.2:4.7 - Reopen locally and state what changed
Reopen when a new participant, affected System, concern, formulation, relation, operating condition, evidence result, value tension, intervention family, horizon, receiving use, or authority fact can change the current result. Name the old boundary, new observation, affected dimension, and dependent result.
When the new basis warrants revision, widen, narrow or replace the affected portion. Use A.2.6 if a declared U.Scope or relied-on membership result changes. Separate or revise the inquiry when the receiving use changes. Use PSDA.11 if new engagement terms are needed, and PSDA.1 if a missing formulation requires its work.
PSDA.2:4.8 - What changes in practice
The practitioner can return a boundary that fits the current use, explain consequential exclusions and show how a change in the evidence or question would affect the scope.
PSDA.2:5 - Archetypal Grounding
PSDA.2:5.1 - Flood-pump boundary
For the board’s pre-season decision, the current boundary includes the district pumping arrangement, permanent and mobile capacity, maintenance and staffing dependencies, deployment safety, district access, the next flood season, and material downstream transfer paths. It preserves the questions of capacity, unequal protection across districts and affected residents, maintenance and safe deployment from PSDA.1.
Long-term watershed redesign and permanent residential relocation are outside the current investment return, for this season. Relocation rights and downstream consequences remain material exclusions because they can reverse a recommendation. The boundary records that verified cross-district flood transfer, a safety limit outside the assumed operating envelope, or evidence that no feasible pump branch protects mobility-constrained residents will reopen the relevant dimension.
The result supports model and alternative work for the stated investment question. Claims that the consequences occur need evidence from the relevant setting. Funding, legal, ecological and safety determinations need the corresponding authority or specialist grounds.
PSDA.2:5.2 - Narrowing after a failed generalization
An incident-response inquiry initially covers all product lines. The available evidence supports the proposed escalation pattern for one regulated line and one staffing configuration. The practitioner narrows the problem boundary and dependent recommendation instead of claiming organization-wide use. Other lines remain explicit unknowns with their own reopen conditions.
PSDA.2:5.3 - Cheap non-use
A laboratory test claim already has a declared U.ClaimScope with population, configuration, and interval selectors. The live issue is whether one proposed test’s U.ContextSlice belongs to that scope. Use A.2.6 directly to evaluate that membership.
PSDA.2:5.4 - One adequate formulation and a consequential exclusion
An analyst and a maintenance lead already share the formulation “why are the authorized pump checks late?” Their immediate clarification is whether to examine this week’s check queue or expand into redesigning the whole maintenance organization. The available queue and assignment facts support the first cut. The analyst describes the scope as “this week’s authorized checks, their staffing and access dependencies, and the late returns.” This scope answers the local question.
A later board asks whether the same result establishes readiness for the flood season. Now the exclusion of uncompleted seasonal checks can change its decision. The returned scope must retain that those checks were outside the weekly lateness inquiry and that their readiness remains unestablished. The board needs the seasonal check result before relying on a readiness claim. The weekly scope remains suitable for the lateness inquiry. Establish seasonal readiness and authority to operate from their respective grounds.
PSDA.2:6 - Bias-Annotation
Scope. Judge the boundary chosen for a particular use. Distinguish inclusion from jurisdiction and from authority to choose. Identify the framing commitments, evidence and dependent work that matter to this cut. State exclusions and conditions for revision in language the recipient can use.
| Recurring bias | Likely drift | Repair |
|---|---|---|
| sponsor-boundary bias | The brief’s perimeter becomes unquestionable. | Challenge it with bearers, formulations, actions, evidence, authority, and reversal. |
| map-completeness bias | More nodes are treated as better scope. | Check how each included dimension affects the requested result or the grounds for relying on it. |
| data-availability bias | Available variables define the problem. | Record excluded concerns and evidence gaps independently of the model. |
| box-as-ontology bias | A drawn perimeter is treated as proof of a System boundary or exact scope membership. | State the ordinary decision-support cut; use the direct engineering practice for a System-boundary claim and A.2.6 for contextual membership when either is needed. |
| exclusion-as-falsehood bias | Outside the current inquiry becomes “does not matter”. | Record material exclusions, uncertainty, consequence, and reopen basis. |
| boundary-freeze bias | Later contrary evidence is absorbed without revising scope. | Reopen the smallest affected dimension and dependent results. |
PSDA.2:7 - Conformance Checklist
- The boundary is tied to one receiving use, subject and horizon, with the authority boundary stated where that use has one.
- Current formulations and material participation or affected-System inputs are recoverable.
- Included bearers, concerns, relations, conditions, evidence, horizons, and intervention families are stated only at the needed grain.
- Material exclusions and unknowns retain reasons, consequences of error, and reopen observations.
- The relevant challenges to bearers, formulations, actions, evidence, authority or reversal were applied in proportion to their consequences.
- The result carries the reason for the cut where the receiving use needs it, including any materially contested exclusion.
-
A claim about exact
U.ContextSlicemembership inU.Scopeuses its own evaluation when that claim is required. - The scope identifies material missing premises, any supported narrower claim and any missing input worth obtaining.
- Reopening changes the smallest affected dimension and identifies dependent results.
- Any attributed choice, authority or specialist judgement has the basis required by its legal, ethical, safety, scientific, engineering or governance practice.
PSDA.2:8 - Common Anti-Patterns and How to Avoid Them
| Anti-pattern | Repair |
|---|---|
| “Everything is connected, so include everything.” | Include only what can change the named receiving use; preserve material exclusions and triggers. |
| “Outside scope means irrelevant.” | State outside-for-now, consequence of error, and reopen condition. |
| “The model boundary is the problem boundary.” | Let formulations and concerns challenge available variables and model convenience. |
| “Draw the system boundary.” | Name the problem-structuring cut; establish any System-boundary or exact contextual-membership claim through its direct pattern. |
| “Unknown means excluded.” | Report true, false or unknown according to the evidence for the declared scope. |
| “Scope was agreed at kickoff.” | Reopen when the named observation can change the receiving result. |
PSDA.2:9 - Consequences
A usable scope can answer its own inquiry or support further models, alternatives, comparisons and recommendations. Revising a material exclusion takes effort, but the change can often be confined to the conclusions that depend on it. An unsupported premise can require narrowing the answer or stopping.
PSDA.2:10 - Rationale
A problem boundary expresses which considerations matter to the receiving inquiry and why. Establish its suitability and the conditions that would justify changing it. For a separate claim of exact contextual membership, use A.2.6.
PSDA.2:11 - SoTA-Echoing
| Practice question | Best-known line | Serious alternative or default | Defect overcome and pattern mutation | Source roles and limits | Reopen condition |
|---|---|---|---|---|---|
| How should a problem boundary remain useful and revisable? | Treat framing as a contextual selection of what matters, compare materially different cuts, state exclusions, and revise the boundary when new evidence changes the receiving use. | A fixed sponsor scope is the serious default; an unbounded whole-situation map is the opposite default. | The first suppresses consequential exclusions and the second cannot stop. Adapt: PSDA.2:4.1–PSDA.2:4.4 and PSDA.2:4.6 require decision-bearing dimensions, material exclusions, proportionate challenges, and the scope reason needed by the receiving use. | Kelly and Gero’s 2022 framing review, Litster, Cardoso, and Hurst’s 2024 mapping study, and Nickel, Hurst, and Duimering’s 2024 contextual trade-off study support explicit framing, externalized change, and contextual trade-offs. They establish neither one framing ontology, universal Method, shared frame, fixed boundary, prevalence, causality, nor superiority. | Reopen if later field evidence changes the best-known boundary practice or if new contextual evidence changes an included or excluded dimension. |
| When does a receiving use need exact contextual scope membership? | Keep ordinary inquiry cuts in plain language; use current A.2.6 only when the receiving use must decide whether one exact U.ContextSlice belongs to one declared U.Scope. | Treating every diagram box or topic perimeter as a declared exact scope is the serious default. | It substitutes apparent precision for boundary judgement and can hide unavailable evaluation. Adopt: PSDA.2:4.5 distinguishes true, false, and unknown evaluation results and routes extension changes to the direct pattern. | Current A.2.6 supplies exact contextual membership, extension change, and refit discipline. Its applicability axis is independent of C.2.3 formality. It does not judge which participants, concerns, formulations, intervention families, or exclusions make a PSM boundary usable. Direct engineering, legal, safety, ethical, and governance practices retain their own boundaries and thresholds. | Reopen if the direct scope pattern gains the complete problem-boundary judgement at equal or lower effort, or if a relied-upon scope or membership result changes. |
PSDA.2:12 - Relations
PSDA.11supplies the identity and authority boundary of a professional engagement when one is involved.PSDA.12supplies participation, concern, and affected-System challenges where those professional results are needed. Use a single adequate formulation or the material differences in a plural set fromPSDA.1when the scope depends on them.PSDA.3andPSDA.4receive the scope and formulation basis for modeling and PSM-arrangement questions.PSDA.17receives the scope and reopen basis for resolving material interference among simultaneous work contributions in a decision-support engagement.A.2.6governs exactU.ContextSlicemembership in a declaredU.Scopewhen that claim is needed.A.1.CSDsupplies consequence-bearer challenges; exact relations remain with their direct governor.- Direct evidence, legal, ethical, safety, scientific, engineering, governance, assignment, and authority patterns govern their own claims. Use their results where the boundary depends on a specialist claim or a later choice.