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

Quality release lag

SCN-X08status lagStanding at Day-0

MES → ERP

MES released a quality hold, but the release was not sent to ERP, so ERP has not caught up and the corresponding inventory remains blocked.

Condition: MES hold released; ERP inventory blocked

The hand-off that is missing

  1. Present · MES Quality Hold

    Coating thickness below limit on the first article

    #1 · RELEASED

    ERP

    EXPECTED · NOT PRESENT

    SCN-X08 is declared across MES and ERP; this record carries no operational link to ERP.

The scenario catalogue names the destination system. No counterpart record exists at Day-0, and none is implied here.

Evidence anchors

Evidence

  • MES Quality Hold #1 · Coating thickness below limit on the first article · RELEASED

    hold released, never sent to ERP

Comparison case

  • MES Quality Hold #3 · Operator queried a batch dimension; ERP stock held pending the check. · RELEASED

    release carried to ERP hold QHLD-2026-000004

    Open its cross-system journey
An implemented mechanism exists, but the Day-0 evidence does not meet its prerequisites
the relay needs an ACT ERP quality hold named by the caller, and nothing in the estate pairs one with this MES hold

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.