Physical Constraint Design For Impossibility¶

Make the wrong action physically impossible, materially rejected, or harder than the correct action.

Version: v1 · 2026-08-24 · History
Solution archetype #: 754
Problem family: Correctness, Conformance & Formal Validity Failure
Problem subfamily: Feasibility & Requirement Consistency

This repaired draft fills the missing queue-position-17 output bundle for uploaded scaled_gap_fill_batch_006. The archetype preserves the physical-action-space version of error_proofing_poka_yoke: redesign the system so the wrong action cannot normally be completed.

When This Archetype Applies¶

Partial catalog groundingSome structural conditions are represented by existing abstractions, but no sufficient condition set is fully represented.

Diagnostic problem

A recurring harmful action remains available in the action space, so prevention depends on vigilance, instruction, reminders, inspection, or after-the-fact correction rather than on the structure of the system itself.

Applicability expression3 distinct conditions

Training-resistant recurring errorandWrong action easierandLate defect detection

Algebraic1∧2∧3

2=2₁?2₂?2₃

2₁=a∨b

2₂=a∨b

2₃=a

′ context guard? connective not recorded∅ no catalog witness yet

groundedpartly groundedopen

3 conditions, all required.

3Required in every casenumbered 1–3

These hold no matter which pattern applies.

1

Training-resistant recurring error · open

The same wrong assembly, connection, sequence, medication, handoff, or configuration recurs despite training.

and — also required

2

Wrong action easier · 3 cases · 3 matched

The incorrect action is physically¹ similar to, easier² than, or more available than the correct action.

This predicate enumerates 3 cases · 3 matched

1
incorrect action is physically similar to correct action
matched to the catalog
Established by any one of these 2
a
domainMode Error— The interaction failure in which the same user action is interpreted differently by a system depending on a hidden mode the user does not perceive — the user acts correctly for the mode they believe is active, and the system, in the actually active mode, does something else.
or — any one of these establishes this case
b
domainTouch-Target Miss— Reclassify a mistyped tap from operator error to interface defect by reading the miss rate off the mismatch between a control's target geometry and the operator population's motor precision — a geometric scan Fitts's Law makes quantitative.
Case 1 of 3 — what it requires — 2 requirements, all needed
All of
- roleA correct action and a corresponding incorrect action are both available in the action space.
- comparisonThe incorrect action is physically similar to the correct action.

?how these combine is not recorded

2
incorrect action is easier than correct action
matched to the catalog
Established by any one of these 2
a
domainConfirmation Fatigue— The interaction-design failure where a blocking confirmation prompt fires so often, and so rarely marks a truly consequential choice, that users develop an automatic dismiss reflex that discharges the prompt without reading it — leaving it syntactically present but informationally inert.
or — any one of these establishes this case
b
domainGolden Hammer Anti-Pattern— Diagnose a team applying its familiar technology to a poorly-fitting problem because the acquisition cost of an alternative is visible while the misfit cost is diffuse and downstream, so fluency reshapes what counts as the right tool before fit is ever asked.
Case 2 of 3 — what it requires — 2 requirements, all needed
All of
- roleA correct action and a corresponding incorrect action are both available in the action space.
- comparisonThe incorrect action requires less effort or is easier than the correct action.

?how these combine is not recorded

3
permissive interface enables incorrect action
matched to the catalog
Established by
domainMode Error— The interaction failure in which the same user action is interpreted differently by a system depending on a hidden mode the user does not perceive — the user acts correctly for the mode they believe is active, and the system, in the actually active mode, does something else.
Case 3 of 3 — what it requires — 3 requirements, all needed
All of
- roleAn interface mediates access to a known incorrect action.
- polarityThe interface is permissive with respect to the incorrect action.
- causalityThe permissive interface enables or makes physically available the incorrect action.

Within a case the abstractions are alternatives — any one establishes it. How the 3 cases combine with each other is not recorded in the source; the predicate reads as an alternation, but polarity can flip that reading, so it is marked ? above rather than guessed.

and — also required

3

Late defect detection · open

Downstream inspection finds the defect only after cost, delay, risk, or irreversible harm accumulates.

Other requirements and context (3)

Why these sit outside the expression

Supporting context — it may accompany or help interpret the situation, but it is not a load-bearing condition in a sufficient diagnostic set.

Solution feasibility — it describes whether the intervention can work, not whether the diagnostic problem exists.

