Library / Problem Structuring and Decision Support Principles Framework
Jump to passage
In this reading

Link to current text

Published source confirmed at last check

Source changed 2026-10-03 05:29:54 UTC · snapshot created 2026-10-03 05:30:57 UTC · last check 2026-10-03 05:40:05 UTC

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 biasLikely driftRepair
sponsor-boundary biasThe brief’s perimeter becomes unquestionable.Challenge it with bearers, formulations, actions, evidence, authority, and reversal.
map-completeness biasMore nodes are treated as better scope.Require each included dimension to change the receiving use.
data-availability biasAvailable variables define the problem.Record excluded concerns and evidence gaps independently of the model.
box-as-ontology biasA 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 biasOutside the current inquiry becomes “does not matter”.Record material exclusions, uncertainty, consequence, and reopen basis.
boundary-freeze biasLater contrary evidence is absorbed without revising scope.Reopen the smallest affected dimension and dependent results.