menu
Book a demo

newspaper // inform

Operational activity, as concise narratives.

Newspaper turns what happened into reports written for humans — and keeps teams informed without constant dashboard monitoring.

read this morning's ↓

01 — written for humans

Read it. Don't hunt for it.

Every morning — or whenever you ask — Newspaper composes what shipped, what broke, what was fixed, and what was learned. Delivered where you already read.

  • 01 narrative first — numbers as evidence, not the story
  • 02 every claim links back to its trace in Lore
  • 03 daily cadence, or on demand per team
MORNING BRIEFtue · 07:30
Checkout incident resolved overnight — 4h13m end-to-end, fixed by rollback of a3f91c. Full trace attached.
Weekly GMV +2.8% · refunds flat · three enterprise renewals closed.
New dataset live: customer_health v1 now feeds the retention review.
Learned: card-auth retries mask pool exhaustion — runbook updated § rollback.
composed by lore · sent to 14 people · no dashboards were opened

02 — what it delivers

Reports people actually read.

01 Daily operations reports every morning · per team
02 Failure digests what broke · why · who's on it
03 Incident summaries timeline · impact · lessons

03 — powered by lore

Same graph as every other surface.

The brief never contradicts the alert or the answer in Slack — it's all one Lore, retold for the morning.

data · logs · metrics · code · docs LORE alfred · ask lucius · build watchtower · monitor newspaper · inform

one graph in, four surfaces out — alfred · lucius · watchtower

Get tomorrow's brief, about today.

30 minutes · your data, your cloud

Book a demo →