Source review — the source wording is not structurally clear enough to support a formal trigger role without clarification.

Supporting contextThe task is performed under time pressure, fatigue, interruption, low visibility, high cognitive load, or handoff ambiguity.
Solution feasibilityThe error class has a clear material, spatial, sequence, fit, access, or default-state signature that can be redesigned.
Source reviewThe target accepted prime is error_proofing_poka_yoke and direct accepted coverage is absent in the scaled queue.

Coverage

1 of 3 conditions grounded · 2 open.

Read the methodology Download the trigger-logic data

Drafting note¶

The draft explicitly records boundary risk with Self-Checking Operation and the pilot physical_poka_yoke_self_check variant. It remains a full draft here because the batch progress log already recorded queue position 17 as drafted_full_archetype and the checkpoint-after-25 repair request asked to generate the missing full output bundle.

Compression statement¶

Physical-Constraint Design for Impossibility turns error prevention into action-space design. It identifies a harmful or invalid action, maps the physical and procedural degrees of freedom that currently allow it, and then changes shape, fit, order, interlock, default state, material path, access route, or effort gradient so the undesirable action is blocked before judgment, memory, training, or after-the-fact inspection must save the system.

Canonical formula: error_impossibility = hazard_action × action_space_map × constraint_insertion × fit_or_sequence_rejection × bypass_control × operational_validation

Abstractions this archetype builds on — directly (a source ingredient) or as a related pattern. Links follow the typed catalog namespace.

Built directly on (1)

Error Proofing (Poka-Yoke): Error prevention.

Also references 20 related abstractions

Access Control: Restrict system access.
Cognitive Load And Attentional Capacity
Constraint: Limits possibilities to guide outcomes.
Controllability: Ability to steer system.
Data Integrity: Accuracy and consistency preserved.
Decision: Committing to one alternative from a set under uncertainty and trade-off, collapsing open deliberation into a chosen path and foreclosing the others.
Design for Implementation: Real-world feasibility.
Fail-Safe: Default to safe state on failure.
Feedback: Outputs influence inputs.
Human-Centered Accommodation: Adapt to human limits.

▸ Show 10 more

Variants¶

Narrower or domain-specific specializations that share this archetype's core structure. Recognized variants are established; candidate variants are provisional.

Accessory Coupled Configuration Completion · implementation variant · recognized

Attach a mode-specific internal reconfiguration element to the accessory that enables that mode, making configuration completeness automatic.

Distinct from parent: The parent blocks harmful actions generally; this variant makes an otherwise omissible, mode-specific internal configuration unavoidable by coupling it physically to the accessory that enables the mode.
Use when: A circulating material stream needs a mode-specific diversion feature that would obstruct other operating modes if left installed.
Evidence (strong independent recurrence confirmed): US8857145B2; Air Baffle for AMC Filler Modules, Compact

Interlock Human Or Material Access With A Recorded · implementation variant · recognized

Interlock human or material access with a recorded decontamination sequence so the containment boundary opens only after verified completion.

Distinct from parent: Physical-Constraint Design for Impossibility owns removing harmful actions from the normal action space; this variant binds boundary opening to verified completion of a protective sequence.
Use when: Opening a containment boundary before a required decontamination sequence completes can expose people, materials, or adjacent space to an invisible hazard.
Evidence (strong independent recurrence confirmed): US12036549B2; SafePass door opens only after completed sterilization cycle; Priorclave double-ended autoclave door-control sequence

Editorial Notes¶

Problem Classification¶

Classification: Correctness, Conformance & Formal Validity Failure → Feasibility & Requirement Consistency

Problem kernel: harmful action remains physically feasible

Rationale: Earliest causal condition: A recurring harmful action remains available in the action space, so prevention depends on vigilance, instruction, reminders, inspection, or after-the-fact correction rather than on the structure of the system itself.

Independent corroboration: The earliest necessary condition in the frozen evidence is: A recurring harmful action remains available in the action space, so prevention depends on vigilance, instruction, reminders, inspection, or after-the-fact correction rather than on the structure of the system itself. That is a feasibility requirement and invariant consistency problem because Required constraints, guarantees, relations, or necessary conditions are absent, mutually incompatible, intrinsically impossible, or unenforceable together within the stated scope.

Review outcome: Independent reviewer agreement; high confidence.