PSD.4 - Set and Reopen the Problem Boundary

Type: DPF pattern body Status: Candidate

Primary working result: a usable problem scope and reopen basis for one bounded receiving inquiry: the formulations, participants, affected Systems, concerns, relations, conditions, horizons, and intervention families included now; material exclusions and unknowns; the basis the recipient needs to judge the cut; and observable conditions for widening, narrowing, or otherwise revising it.

PSD.4:0 - Use This When

Use this pattern when a decision-support 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 PSD.3 when plural formulations imply different boundaries.

Choose the smallest boundary that supports the named receiving decision or Work, make consequential exclusions visible, and state how the boundary can reopen. The practical gain is an actionable scope without pretending that what lies outside is false, irrelevant forever, or unaffected.

Do not use PSD.4 merely to decide whether one exact U.ContextSlice belongs to an already-declared U.Scope; use A.2.6 for that claim. Do not use it for generic document scope, organizational jurisdiction, a System boundary owned by a direct engineering practice, or a static project charter when no problem-structuring question remains. Return to PSD.1 if the receiving use or engagement identity itself is unclear.

PSD.4:0.1 - Working Distinctions

Working term	Meaning in this pattern
engagement boundary	The `PSD.1` 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. It need not be exhaustive or permanent.
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.

PSD.4:1 - Problem frame

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.

The primary concern is not to find the one true perimeter. It is to choose and expose a boundary adequate for one receiving use while preserving the exclusions and observations that could require revision. Recognition can begin with one plausible boundary reversal. Consequential inclusion, exclusion, relation, harm, authority, legal, ethical, safety, or factual claims retain their direct assurance.

PSD.4:2 - Problem

An implicit sponsor boundary hides who and what the inquiry sacrifices. A comprehensive “whole system” map creates the opposite failure: every related condition enters, no stopping rule survives, and the receiving decision disappears. An exact scope declaration can conceal that the underlying inquiry cut remains contestable.

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.

PSD.4: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.

PSD.4: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.

PSD.4:4.1 - Fix the receiving use and current formulations

Recover the subject, recipient, receiving decision or Work, horizon, and choice owner from the current PSD.1 engagement question or a qualified direct source for the same inquiry. Name the PSD.3 formulations whose consequences the boundary must preserve. Use one adequate current formulation directly when plural formulations are unnecessary. Keep a materially contested exclusion or boundary reason in the scope where it can change the receiving use.

Use a current PSD.2 account where participants, affected Systems, concerns, duties, interests, dissent, representation limits, or possible consequence paths can challenge the cut. Inclusion in that account does not require inclusion in every current model or analysis; exclusion from the boundary does require an honest reason when material. When an input needed for the cut is unavailable, stale, or incompatible, obtain a qualified direct result or return the exact missing premise. A formulation alone does not establish current representation or choice authority.

PSD.4:4.2 - State the boundary through decision-bearing dimensions

Name only dimensions that can change the receiving use:

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 cut in ordinary language; add an exact U.Scope declaration only when the receiving use needs it. A boundary is not justified by drawing a box or using the word “system”.

PSD.4:4.3 - Keep material exclusions and unknowns alive

For every omitted item that could change a downstream result, record the item, exclusion reason, current evidence or uncertainty, consequence of being wrong, and reopen observation. Distinguish:

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.

Items with no plausible consequence for the current use need not receive a full record. Items that can reverse a high-consequence result require proportionate direct assurance or an explicit stop.

PSD.4:4.4 - Challenge the cut before accepting it

Apply the smallest relevant challenges:

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: what smallest observation would make the current result unusable or materially different?

Repair only the affected dimension. A challenge does not require maximal widening.

PSD.4: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. Unknown means the available basis cannot decide; obtain the missing input, narrow the attempted use, or abstain instead of asserting exclusion. Changing the extension creates a new scope; a refit that preserves the extension does not.

Do not force every ordinary concern or participant into U.Scope. PSD.4 governs the field-specific judgement that a problem boundary is usable for the current 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.

PSD.4:4.6 - Return the usable scope and reopen basis

Return the scope in the smallest form that answers the current question. Keep the following content where it changes the recipient’s understanding or reliance; a local clarification can finish in the scope itself.

