Track a running story as a sourced chronology, down to the minute, and embed it in the article as one iframe that updates as new events land.
A running story is already a chronology; the question is whether anyone is keeping it. Boromlia keeps it with you: every development dated and sourced as it lands, and one live embed in the article that never needs republishing.
What you get
Each development logged with its time, the people in it and where it came from.
A source filter that flags unsourced entries before publication, not after.
An embed for the article that shows new events as soon as you add them, on Advanced.
A CSV and an A4 PDF for the editor, the lawyer or the archive.
From notebook to published piece
Add developments as they happen, down to the minute when the day is not precise enough. Tags cut across a long story, so everything tagged "court" or "statement" can be read on its own. On Advanced, the Log style lays the same events out as a sortable table for the colleague who asks what happened in a given week.
The embed is one iframe tag, with no script and no key. It is served with a noindex header, so it never competes with your article in search, and the timeline keeps its own linkable page on boromlia.com.
Where AI helps a story, and where it cannot
An assistant can summarise yesterday’s coverage in seconds. It cannot confirm that a statement was made at 14:05 and not 16:30, and in a running story that is often the story. A chronology with a source on every line is something an editor can check and a correction can point to.
Readers ask assistants about the news too, and an assistant can easily get the order of events wrong. A public, dated, sourced timeline gives readers one version of the order that is easy to verify.
Views worth leaving open
Log: On Advanced: everything in a given week, sorted, in one table.
River: The reading view: what happened, in order, with the pictures.
Map: Where a story happened, when that is the story.
Questions
Does an embedded timeline update by itself?
Yes. The frame loads the live timeline, so an event added an hour ago is in the article an hour ago. Nothing is exported or republished.
Will the embed compete with my article in search?
No. Embed URLs carry a noindex response header, so the frame stays out of results and the article keeps the ranking.
How precise can a date be?
As precise as the story needs. A timeline’s horizon runs from years down to seconds, and any event can be a single moment or a range.