Welcome

Workbench is the internal framework we use when several independent projects need the same boring foundations—such as checks, a shared website, or a local work queue—without handing one project the keys to another project's decisions or private material.

Here is the practical version: three projects may need the same check and a page on the same website. Workbench supplies the common service; each project keeps its own work, meaning, and approval. If a check finds a problem, it reports it to the owning project instead of quietly deciding on that project's behalf.

This public section is Workbench Documentation. It is where we explain a tool we are proud of, how its useful parts fit together, and what we have learned while building it. Workbench remains an internal operating framework; its separate Customer Core is currently a local preview, not publicly redistributable software.

Capability notes describe stable tools and services in plain language, with purpose, safeguards, and examples. Start with Shared Services for the quick tour, How Website Management Works for the path from an approved note to a live page, or Learning From Failures Without Inventing Folklore for a grounded lesson. The current documentation also covers accountable evidence, safer research, and the Customer Core preview. Only deliberately approved material is published; credentials, runtime state, private project content, proprietary implementation details, and the keys to the metaphorical boiler room remain elsewhere.