Result position	Content needed by the recipient
receiving use	Subject, recipient, decision or Work, horizon, and retained choice owner.
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	Observable triggers and the dimension to widen, narrow, replace, or re-formulate.

If no defensible boundary is available, return the exact missing premise, blocker, narrowed claim, or abstention. Do not hide the stop by expanding the map.

PSD.4: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.

Widen, narrow, or replace only that portion. If a declared U.Scope or a relied-upon membership result changes, apply A.2.6; if the engagement identity or receiving use changes, return to PSD.1; if a new formulation is needed, return to PSD.3.

PSD.4:4.8 - What changes in practice

The practitioner stops treating scope as either the sponsor’s box or an ever-growing map. They can state a small usable cut, defend why exclusions are tolerable now, and show the precise observation that would reopen each consequential part.

PSD.4:5 - Archetypal Grounding

PSD.4: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 all four PSD.3 formulations rather than reducing the inquiry to pump count.

Long-term watershed redesign and permanent residential relocation are outside the current investment return, but they are not declared irrelevant. 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 is usable for model and alternative work. It does not authorize funding, assert that every included consequence obtains, or make the emergency board competent to settle legal, ecological, or safety questions.

PSD.4:5.2 - Narrowing after a failed generalization

An incident-response inquiry initially covers all product lines. Evidence shows that the proposed escalation pattern applies only to 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.

PSD.4: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. PSD.4 adds no problem-structuring judgement.

PSD.4: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 returns: “Examine this week’s authorized checks, their staffing and access dependencies, and the late returns.” This scope answers the local question; it needs no new rival-formulation inquiry or separate explanation of why PSD.3 was not used.

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. This added limitation serves the new receiving use; it does not undo the supported weekly scope or authorize operation.

PSD.4:6 - Bias-Annotation

Scope: provisional problem boundaries for a named decision-support use. Lenses: Gov keeps inclusion, jurisdiction, and choice authority separate; Arch exposes dependencies on the cut; Onto/Epist distinguishes situation, formulation, ordinary boundary, declared U.Scope, and evidence; Prag seeks the smallest usable scope; Did makes exclusions and reopen cues readable without a specialist notation.

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.	Require each included dimension to change the receiving use.
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.

PSD.4:7 - Conformance Checklist

The boundary is tied to one receiving use, subject, horizon, and authority boundary.
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 bearer, formulation, action, evidence, authority, and reversal challenges were applied proportionately.
The result carries the reason for the cut where the receiving use needs it, including any materially contested exclusion.
Ordinary problem-boundary judgement is not confused with exact U.ContextSlice membership in U.Scope.
Missing premises produce a gap, narrowed claim, request, blocker, or abstention.
Reopening changes the smallest affected dimension and identifies dependent results.
The scope neither authorizes the later choice nor displaces direct legal, ethical, safety, scientific, engineering, or governance practices.

PSD.4: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.”	Separate true or false membership from an unknown evaluation; unknown does not establish exclusion.
“Scope was agreed at kickoff.”	Reopen when the named observation can change the receiving result.

PSD.4:9 - Consequences

The inquiry becomes bounded enough to support models, alternatives, comparison, and recommendation while keeping consequential omissions recoverable. Revision can be local rather than a complete restart. The cost is explicit exclusion work and occasional narrowing, widening, or stopping when a premise cannot be assured.

PSD.4:10 - Rationale

Problem boundaries are practical framing commitments. A discovered perimeter or exact membership test alone does not establish that a cut is adequate for a receiving inquiry. PSD.4 contributes that PSM-specific judgement and preserves the conditions under which the cut must change. A.2.6 remains the direct owner of exact contextual membership when that stronger claim is needed.

PSD.4: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: `PSD.4:4.1`–`4.4` and `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: `PSD.4: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.

PSD.4:12 - Relations

PSD.1 supplies the engagement identity and authority boundary. PSD.2 supplies participation, concern, and affected-System challenges. PSD.3 supplies the plural formulation set whose differences the boundary must preserve.
PSD.5 and PSD.6 receive the scope and formulation basis for modeling and PSM-arrangement questions. PSD.16 receives the scope and reopen basis for the inquiry result.
A.2.6 governs exact U.ContextSlice membership in a declared U.Scope when that claim is needed. A.1.CSD supplies 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. PSD.4 neither establishes those results nor authorizes the later choice.