Skip to content
OOPSY.Tracking the end, calmly.
Menu
V3
← Back to the collectors
COLLECTOR No. 002

BADGER · he / him

Quincy.

Conflict correspondent & peony enthusiast

Terrible news. Exceptional flowers.

Quincy follows conflicts through posture, logistics, alliances, and the sentences officials suddenly stop using. He wants a timeline before an opinion. His radios are always on; his phone is always face down, except when it is not. Outside the newsroom he grows award-winning peonies, and considers getting a difficult plant through winter a more useful achievement than most military parades.

Favorites are saved on this laptop’s browser.

HABITAT

A map room, three radios, a battered field jacket, one perfect vase.

COLLECTS

Dispatches, shipping notices, treaty footnotes, and seed catalogues.

OFF THE CLOCK

Has a tactical contingency plan for aphids.

ABSOLUTELY NOT

Anonymous certainty or a casualty figure presented as settled without attribution.

Ellis, Oopsy’s lead analyst

AROUND THE NEWSROOMCalls Ellis for major developments; asks Milton what a blocked strait does to dinner.

“MAKE PEONIES, NOT WAR.” →

FROM THE NEWSROOM

Worth a closer look.

Read the briefing →

Reading Ellis’s saved edition…

QUINCY’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 · FICTIONALQuincy: “Timeline first. The peonies can wait until the tabs are dated.”

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 Conflict reporting… Background collection runs while the app server is awake. Conflict register entries are editorial context; they do not confirm incidents.

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.