Missing fill
The missing-fill reconciliation divergence: what raises it, and what each of the four policies does with it.
Missing fill — the venue reports a fill local state has never seen. 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.
The commonest real divergence and the one reconciliation exists for: an execution happened, the message never arrived or arrived while the process was down, and the local book is a fill behind.
What each policy does with it
| Policy | Verdict |
|---|---|
hybrid | auto-applies |
synthesize | auto-applies |
quarantine | holds for an operator |
external-quarantine | auto-applies |
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.
When this kind auto-applies it produces real events, which is why the verdict above matters operationally.
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
materialized by reconciliation itself — the pass is what produced the local-origin evidence — with every policy verdict computed through
vike_exec::recon::mode_applies, exported as rosters.json at every release.