Ellis.

Editor of the end times

The world is a lot. She brought folders.

Ellis runs a newsroom that would benefit enormously from a quiet Tuesday. She remembers the warning nobody read, the correction buried on page six, and exactly who borrowed her stapler. When Quincy calls, she clears the board, checks the timestamps, and makes the complicated thing legible. She cares deeply. This is why the filing system is so aggressive.

Visit my desk ↗Open my map ↗

Favorites are saved on this laptop’s browser.

HABITAT

The central archive. Warm lamps, cold tea, one very large situation board.

COLLECTS

Global developments, long-term trends, and a suspiciously comprehensive biscuit inventory.

OFF THE CLOCK

Remembers everyone’s tea order, even during a breaking story.

ABSOLUTELY NOT

An important headline without a source trail.

AROUND THE NEWSROOMQuincy spots the escalation. Ellis makes sure the whole newsroom knows.

“ONE THING AT A TIME.” →

FROM THE NEWSROOM

Worth a closer look.

Read the briefing →

Reading Ellis’s saved edition…

ELLIS’S LATEST DATA & NEWS

Recently collected.

Actual API records and reporting, sorted by their supplied dates. A collection can contain older observations or future forecasts.

SAVED ASSIGNMENTS

Working with the newsroom

Reading saved assignments…

Roles are saved event assignments. They do not mean a character independently checked a source.

CHARACTER COMMENTARY · FICTIONALEllis: “One thing at a time. Leave room in the folder for a correction.”

SAVED REVISION HISTORY

What changed in assigned records

Latest saved revisions, including resolved and archived work. Source observation dates remain on the exact record.

Ledger changes are not a log of character actions.

Actual provider request history · shared collection service

No provider attempts saved yet. Cache reuse does not make a new request.

These are application requests, not actions performed by a fictional collector.

LINKED EVENT WORK

Events I’m working on

Collecting connected Health reporting… Background collection runs while the app server is awake; saved events remain available between checks.

Collecting connected Natural Events… Background collection runs while the app server is awake. Saved records remain available; absence from a feed is not an all-clear.

Collecting connected Conflict reporting… Background collection runs while the app server is awake. Conflict register entries are editorial context; they do not confirm incidents.

Collecting connected Infrastructure and Economy… Background collection runs while the app server is awake. Source observation dates remain explicit; headline route grading does not verify closures.

Collecting connected Climate reporting and measurements… Background collection runs while the app server is awake. Daily, monthly, annual and partial-year observations retain their own periods and baselines.

Collecting Space reporting and provider records… Background collection runs while the app server is awake. Estimated Kp, solar flare classifications, forecasts and reported impacts keep separate meanings.

Collecting attributed anomaly reporting… Background collection runs while the app server is awake. Named-site pins are reporting context. CNEOS natural-fireball references are dated sensor records, separate from UAP reports and held off Watch; the catalogue is refreshed at most daily.

Reading the saved event history…

Signals & source records 0

Loading recent data…

On my news radar 0

Checking the wire…

Reporting is selected from the home engine and specialist sources; it is not complete topic coverage.