Skip to content
CHEREngineering workspace
Experience
Appearance

Engine

Runs

A run is an execution the engine recorded. A gate outcome is what one run made of one gate, and a run that reported nothing is not a run that passed.

Read-only. Everything here is read from what CHER has recorded. Nothing on this screen decides, approves, records an outcome or writes to governance, evidence or audit.

Runs

source PLANE_B_STORE

Gate outcomes are recorded per run by the engine. 3 run(s) and 2 outcome(s) exist in this store. A run with no outcomes has not reported; it is not a run that passed.

  • RUN-VERIFY-0001

    state CONTEXT

    Snapshot the run ran against
    KS-cd27e616e2091377
    Created
    2026-09-01T14:44:53.448381+00:00

    No gate outcome record names this run

  • RUN-2026-09-05-001

    state VALIDATE

    Snapshot the run ran against
    KS-2d4a1d596a27c2e1
    Created
    2026-09-05T05:42:48.998746+00:00

    1 gate outcome record(s) name this run

  • RUN-2026-09-05-002

    state VALIDATE

    Snapshot the run ran against
    KS-2d4a1d596a27c2e1
    Created
    2026-09-05T05:44:38.758952+00:00

    1 gate outcome record(s) name this run

Gate outcomes reported by a run

2 outcomes from 2 of 3 runs

  • GATE-CONSOLE-PLANE-001

    PASSED
    Reported by run
    RUN-2026-09-05-001
    Observed at
    2026-09-05T05:42:49.003459+00:00
    Package
    EEP-CHER-CONSOLE-001
    Package version
    1.6.0

    The record names nothing as blocking this outcome.

  • GATE-CONSOLE-PLANE-001

    PASSED
    Reported by run
    RUN-2026-09-05-002
    Observed at
    2026-09-05T05:44:38.761673+00:00
    Package
    EEP-CHER-CONSOLE-001
    Package version
    1.6.0

    The record names nothing as blocking this outcome.

An outcome is what one run recorded of one gate at one time. It is not a dispatch, not an approval and not a statement that the work it names is complete.