The Situation Desk

Situations

One reading is a thing that changed on a day. A situation is several readings that keep pointing at the same subject, chained in order — so a change reported twice on Tuesday and reversed three weeks later reads as one story rather than three cards. Each one states how many days it actually covers, and whether anything has landed since you last looked.

7

Situations

44

Readings chained

6

Earned a second day

1

One day only

13 readings named no tracked subject. Counted 02/11/2026, 05:30:08.

Still moving

AI training & copyright

6 readings on 6 days (2026-01-17 to 2026-10-30), from 4 sources, collapsed into 6 events.

6

events

6 readings6 days covered4 sourcesearned a second daylast 30 Oct 2026

Still moving: last reading 3 days ago, across 6 separate days.

Still moving

Unity — engine & runtime

5 readings on 4 days (2026-03-06 to 2026-10-29), from 5 sources, collapsed into 5 events.

5

events

5 readings4 days covered5 sourcesearned a second daylast 29 Oct 2026

Still moving: last reading 4 days ago, across 4 separate days.

Still moving

Steam — storefront & discoverability

4 readings on 4 days (2026-01-17 to 2026-10-29), from 4 sources, collapsed into 4 events.

4

events

4 readings4 days covered4 sourcesearned a second daylast 29 Oct 2026

Still moving: last reading 4 days ago, across 4 separate days.

Still moving

Apple / App Store — storefront & discoverability

5 readings on 4 days (2026-03-04 to 2026-10-29), from 5 sources, collapsed into 5 events.

5

events

5 readings4 days covered5 sourcesearned a second daylast 29 Oct 2026

Still moving: last reading 4 days ago, across 4 separate days.

Still moving

Unreal Engine

7 readings on 6 days (2026-03-04 to 2026-10-29), from 7 sources, collapsed into 7 events.

7

events

7 readings6 days covered7 sourcesearned a second daylast 29 Oct 2026

Still moving: last reading 4 days ago, across 6 separate days.

One day only

GameMaker — engine & runtime

2 readings on 1 day (2026-10-23), from 1 source, collapsed into 1 event.

1

event

2 readings1 day covered1 sourcenever got a second daylast 23 Oct 2026

Every reading landed on one day. It has not earned a second day of coverage yet, and this card says so rather than calling it a trend.

Still moving

Godot — engine & runtime

2 readings on 2 days (2026-08-18 to 2026-10-15), from 2 sources, collapsed into 2 events.

2

events

2 readings2 days covered2 sourcesearned a second daylast 15 Oct 2026

Still moving: last reading 18 days ago, across 2 separate days.

Untracked

Readings on untracked subjects

13 readings on 11 days (2026-06-11 to 2026-10-29), from 13 sources, collapsed into 12 events.

12

events

13 readings11 days covered13 sourcesearned a second daylast 29 Oct 2026

These readings named none of the tracked subjects, so they were not force-fitted into a situation. Adding a subject to the vocabulary is what files them.

How a situation is formed

What joins
A reading joins a situation when its own words name that subject. No model call, nothing inferred.
Minimum readings
2 — a single reading stays a reading; it does not become a situation.
Survivability
A situation has earned a second day when its readings fall on two or more distinct days. One day of coverage is printed as one day.
Going quiet
Nothing new for longer than the quiet window (21 days) marks a situation quiet. It is kept and labelled, never deleted.

Nothing here is generated by a model: the grouping is word matching against a fixed subject list, and every event carries the ids of the readings it was built from. Readings that name no tracked subject are kept and shown as untracked rather than being pushed into the nearest situation.