User-facing mdBook documentation

Goal

Create accurate en-US documentation that helps users complete a task or understand public behavior with minimal cognitive load. Lead with the outcome, verify claims against authoritative sources, and include implementation detail only when it changes a user decision or observable result.

For a multi-package product workspace, maintain one canonical user-facing workspace book that accounts for every public member and provides all needed member and cross-member guidance. Treat member crates as parts of that book's product surface, not as reasons to create separate books or duplicate book navigation in member READMEs. A genuinely distinct product, audience, or deployment boundary belongs to its own documentation scope rather than becoming a second book for the same workspace product.

Request mode and write boundary

Choose the mode before following the workflow: