QAEDA-TST-009 · procedural safeguard

Inspect intermediary chokepoints

Does the restriction operate through payments, hosting, app distribution, identity, network access, ranking, translation, or another intermediary in a way that obscures who is responsible and what process applies?

Pass condition

What a defensible proposal should be able to show.

The proposal identifies the initiating and executing actors, lawful authority, specific mechanism, appeal path, alternatives, and whether the intermediary is meaningfully replaceable.

Warning signs

Signals that the proposal is drifting.

  • Responsibility is split so no actor accepts accountability for the restriction.
  • A financial or infrastructure dependency makes nominally voluntary enforcement effectively unavoidable.
  • The same restriction would face greater procedural scrutiny if imposed directly.
  • Users cannot tell whether a visibility or access loss came from law, platform policy, commercial risk, or technical failure.

Evidence to demand

What should exist before confidence rises.

  • Documented chain of authority or contractual responsibility.
  • Market and technical analysis of practical alternatives to the intermediary.
  • Notice and appeal records for affected speakers or users.
  • Evidence separating ordinary commercial enforcement from viewpoint- or state-driven pressure.
Failure mode

Indirect restriction can hide coercion, eliminate recourse, and convert concentrated infrastructure into an unreviewable speech-governance layer.

Decision discipline

No single passing test licenses the intervention.

Apply the full sequence. A defined harm does not excuse a weak nexus; a narrow mechanism does not excuse secret secondary use; an appeal process does not prove efficacy.