Mission feed
Mission feed
Every move the crew made, in the order it made it. Not a spinner. This is the crew's own event log, streamed over server-sent events straight out of the run store. Stage errors are in here too, because a clearance tool that silently skips a shot is worse than one that admits it.
Getting everything ready Setting the run up and handing your commercial to the crew. ingest -> 13 raw shot(s) merged to 12 pipeline 4 events 11:28:14.5
11:28:14.5
console accepted Ai_ki_-_Ready_When_You_Are_FR_.mp4 (20.1s) for AE-ABUDHABI, FR-F2, ID-SCTV, IN-COLORS, SA-ROTANA
11:28:14.5
run run_6261cfd86780 started: asset=runs/uploads/eb3a25369ee3/Ai_ki_-_Ready_When_You_Are_FR_.mp4 markets=['AE-ABUDHABI', 'FR-F2', 'ID-SCTV', 'IN-COLORS', 'SA-ROTANA']
11:28:14.5
ingest -> detecting shots
11:28:16.2
ingest -> 13 raw shot(s) merged to 12
Listening to what is said Writing down the words in each shot, so a claim that is only spoken is caught as surely as one on screen. shot_12 -> 74 char(s) transcription 12 events 11:28:20.6
11:28:20.6
shot_0 -> 12 char(s)
11:28:28.0
shot_1 -> 37 char(s)
11:28:31.2
shot_2 -> 0 char(s)
11:28:36.5
shot_3 -> 25 char(s)
11:28:39.4
shot_4 -> 20 char(s)
11:28:42.4
shot_5 -> 2 char(s)
11:28:47.6
shot_6 -> 20 char(s)
11:28:50.3
shot_7 -> 16 char(s)
11:28:53.0
shot_8 -> 7 char(s)
11:28:56.1
shot_9 -> 11 char(s)
11:28:58.8
shot_11 -> 8 char(s)
11:29:02.7
shot_12 -> 74 char(s)
Writing down what is actually there Looking at every shot once and describing what it holds -- a glass, a hemline, a logo -- in neutral sentences, with no verdict attached. Every market will argue about these same sentences. observe -> shot_12 analyst 12 events 11:29:09.0
11:29:09.0
observe -> shot_0
11:29:14.7
observe -> shot_1
11:29:20.6
observe -> shot_2
11:29:26.0
observe -> shot_3
11:29:32.8
observe -> shot_4
11:29:38.2
observe -> shot_5
11:29:43.8
observe -> shot_6
11:29:49.5
observe -> shot_7
11:29:55.6
observe -> shot_8
11:30:00.5
observe -> shot_9
11:30:05.4
observe -> shot_11
11:30:10.0
observe -> shot_12
Getting everything ready Setting the run up and handing your commercial to the crew. analyst -> 46 observation(s) persisted pipeline 1 event 11:30:16.5
11:30:16.5
analyst -> 46 observation(s) persisted
Asking every market what it thinks One adjudicator per jurisdiction, all at once, each holding its own rulebook and looking up the statute behind anything it objects to. SA-ROTANA clearance -> cleared (0 finding(s)) adjudicator 15 events 11:30:17.4
11:30:17.4
judge -> FR-F2 (6 candidates)
11:30:17.4
judge -> SA-ROTANA (19 candidates)
11:30:17.4
judge -> AE-ABUDHABI (30 candidates)
11:30:17.5
judge -> IN-COLORS (10 candidates)
11:30:17.5
judge -> ID-SCTV (9 candidates)
11:30:27.1
citation check -> FR-F2 FR-LANG-01 for obs_shot_4_001
11:30:36.2
citation check -> FR-F2 FR-LANG-01 for obs_shot_8_001
11:30:42.7
citation check -> FR-F2 FR-LANG-01 for obs_shot_9_001
11:30:50.1
citation check -> FR-F2 FR-LANG-01 for obs_shot_11_001
11:31:04.6
citation check -> FR-F2 FR-LANG-01 for obs_shot_12_003
11:31:10.7
AE-ABUDHABI clearance -> cleared (0 finding(s))
11:31:10.7
FR-F2 clearance -> cleared (5 finding(s))
11:31:10.7
ID-SCTV clearance -> cleared (0 finding(s))
11:31:10.7
IN-COLORS clearance -> cleared (0 finding(s))
11:31:10.7
SA-ROTANA clearance -> cleared (0 finding(s))
Getting everything ready Setting the run up and handing your commercial to the crew. adjudicate -> 5 finding(s) persisted across 5 market(s) pipeline 1 event 11:31:10.7
11:31:10.7
adjudicate -> 5 finding(s) persisted across 5 market(s)
Putting it all into Grafana Calling Grafana and making sure everything lands there: the numbers, the finding detail, the dashboards to read them on and the alerts that will wake the crew if something needs fixing. mcp update_dashboard('customs-overview', replace $.description) publisher 6 events 11:31:10.7
11:31:10.7
publisher -> connecting to Grafana
11:31:23.9
push_run_telemetry -> {'run_id': 'run_6261cfd86780', 'markets': ['AE-ABUDHABI', 'FR-F2', 'ID-SCTV', 'IN-COLORS', 'SA-ROTANA'], 'clearances': {'AE-ABUDHABI': 'cleared', 'FR-F2': 'cleared', 'ID-SCTV': 'cleared', 'IN-COLORS': 'cleared', 'SA-ROTANA': 'cleared'}, 'risk_samples': '5 market(s) x 20s', 'logs': 5, 'annotations_created': 5, 'annotations_skipped_as_duplicates': 0, 'failed_stages': []}
11:31:26.5
ensure_dashboards -> ['customs-findings', 'customs-history', 'customs-market', 'customs-overview', 'customs-remediation', 'customs-timeline']
11:31:28.1
mcp search_dashboards('customs')
11:31:30.1
mcp get_dashboard_by_uid('customs-overview')
11:31:34.8
mcp update_dashboard('customs-overview', replace $.description)
Getting everything ready Setting the run up and handing your commercial to the crew. snapshot store=True artifacts=3 pipeline 2 events 11:31:39.5
11:31:39.5
run run_6261cfd86780 done
11:31:41.5
snapshot store=True artifacts=3
Fixing the shots that failed Working out the cheapest edit that would satisfy the rule, pricing it, and changing only the seconds that were objected to. snapshot store=True artifacts=3 remediator 3 events 12:03:24.8
12:03:24.8
console requested remediation: FR-LANG-01 (FR-F2) -> fnd_FR-F2_FR-LANG-01_obs_shot_4_001
12:03:24.8
FR-LANG-01 (FR-F2) -> not remediable at concept scope: The element runs through the whole scene, so a patch cannot reach it: the scene has to be regenerated with the permitted element in its place.
12:03:27.0
snapshot store=True artifacts=3