What the scheduled export loop does with the advisory settings and the mounted ecosystems.

One mounted ecosystem the scheduled loop compiles, with what a failed EPSS feed means for it.

A configured store turns exporting on, as it does for the proxy's sync, and each mounted ecosystem earns an artifact. Nothing is a store with no ecosystem to compile, which the boot refuses.

The delay between export cycles. The config decoder bounds compileInterval to maxBound `div` 1000000 seconds, so this conversion cannot wrap to a negative delay.

How long the idle loop sleeps between wakeups. Nothing observes the wakeup, because an added store only takes effect on the next boot, so the sleep is deliberately long.

The upstreams a compile reads, scheduled or one-shot. Both are configured keys, so a moved or mirrored feed never needs a new binary.

The quiet-time thresholds one compile is judged against. An ecosystem with no configured threshold, and a one-shot compile of a name this build does not serve, take defaultQuietTime.

The egress every compile attempts whatever the rules, named by the host and port it dials.

Options for the one-shot ecluse pilot compile mode.

The EPSS requirement a one-shot compile runs under. A mounted ecosystem takes its resolved policy's. An unmounted one prepares a dataset ahead of its mount, so it requires the feed.

The warning a one-shot compile logs for an ecosystem the loaded configuration does not mount.

Whether a one-shot run uploads its artifact, and where.

Plan a one-shot run's upload. Asking for one with no store configured is refused, never skipped, so a scripted run cannot exit successfully having published nothing.

Requesting an upload without a configured advisory store. It is a wiring fault at the composition root, so it throws rather than returning a value the caller could only re-raise.

Where one compiled artifact lands: the store's bucket, and the object key its own file name takes under the store's prefix. The proxy's sync reads that same key.