import type { OneSdkContext } from '../../sdk/types/oneSDK';
import type { JourneyScreenConfig, ScreenSequence } from './screenSequence';
import type { StepRunner } from '../journeyHandle';
import type { FirstPaintSignal } from '../steps/firstPaint';
import type { StepMachine } from '../steps/stepMachine';
export type IdvStepRunner = {
    run: StepRunner;
    /** take the vendor's UI down at terminal settlement — see the implementation */
    /** leave the container clear for the terminal card — see the implementation */
    clearForTerminalScreen: () => void;
};
/**
 * Converts engine events into a ClassifierInput. Decides nothing itself —
 * spec §5.0.1: the IDV status is process state, never an outcome.
 *
 * Which engine events the capture step listens to, and which of them complete
 * it, is declared in `steps/stepTable.ts` (row CAPTURE) — the handler map below
 * has to cover exactly those events or it will not compile. Everything is
 * subscribed once, through the machine, and released by its single teardown.
 *
 * There is deliberately **no fallback timer** on anything the applicant does.
 * The only timer in this file waits out the idv module's own mount debounce,
 * which guards engine behaviour rather than human action.
 */
export declare const mkIdvStepRunner: (deps: {
    oneSdk: OneSdkContext;
    config: JourneyScreenConfig;
    machine: StepMachine;
    firstPaint: FirstPaintSignal;
}) => IdvStepRunner;
export type { JourneyScreenConfig, ScreenSequence };
//# sourceMappingURL=idvFlow.d.ts.map