get_scenario

com.airsidelabs/aviation-tools · Verify this server

One real episode end to end: what happened, where and when (UTC), the actors, what it shows and what it must not be read as; the timeline, every event with its actor, source and the reference of the raw record it came from; and the lenses, each a use case's cut of the day with a small evidence table, an implication, and the use cases it illustrates with a reason for each. Use it when a brief needs the whole story rather than one finding: a worked example with a paper trail, an edge-case write-up for a data science team, a workshop narrative. For one use case's view, take the lens from get_use_case instead; it is smaller and carries the same caveats. `events=False` or `lenses=False` trims the reply. Every figure in a lens was measured by a probe over the named source and window and checked against its evidence before publication; quote it with the scenario id, the source and the window, and copy `not_to_be_read_as`. Do NOT extend a scenario past its window, treat its counts as rates, or read one airline's behaviour on one day as its policy. Do NOT call this for live status: nothing here is live, and the server never queries the feeds a scenario was cut from. An unknown id returns the known ids.