Language / locale

Languages.

English is the source. All ten locales are live.

02 / News intelligence

Leila.

The news is not short. A useful daily update is. Leila reads the world, groups what matters, and gives a reader a short brief instead of a second job.

Role
AI product, data pipeline, publishing, subscriptions
Scope
Source ingestion, classification, daily brief, reader experience, payments
Status
Live / reviewed
news categories
16
Recorded 2026-10-31
languages
Five
Recorded 2026-10-31
reader brief
Daily
Recorded 2026-10-31
source backbone
GDELT
Recorded 2026-10-31
  1. 01

    Sources

    GDELT and the Global Knowledge Graph bring a wide, changing stream of events.

  2. 02

    Leila core

    Classification, grouping, language handling, and the daily brief.

  3. 03

    Reader

    A short update, a clear topic, and a subscription that fits the reader.

From an open signal to a short read

01 / Context

The problem

A person who wants to follow the world has too many sources and too little time. A feed rewards the loudest item, not the most useful one. A daily brief has to make choices: what belongs, what is duplicated, and what can wait.

Leila treats that editorial problem as a system problem. The model is one part. The source pipeline, the category rules, the publishing step, and the reader experience are the rest.

02 / Audience

Who it is for

The reader wants to understand enough to act, without reading everything. The publisher needs a repeatable daily product: sources, categories, language, delivery, and subscriptions. Those needs pull in different directions. The interface has to stay calm while the pipeline moves a large amount of material.

03 / Constraint

The constraint that shaped the build

News is repetitive, multilingual, and uneven. Two reports can describe one event. A word can mean different things in different places. A source can be late or can fail. The product has to absorb that without turning the reader's morning into an investigation.

The business side had to work too. Subscriptions, automatic publishing, and more than one payment route make the service a product rather than a demo. Payment providers and messaging channels each have their own rules.

04 / Build

What we built

Leila is a complete daily loop:

  • GDELT and Global Knowledge Graph ingestion, with a pipeline that can change without rewriting the reader experience.
  • Sixteen news categories and a grouping step that removes repeated stories before they reach the brief.
  • Five language paths, with the source language and the reader language treated as separate problems.
  • A scheduled daily brief, automatic publishing, and a reader-facing index.
  • Subscriptions through Paystack, Flutterwave, and Telegram Stars.

05 / Decisions

The hard part

The difficult edge is not generating a paragraph. It is deciding what a reader should see, when a story is the same story, and how a failure in one source should not empty the page. The system has to be predictable enough to run every day and honest enough to show a thin day as thin.

The payment routes are separate from the editorial product. A provider can fail without losing the brief. A subscriber should never have to understand the pipeline to use the service.

06 / Outcome

What is live

Leila is live at leila.frvnkenstein.online. The public site is the reader's entry point; the work behind it is a pipeline that has to keep its shape as sources, categories, and languages change.