Search words, quoted phrases, and exact IDs across the current corpus.
By default, all meaningful words must match the same source passage, in its text or titles. Matching ignores letter case. Ordinary word queries skip common English function words such as the, and and or; quotes keep a phrase, and uppercase operators control matching.
| Example | What it does |
|---|---|
controlled variation | Requires both meaningful words; their order may differ. |
"controlled variation" | Requires adjacent words in that order. |
SYSE.24:4 | Prioritizes the exact named section. Pattern IDs also work. |
engineering OR management | Matches either alternative. Write OR and AND in uppercase. |
engineering AND (research OR management) | Requires engineering together with either grouped alternative. |
engineering -management | Excludes passages that match management. |
title:"controlled variation"body:"controlled variation" | Restricts the phrase to section/publication titles, or to source text. A field prefix applies to the following term or phrase. |
"controlled variation"~1 | Allows one intervening word in the phrase. |
"controlled vari"* | Requires adjacent words, with the last word as a prefix. |
engineering^2 OR management | Gives engineering matches more ranking weight. |
The Publication, Suite and Type filters narrow the same query. Results are source passages, not generated answers. Search does not translate, expand synonyms or automatically correct spelling. For a task expressed in another language, try English terms and read the context. Press / to focus the search field.
PSDA.2 - Set and Reopen the Problem Boundary Type: Method pattern body Status: Stable Primary working result: a usable problem scope and reopen basis for one bounded receiving inquiry: the formulations, participants, affected Systems, concerns, relations,…
In PSDA.2 - Set and Reopen the Problem Boundary
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. PSDA.2 contributes that PSM-specific judgement and preserves the conditions under…
In PSDA.2 - Set and Reopen the Problem Boundary
… directly. PSDA.2 adds no problem-structuring judgement. 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…
In PSDA.2 - Set and Reopen the Problem Boundary
PSDA.2:12 - Relations PSDA.11 supplies the identity and authority boundary of a professional engagement when one is involved. PSDA.12 supplies participation, concern, and affected-System challenges where those professional results are needed. PSDA.1 supplies…
In PSDA.2 - Set and Reopen the Problem Boundary
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. PSDA.2 adds no problem-structuring…
In PSDA.2 - Set and Reopen the Problem Boundary
PSDA.2: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…
In PSDA.2 - Set and Reopen the Problem Boundary
… the scope. Use A.2.6 only when a receiving claim depends on exact U.ContextSlice membership in a declared U.Scope…
In PSDA.2 - Set and Reopen the Problem Boundary
… outside is false, irrelevant forever, or unaffected. Do not use PSDA.2 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…
In PSDA.2 - Set and Reopen the Problem Boundary
PSDA.2: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…
In PSDA.2 - Set and Reopen the Problem Boundary
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…
In PSDA.2 - Set and Reopen the Problem Boundary
… 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…
In PSDA.2 - Set and Reopen the Problem Boundary
PSDA.2: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…
In PSDA.2 - Set and Reopen the Problem Boundary
PSDA.2: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,…
In PSDA.2 - Set and Reopen the Problem Boundary
PSDA.2: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…
In PSDA.2 - Set and Reopen the Problem Boundary
… 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. PSDA.2 governs the field-specific judgement that a problem…