Skip to page content
L’AGENCE
عربي
عربي

Find your next direction.

Not sure where to start?
Help me choose →

Start a project
Start a project

Case study

RALIFY. BUILDING THE NEWSROOM ENGINE.

Connecting discovery, classification, translation and publishing with review controls and recoverable workflows.

THE DELIVERY AT A GLANCE

An editorial pipeline with human control

Discover → Classify → Translate → Review → Publish

Automation foundations with review and recovery; commissioning and quality monitoring continue.

Editorial summary of the published case study—not a product screenshot or a performance claim.
CLIENT / BRAND

Ralify

DISCIPLINETechnologies
RELATIONSHIP

L’AGENCE-owned venture

How we got thereExplore the decisions and delivery details

The starting point

Ralify’s bilingual newsroom turns external gaming sources into structured editorial work. L’AGENCE developed a connected editorial operating system to coordinate that work as part of its owned media platform.

The challenge

The workflow crossed source feeds, editorial records, translation and website publishing. Repeated requests, partial failures and ambiguous source material made simple automation insufficient: the system also needed to prevent repeat work and expose exceptions.

The decision

Bring the newsroom into one coordinated workflow. Separate repeatable processing from editorial judgment, and make publishing rules configurable so generated drafts receive the appropriate checks before publication.

The system

The editorial operating system connects source discovery, content classification, translation, review and publishing. Shared records track what has been processed, what needs attention and what is ready to publish. Approval controls and clear operator views keep the team in charge.

The delivery

We implemented duplicate detection and work claims, classification routes, bounded translation attempts and recovery state. Approval handlers check the authorised actor and guard against repeated actions. Run logs, failure records and protected operator endpoints make the system inspectable.

The result

The implemented workflow provides an operating foundation for the bilingual newsroom, with duplicate controls, review steps and visibility into failures. Quality monitoring and end-to-end commissioning continue.

Additional project notes

Automation needs memory. Processing a feed twice should not produce the same article twice. The implementation checks existing work and claims candidates before processing, with separate handling for repeated approval actions and publishing side effects. Translation needs its own recovery path. Arabic publishing is treated as a separate operation. Attempt tracking and checkpoint state allow failures to be inspected and recovered without assuming that a successful source-language article means both versions are complete. Human control remains part of the workflow. Editorial thresholds and approval routes allow the team to manage which material progresses. The goal is to make routine work easier to operate while retaining a decision point for uncertain content and exceptions. Delivered capability, measured carefully. The case demonstrates implemented orchestration, review controls and operational visibility. It does not claim a percentage cost reduction, time saving or error-free service; those require a defined measurement period and completed commissioning.

ANOTHER PERSPECTIVE

Continue
the collection.

Ralify brand mark
TechnologiesOWNED VENTURE

RALIFY. ONE PLATFORM. TWO LANGUAGES.

Building a connected English and Arabic gaming destination around reusable content and living game Worlds.

Ralify brand mark
AgencyOWNED VENTURE

RALIFY. A HOME FOR GAMERS.

Defining a clear promise for a bilingual gaming brand—and turning it into a product people can navigate.

BACK TO THE COLLECTIONSelected work

The thinking. Made tangible.