Methodology

1. Overview

RAQEB is an open platform for monitoring online electoral discourse. It detects potential issues across major platforms and public broadcast feeds, routes them to trained reviewers for human verification against electoral law and editorial guidelines, and publishes verified findings to a public dashboard with full evidence and an audit trail.

This page describes how that works in detail — what we collect, how we analyze it, how we verify it, what we publish, and the principles that govern every step.

2. Data sources

RAQEB monitors content that is either publicly accessible or licensed for analysis. We do not scrape, do not collect private content, and do not track individual users.

Licensed platform content

• Major social platforms (Meta, X) via licensed content API access. Content is pulled in structured batches under the terms of the platform's content licensing agreement.
• Public WhatsApp channels — only the channels that are publicly accessible by design.

Public broadcast and press

• TV and radio broadcasts via public feeds and transcripts
• Online press articles
• Published opinion polls and official electoral commission data

Official electoral content

• Public statements, speeches, and posts from official accounts of candidates, parties, and electoral bodies
• Meta Ad Library and equivalent public political advertising disclosures

Submissions

• Observer reports and citizen submissions submitted through structured intake forms (with safeguards described under Privacy)

All sources, per deployment, are documented and disclosed openly. Each deployment publishes its own source list as part of its public methodology.

3. Per-deployment data isolation

Each adopting organization operates an independent deployment of RAQEB. The data ingested for one deployment is isolated from every other deployment.

What that means in practice

• A deployment's data is stored in a dataset dedicated to that deployment
• That dataset is not shared, mixed, or cross-queried with any other deployment's data
• The adopting organization's team has access to their deployment; access controls are configured by them
• The shared methodology governs how data is analyzed and published; it does not pool the data itself

This isolation is structural, not just policy. It ensures each deployment's adopting organization controls its own monitoring environment under its own oversight.

4. AI detection — what the models do

RAQEB uses AI models to surface signals from the volume of monitored content. The role of the AI is detection and scoring, not judgment. Models do not publish findings.

What the models are trained on

• The electoral law and regulatory guidance of the deployment's context (silence-period rules, campaign-period rules, disclosure requirements, broadcaster obligations)
• Editorial framing and language guidelines used by RAQEB reviewers (how to describe potential issues without overclaiming)
• Known patterns of electoral issues: silence-period violations, coordinated narrative amplification, manipulated media, sponsored content lacking disclosure, false claims about voting procedures
• Linguistic context across Arabic, English, and French (with additional languages added per deployment as needed)

What the models do

• Classify content against the trained categories
• Assign a confidence score to each detection
• Cluster related content (e.g., coordinated posting patterns, narrative repetition)
• Surface candidates for human review

What the models do not do

• Decide whether a finding is published
• Assign legal labels (no "FALSE," no "BREACH," no fixed verdict labels)
• Replace human judgment at any stage

5. Confidence scoring

Every AI detection is assigned a confidence score. The score reflects the model's certainty that the content matches the pattern it was trained to detect — nothing more.

The score is one input into a routing decision. It does not determine whether anything is published. High-confidence detections still go to human review. Low-confidence detections may still be reviewed if the issue type or sensitivity warrants it.

Confidence thresholds are configurable per deployment and per issue type. They are documented openly in each deployment's published methodology.

6. Escalation routing — multi-dimensional

When the AI surfaces a candidate finding, it is routed to a verification track based on four dimensions, not a single severity score:

Routing tracks include

• Standard review — single reviewer applies framing guidelines, confirms or dismisses
• Dual review — two reviewers must independently confirm before publication
• Senior reviewer escalation — sensitive or high-severity findings go to a senior reviewer
• Editorial board escalation — findings with legal implications or potential public-interest weight are reviewed by the editorial board before publication

This multi-dimensional routing is the practical mechanism that ensures nothing is published without proportionate review.

7. Qualified language — by design

RAQEB does not adopt fixed verdict labels (FALSE, MISLEADING, BREACH, etc.). This is a deliberate editorial discipline that protects both accuracy and liability.

Instead, findings are described in qualified language that reflects what the evidence actually supports:

This is not hedging. It is editorial accuracy. RAQEB is not a court, an electoral commission, or a fact-checking authority that issues definitive verdicts. We document, verify, and publish — leaving determinations of legal breach to the bodies empowered to make them.

When a finding is later confirmed, updated, or refuted, the public record is updated and the change is logged.

8. Reviewer guidelines

Trained reviewers operate under documented guidelines covering:

Framing

• How to describe a finding without overstating its meaning
• How to attribute claims to their source rather than making them in RAQEB's voice
• How to handle content involving named individuals with appropriate care

Verification

• How to cross-check a claim against original sources
• How to confirm the authenticity of media (image metadata, broadcast logs, platform-level timestamps)
• How to identify coordinated behavior versus organic amplification
• When to escalate rather than confirm or dismiss

Language

