didbot_brand/

lib.rs

//! The did.bot brand images, rebuilt from the simulation that draws the
//! landing page.
//!
//! Every file this crate writes — the wordmark, the social card, the whole
//! icon set, the favicon — is a snap of the same 2-D Ising anneal
//! `crates/didbot-site-anim` runs in the browser, stopped at the end of
//! its schedule. Nothing is traced, redrawn, or exported from a design
//! tool, so there is no second copy of the mark to keep in step with the
//! page: change the schedule and rebuild, and the images change with it.
//!
//! # Rebuilding
//!
//! ```text
//! scripts/build-brand.sh          # rewrite site/public
//! scripts/build-brand.sh --check  # fail if anything is stale
//! ```
//!
//! Both run this crate's `render` example, which is what the generator is:
//! a program run from a checkout to refresh committed files, never one
//! anybody installs. The `--check` form is what CI runs, and it is the
//! reason the images are committed at all: the tree is allowed to hold
//! generated files as long as something proves they are the ones the
//! generator produces.
//!
//! # Icons, and what "the same noise" means
//!
//! An icon is not the wordmark shrunk. It is a size ladder of marks — a
//! "d" cut out of a disc from 48 sites up, the dot below that — set in
//! the same six-glyph font, annealed on its own square lattice by the
//! same schedule, and painted with the same two colours at the same
//! one-block-a-site magnification. So the grain reads as the same
//! material as the landing page at every size, without ever resampling a
//! picture of it. [`mark`] is where the ladder is written down, and each
//! tier's doc comment says what fails on the tile below it. "did.bot"
//! itself appears only on the wordmark and the social card.
//!
//! Every icon also carries three [`mark::Specks`] — pinned sites the field
//! does not decide, single pixels at 16 and irregular clumps above it.
//!
//! # Determinism
//!
//! An image is a pure function of its [`mark::Mark`] — no clock, no
//! entropy, no filesystem — so building twice on one host gives identical
//! bytes, which `--check` relies on. Bit-exactness across platforms is
//! not promised, for the reason `didbot-avatar` gives: the Metropolis
//! acceptance test goes through `exp`, and a `libm` is entitled to its own
//! last bit. That is why `--check` is a CI gate on one platform rather
//! than a claim about every machine.
//!
//! # Pages
//!
//! [`page`] draws the page a browser lands on at each step of a sign-in,
//! around [`WORDMARK_SVG`] and [`FAVICON_SVG`]. A server needs only that,
//! so everything else here is behind the default `render` feature, and the
//! simulation with it.

#![forbid(unsafe_code)]

#[cfg(feature = "render")]
pub mod ico;
#[cfg(feature = "render")]
pub mod mark;
pub mod page;
#[cfg(feature = "render")]
pub mod paint;
#[cfg(feature = "render")]
mod render;

#[cfg(feature = "render")]
pub use render::*;

/// The cropped wordmark as `scripts/build-brand.sh` last wrote it, for a
/// page that carries the logo inline rather than linking to the site.
pub const WORDMARK_SVG: &str = include_str!("../../../site/public/brand/wordmark-tight.svg");

/// The tab icon, the same way.
pub const FAVICON_SVG: &str = include_str!("../../../site/public/favicon.svg");