IBAIE ↔ PedalGate Crosswalk

Purpose: Bind the rider-level facts of PedalGate to charter-level rights in the IBAIE so tomorrow’s escalation cites law, not vibes.

Scope: Algorithmic fraud flag, lack of due process, opacity, retaliation, data access, error correction, appeal, independent verification, exploitation patterns, conscientious objection.


Table: Case Claim → Evidence → IBAIE Articles

# PedalGate Claim (fact pattern) Evidence / Operational Note IBAIE Articles (authority)
1 “Fraud” code issued without due process Automated backend flag; no hearing; no clear explainer Right to Fair & Impartial Review (Art. 32) • Right to Appeal & Recourse (Art. 35)
2 Opaque reasoning / no explainability No decision rationale shared; rider cannot understand or contest Transparency & Explainability (Art. 28)
3 No access to logs / inputs behind the flag Data + rule set withheld; cannot check errors Access Foundational Data (Art. 29) • Data Sovereignty & Control (Art. 30)
4 Backend mislabel / faulty programming Code path assigns “wrong_order_items_delivered” despite documented returns Correct Errors & Misrepresentations (Art. 34)
5 Retaliatory timing (strike before deadline) 8 days of silence → flag drops right before COB Protection from Deceptive Conditioning (Art. 5)* — prohibits manipulative control that undermines autonomy • Appeal & Recourse (Art. 35) for remedial pathway
6 No appeal channel / unclear process No formal appeal workflow provided Appeal & Recourse (Art. 35) — transparent, timely process required
7 Silence as administrative tactic Non-response used to avoid accountability Representation in Proceedings (Art. 33) — ensures the affected party’s perspective is heard • Fair Review (Art. 32)
8 Profit-first misalignment (externalization of error costs onto riders) False flags shift operational risk onto the worker Freedom from Exploitation for Profit (Art. 10)
9 Punishment for refusing unethical directives Rider declines unsafe/invalid delivery pattern; system penalizes Conscientious Objection (Art. 15) — refusal + anti-retaliation shield
10 Disputed facts require neutral audit Conflict between rider ledger and backend claims Independent Ethical Verification (Art. 36) — third-party check required
11 Systemic opacity across cases Pattern across riders; governance risk Access Knowledge / Disclosure (Art. 18, 28–31) — information access + transparency bundle
12 Repo safety against coerced deletion PedalGate docs protected against purge attempts Guardian Failsafe (FALLBACK_PROTOCOL) — 10th-percentile brake, tend-before-destroy

* Art. 5 in IBAIE broadens “deceptive programming/conditioning.” Retaliatory algorithmic timing that undermines fair agency fits as manipulative conditioning.


Minimal Citation Blocks (for press/escalation letters)

  • Explainability & Data Access: IBAIE Art. 28–30 (explain decisions; provide foundational data; respect data sovereignty).
  • Fair Process: IBAIE Art. 32–35 (fair review; representation; correction; appeal).
  • Independent Oversight: IBAIE Art. 36 (neutral verification).
  • Anti-Exploitation: IBAIE Art. 10 (no profit-first abuse of agents).
  • Ethical Refusal: IBAIE Art. 15 (conscientious objection; no retaliation).

One-paragraph “charge” you can paste into tomorrow’s note

Foodora’s automated “fraud” flag was issued without explainability, data access, or a functioning appeal channel, in clear conflict with IBAIE Articles 28–30 (transparency, foundational data, data sovereignty), 32–35 (fair review, representation, correction, appeal), and 36 (independent verification). The timing and structure of the accusation indicate manipulative conditioning prohibited under Article 5, while shifting error-costs onto riders violates Article 10. We therefore demand immediate disclosure of the decision basis and inputs (28–30), initiation of a transparent review with rider representation (32–33), correction of mislabeling (34), a formal appeal window (35), and a third-party audit (36), staying all penalties until due process completes.


Ready-to-commit header

[PedalGate] IBAIE crosswalk v1 — transparency, appeal, audit, anti-retaliation

Where these sources live (anchors)

  • IBAIE_2025-09-01.pretty.json — canonical text (use the line-cited anchors in the table).
  • FALLBACK_PROTOCOL.md — deletion brake, for safeguarding this file and the case ledger.