ExplicitTradeOffDisclosure [rule] v1.0.0

When any design or implementation decision degrades UX quality, information architecture clarity, or accessibility compliance, the trade-off must be named explicitly in the design rationale or PR description — with the sacrificed quality named and at least one alternative presented.

Severity

warning

Applies When

Any design or implementation decision that reduces accessibility, UX clarity, IA coherence, or interaction quality compared to the recommended approach.

Verify By

Confirm that design notes or PR description names the specific quality being traded away and at least one alternative that would not require the trade-off.

ExplicitTradeOffDisclosure [rule] v1.0.0

When any design or implementation decision degrades UX quality, information architecture clarity, or accessibility compliance, the trade-off must be named explicitly in the design rationale or PR description — with the sacrificed quality named and at least one alternative presented.

Severity

warning

Applies When

Any design or implementation decision that reduces accessibility, UX clarity, IA coherence, or interaction quality compared to the recommended approach.

Verify By

Confirm that design notes or PR description names the specific quality being traded away and at least one alternative that would not require the trade-off.

Rationale

Making trade-offs visible keeps quality degradation intentional and auditable rather than accidental. An undisclosed trade-off becomes invisible technical or design debt — later reviewers cannot tell whether the degraded quality was deliberate or an oversight.

Severity

warning

Applies When

Any design or implementation decision that reduces accessibility, UX clarity, IA coherence, or interaction quality compared to the recommended approach.

Verify By

Confirm that design notes or PR description names the specific quality being traded away and at least one alternative that would not require the trade-off.