Abuse Complaint and Appeals Process¶
Grievance-and-remedy process — instantiates Bottleneck Power Governance
Gives affected parties a reviewable channel to challenge denial, degradation, or retaliation — surfacing abuse, adjudicating it, and escalating through a ladder of remedies.
An Abuse Complaint and Appeals Process is the reactive enforcement channel that lets those who depend on a bottleneck contest how they are treated — a denial of access, a quiet degradation, a retaliatory cutoff, an unfair term. Its defining role is to be the live grievance loop that makes the substantive duties real: where the rules state what the controller owes, this process is how a wronged party forces the question and obtains a decision, a reason, and a remedy. It has three moving parts — complaints that double as a detection signal for abuse and exclusion, an independent authority that hears and decides with a right of appeal, and a ladder of escalating remedies. It enforces duties; it does not define them.
Example¶
A lawful online merchant is abruptly cut off by the dominant payment gateway it relies on — no reason given, and no alternative processor reaches its customers. It files a complaint. The process requires the gateway to state its grounds within a set window and to show its evidence; the merchant is given the chance to respond. An independent reviewer — not the gateway's own trust-and-safety team — decides, issues a written reason, and offers a route of appeal. Because that reviewer sees many such complaints, a pattern of cutoffs hitting one merchant category surfaces as a detected exclusion signal rather than a string of isolated events. Remedies escalate along a ladder: reinstatement plus a reasoned-notice requirement first; then, for repeat or bad-faith conduct, penalties and mandatory advance-notice terms. The governing standard throughout is natural justice — notice, a hearing, reasons, and an impartial decision-maker.[1]
How it works¶
- Treat intake as a monitor. Complaints aggregate into a detection signal for patterned abuse and exclusion, not merely one-off fixes.
- Shift the burden and require reasons. The controller must justify its action on the record, rather than the complainant proving a negative.
- Adjudicate independently, with appeal. Decided by someone insulated from the controller, with a route to escalate a wrong decision.
- Escalate along a remedy ladder. Proportionate and rising: reinstatement and reasoned notice, then penalties, then referral for a structural remedy when abuse persists.
Tuning parameters¶
- Adjudicator independence — internal ombudsman versus external tribunal; more independence resists capture but costs more and moves slower.
- Burden of proof placement — how much the controller must justify versus the complainant must establish.
- Remedy-ladder steepness — how fast sanctions rise on repeat conduct; too shallow invites repeat abuse, too steep deters legitimate refusals.
- Interim relief — whether access is restored while the case is decided — decisive when a cutoff is existential.
- Standing and cost — who may complain and how cheaply; a high cost silences the small complainants who most need the channel.
When it helps, and when it misleads¶
Its strength is unique among these mechanisms: it gives the affected party agency — a duty with no complaint channel is unenforceable — and its aggregated complaints surface patterns a periodic screen would miss. Its weaknesses are speed and resourcing, the risk that a captured or timid adjudicator rubber-stamps the controller, and retaliation that deters people from complaining at all. The classic misuse is a complaints process built for show — long queues, no interim relief, non-independent reviewers — that manufactures the appearance of due process while defeating it in fact. The discipline is independence, reasons on the record, interim relief, and treating the complaint stream as a monitoring dataset rather than a queue to clear.[1]
How it implements the components¶
oversight_appeal_and_remedy_authority— it is the independent authority that hears the grievance, decides it, and grants a right of appeal.abuse_and_exclusion_monitor— aggregated complaints are the detection signal for patterned exclusion and abuse.remedy_ladder— it applies proportionate, escalating remedies from reinstatement through penalties to structural referral.
It enforces duties it does not write: what counts as wrongful denial or an unreasonable term is set by Essential Facility Access Rule and Common Carriage Obligation, and watching for regulator capture is Regulatory Capture Audit's job, not this channel's.
Related¶
- Instantiates: Bottleneck Power Governance — the channel through which affected parties enforce the regime's duties.
- Consumes: Common Carriage Obligation and Essential Facility Access Rule — it adjudicates against the substantive duties they define.
- Sibling mechanisms: Common Carriage Obligation · Essential Facility Access Rule · Market-Power Screen · Regulatory Capture Audit · Structural Separation or Unbundling · Competition or Antitrust Remedy
Notes¶
This process detects and remedies, but it cannot cure a structural problem. When the same patterned abuse recurs across many resolved complaints, that is itself a signal to escalate — to structural separation or a stronger antitrust remedy — which live outside this channel. Read the complaint record as evidence, not just as cases to close.
References¶
[1] Natural justice is the principle that a party facing an adverse decision is entitled to notice, a fair hearing, reasons, and an impartial decision-maker — captured in the maxim audi alteram partem, "hear the other side." Cited as the standard the process must meet, not as a claim about any specific tribunal. ↩