Context Layer

Operator console

Context health

Reconcile an earlier summary with the latest terminal evidence.

Synthetic sample Open a private JSON snapshot to inspect it in this browser.
Nothing is uploaded or stored.
Current answer

Needs attention

Are all scheduled automations healthy?

Evidence conflict Detected
Earlier summary
Current evidence

Lane status

What needs attention

Evidence timeline Inspect chronology

    Engineering proof

    Small, inspectable, and bounded.

    Try bounded retrieval ↑
    Deterministic Same packet, same answer
    Zero model calls Rules run locally
    Fail-closed Missing proof cannot become healthy

    Operational path

    Generate, open, decide.

    1. Create a snapshot from scenario and evidence records.
    2. Open it locally in the console; no server receives it.
    3. Copy the bounded report or inspect the exact source record.
    npm run diagnose -- --output snapshot.json

    Evidence boundary

    What it proves, and what it does not.

    It proves the supplied records support the displayed operational conclusion under explicit freshness and schedule rules.

    It does not prove an external source is true, replace authorization, or silently infer missing state.

    Evidence record