Efficiency optimization must not change the default path’s result, only the cost of reaching it

What it is

Shortcuts, templates, bulk operations, autofill, and accelerated paths should compress steps, waiting, and input without silently changing object scope, defaults, validation, permissions, logs, or final data. The optimization boundary requires a fast path and ordinary path to produce explainably equivalent results for the same intent.

Why it happens

Efficiency features often come from different entries and may copy stale defaults, skip validation, change ordering, merge requests, or use another time base. When users verify through the slow path and then execute in bulk through the fast path, any difference becomes a silent error. Safety rules belong in a shared service layer; interface shortcuts change expression and step count while preserving attribution and audit.

Where it stops holding

Some efficiency designs do narrow scope, such as “bulk-delete only the current filtered set,” but the difference must be explicit and confirmed, not implicit drift. Performance optimization may delay, merge, or execute asynchronously; the time at which results take effect must be visible. Different permission paths may expose different actions; that is authorization difference, not default-path drift.

Applying it

• For every shortcut, define input, scope, defaults, validation, permissions, output, logs, and failure semantics.
• Put business rules in a shared service called by all entries; the interface only changes interaction cost.
• Before execution, show scope summaries such as “current 24 items” or “using template T3 defaults.”
• Use equivalence tests to compare slow path, shortcut, template, and API results, notifications, undo, and audit.

Related

• Same group: B3.15.1 An accelerator’s value rises with frequency of use; infrequent functions do not merit shortcuts · B3.15.2 Personalization weakens teachability; users can no longer guide one another with the same language · B3.15.3 The system should recognize proficiency and proactively suggest faster paths
• Nearby: B2.26 Directness and Indirection Trade-offs · R2 Engineering Delivery
• Search terms: optimization boundary · operation equivalence · default path