Deep dives#

Understanding-oriented discussion of the why behind Katalyst: the vision and scope, the domain model the tool is built on, and the deeper design discussions that no single page or package owns: how checks work and the libraries that run them, how bases map backend sources onto the model, and how operations grow richer as a backend’s capabilities increase. For the short version, start with Welcome.

These pages carry the behavioral why - any rationale a user can observe - and each subsystem’s architecture: how it is built, its entities, and the design decisions behind it. A package’s AGENTS.md holds only its code conventions and a pointer back to its page here.