//! The bottom of acme-proxy's crate graph: what every layer above it speaks.
//!
//! Configuration ([`config`]), the ACME wire vocabulary ([`identifier`],
//! [`jws`], [`error`]'s problem documents, [`routes`]), the nested-JWS
//! surfaces that are pure verification ([`eab`], [`key_change`]), certificate
//! parsing ([`cert`]), the audit trail's vocabulary ([`audit`]), where a
//! request came from ([`client`]), and the small shared helpers
//! ([`datetime`], [`logfields`], [`palette`], [`pemfile`], [`random`],
//! [`script_hook`], [`templating`]).
//!
//! Nothing here opens a database, dials a network or knows a signer; the
//! crates that do are built on it. An internal crate of the `acme-proxy`
//! binary, published in lockstep with it and with no semver promise of its
//! own.