Physical Constraint Design For Impossibility¶
Make the wrong action physically impossible, materially rejected, or harder than the correct action.
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.
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
Related Abstractions¶
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.