Chapter 5 of 7

15 min

Trace batch reference rows and runtime events separately

Separate two execution contracts in event history and inspect the scope and current limits of the ontology graph.

Question for this chapter

Do the eight batch rows and the two Agent events mean the same thing?

Why this matters now

All rows land in om_event_history, so a row count can make them look like one execution. The batch reproduces reference values for eight zones; runtime events record one operator’s allowed and blocked requests. Audit interpretation depends on this distinction.

Try it

Refresh om_event_history. In a fresh practice space, one run of each preceding action leaves eight batch rows followed by two rows for OPR-WORKSHOP-01, for a total of ten.

Contract	Producer	Rows	`user_id`	Meaning
Batch reference	`map_control_execution`	8	`AGENT`	reproducible coordinates and events for eight zones
Runtime allowed	`log_event` → event pipeline	1	`OPR-WORKSHOP-01`	execution evidence for the Busan display command
Runtime blocked	`log_rejection` → event pipeline	1	`OPR-WORKSHOP-01`	rejection evidence for the patrol-history question

Korean Portal event-history table showing the TZ-008 UI_CONTROL batch event — The Portal capture is in Korean. Inspect the zone ID and action type on the reproducible batch event first.

Next, run ontology_materialization. After it completes, inspect TZ-008 in this order.

In Graph Explorer, select this scenario's collection.
Select mc_tactical_zone under Entities.
Select TZ-008 and confirm zone_id in Node properties.
Inspect the coordinate-overlay and event connections returned with the zone.
Select the connected event and confirm created_at and the action type.

Success looks like this

The graph connects the TZ-008 zone to its OV-008 overlay and a batch event. Select the edges and confirm the relation types mc_has_spatial_coordinates and mc_referenced_in_event.

With the eight batch rows, ontology materialization produces these counts.

Output	Rows
`mc_tactical_zone`	8
`mc_graphic_overlay`	8
`mc_event_history`	8
`mc_has_spatial_coordinates`	8
`mc_referenced_in_event`	8

After two runtime events are persisted and materialization runs again, the event entity reaches ten rows. The spatial relation stays at eight. Under the current transformation contract, the event-reference relation still connects only the eight batch rows.

Interpret the result

Each batch action_log places 안전구역객체ID at the top level, where ontology materialization can read it directly. An Agent runtime event nests the original request and result under result, so the current transformation does not materialize that nested zone ID as a relation.

Read the current evidence in three places.

Batch zone, coordinate, and event relations: Graph explorer
Runtime allowed and blocked requests: om_event_history, filtered by user_id
Runtime distribution: the dashboard in the final chapter

The runtime audit event is not missing; it remains in the dataset but is not yet linked as a graph relation. Production end-to-end graph tracing needs a transformation that extracts the nested zone ID.

Next decision

You have separated the two execution contracts and the current graph boundary. Next, check the safe control conditions in four questions before confirming both runtime intents in the final chapter.