Day-0 Explorer
General enterprise visibility, with access to the enterprise's general document spaces. No HR or payroll compartment access.Viewing as Enterprise Reader

IoT/MES event ordering

SCN-X09event orderingStanding at Day-0

IoT → MES

An operator recorded a manual machine stop in MES before an IoT alert for the same machine arrived, so Day-0 preserves the two system events in that order.

Condition: IoT alert arrives after manual downtime

Evidence anchors

Evidence

  • MES Downtime Event #4 · CLOSED

    operator-typed; ALRT-2026-000001 opened inside it

Comparison case

No implemented action can reverse this Day-0 condition
records an ordering that happened; no command writes external_iot_event_ref onto an existing manual stop

Why this is here

Metrolane Day-0 deliberately includes realistic cross-system delays, duplicate source records and event-ordering conditions. They are verified parts of the frozen reference estate, not accidental data corruption.