Orphan local order

Orphan local order — local state holds a working order the venue does not report. It is one of the divergence kinds a reconciliation pass can raise (vike_exec::recon::DivergenceKind): the pass fetches the venue's own order, fill, position and balance reports for a lookback window, diffs them against local state, and classifies every disagreement.

Evidence of an ABSENCE, which is the weakest kind there is: a venue report that omits an order is not the same as a venue that denies it. That is why this kind resolves to no events under every policy — see the verdicts below.

What each policy does with it

Every verdict above is computed from the policy the runtime actually applies, not written down beside it. That is not decoration: the opposite claim about the default policy was stated in six places in this codebase and was false in all six, so the export asks the function and the docs render the answer.

⚠ Auto-applying is not the same as doing something. This kind resolves to an EMPTY event list, so even under a policy that folds it, nothing changes — and because it folded rather than held, it does not raise an operator alert either.

Held means an operator sees an alert carrying the events the pass WOULD have folded, and confirming it folds exactly those — the same events, with a person in front of them.

Reading this in an incident

The policies page covers the four presets and when to choose each; the rollout rule for a newly wired venue is to start under quarantine until that venue's position reports are proven complete, precisely because position drift auto-applies under the default.

Where this comes from

vike_exec::recon::DivergenceKind and its origin class — this kind's evidence is an absence — the evidence is something NOT reported, the weakest class of evidence — with every policy verdict computed through vike_exec::recon::mode_applies, exported as rosters.json at every release.