• Use qualified language at all stages of documentation
• Use the source's own words when quoting; do not paraphrase in a way that changes meaning
• Apply the same standard to all sides, regardless of political affiliation

Dismissal

• When a detection does not meet the verification standard, it is dismissed and logged
• Dismissals are tracked to refine the AI's training over time

Senior reviewers handle escalations and apply heightened care to sensitive findings. An editorial board reviews findings with broader legal or public-interest implications.

9. What gets published vs. what is held

Not every verified finding is published immediately. Publication criteria:

Published

• Findings confirmed by the required number of reviewers
• Findings mapped to a documented issue type
• Findings supported by evidence accessible to readers

Held

• Findings where verification is incomplete
• Findings where evidence cannot be made public without compromising a source
• Findings under editorial review for sensitivity or legal implications

Never published

• Personally identifying information beyond what is already public
• Private content (private messages, non-public posts, restricted-access material)
• Submissions without sufficient evidence to support qualified language

Holds are logged internally. They are not concealed — adopters can review what was held and why.

10. Audit trail

Every published finding carries a public audit trail that includes:

• Source — the original content, with a link or archived reference
• Detection details — when it was surfaced, what AI track flagged it, the confidence score
• Review chain — which reviewers handled it, what verification steps were applied, escalation history if any
• Editorial decisions — any language changes between draft and publication, with timestamps
• Updates — any revisions made after publication, with the reason and date

The audit trail makes RAQEB's process inspectable. A reader, an adopter, a journalist, or an electoral body can trace any finding from public record back to its original signal.

11. Privacy principles

RAQEB monitors public discourse, not individuals. Our privacy principles:

What we do

• Aggregate analysis of public content
• Pattern and trend detection across volumes of posts
• Narrative clustering and amplification analysis
• Verification of public claims against evidence

What we do not do

• Track individual user behavior over time
• Collect personally identifying information beyond what is already public
• Publish private account details, personal communications, or restricted content
• Use monitoring data for any commercial purpose

Submissions and sources

• Citizen and observer submissions are handled with care for source protection
• A submitter's identity is not published unless they explicitly choose to be named
• Sensitive submissions are routed to senior reviewers; submitters are informed of how their report will be handled

Data retention

• Each deployment publishes its own data retention policy as part of its methodology

12. Non-partisanship

RAQEB is non-partisan. The methodology applies the same standard to every actor monitored — candidates, parties, broadcasters, official accounts, independent commentators — regardless of political position or affiliation.

The platform does not endorse, oppose, or recommend any candidate, party, or political position. Findings represent data-driven documentation of what occurred in the monitored discourse, mapped against the regulatory and editorial standards of the deployment.

Adopting organizations operate under the same non-partisanship principle. Eligibility criteria for adoption require organizations to operate independently of political parties and to commit to monitoring all actors under the same standard.

13. Limitations and caveats

RAQEB is rigorous, but it is not infallible. Honest limitations:

• AI models miss things. Detection coverage is high but not complete. Some issues will surface in the discourse without being flagged by the models.
• Human review can disagree. Two reviewers may reach different conclusions on the same finding. Dual-review and editorial escalation mitigate this but cannot eliminate it.
• Findings are not legal judgments. Whether something constitutes a breach of electoral law is a determination for the relevant electoral authority or court — not for RAQEB. We document; they decide.
• Findings may be updated. As evidence develops, a published finding may be revised, expanded, or — rarely — withdrawn. The change is logged publicly.
• Coverage is bounded by data access. RAQEB monitors what is publicly accessible or licensed. Content on closed platforms or in private channels is outside our scope by design.
• No real-time guarantee. AI detection and human verification take time. RAQEB is fast, but not instant. Some patterns become visible only with hours or days of accumulated signal.

Stating limitations openly is itself part of the methodology.

14. Update policy

Published findings may be updated when new evidence becomes available.

• Minor corrections (typos, source link updates) are made without notice; the change date is logged.
• Substantive revisions (changes to the language of the finding, additional evidence, reassessment) are flagged with a visible "Updated" note and a brief description of what changed.
• Withdrawals (a finding that the editorial board determines should not have been published, or that has been refuted by subsequent evidence) are flagged with a visible "Withdrawn" note. The original finding remains visible with a strikethrough and a link to the explanation.

The update history of every finding is preserved. RAQEB does not silently edit the record.

15. Contact and corrections

Anyone affected by a published finding — a candidate, party, broadcaster, account holder, or third party — may submit a correction request.

• Correction requests are reviewed by a senior reviewer and, if substantive, by the editorial board.
• The submitter receives a response within a published timeframe (set per deployment).
• Substantive corrections trigger an update to the public record as described in the update policy.

Contact channels

• Corrections and disputes: corrections@raqebinitiative.org
• General inquiries: contact@raqebinitiative.org
• Press inquiries: press@raqebinitiative.org
• Methodology questions: methodology@raqebinitiative.org