Docs

The writing that spans the code, in reading order.

Design: what it is, why it's built this way, and what it isn't.
Usage: install it, use it, and the snippet for agents.
Rules: how every repository builds, checks, deploys and releases, each rule with its id.
Plan: what's done and what's next, in order.
Lessons: what building it taught, for the next change.
Development: build, test and change it.

Docs

design.md
craftz is one way to build, check, deploy and release a repository, as a package each one depends on. It's also the repository that shows it working. This page is the design as a whole. The plan says which parts are built so far, and in what order the rest comes.
development.md
How craftz is built and changed. What every repository shares, like the scripts, CI and releases, is in the rules, and isn't repeated here.
lessons.md
What setting up the repositories' builds and deploys taught, and then building craftz, for whoever changes them next. Each lesson says what happened and what to do about it. Lessons that belong to one repository stay there.
plan.md
What's built, and what comes next, in order. The design is the whole of what craftz becomes.
rules.md
How every repository builds, checks, deploys and releases. There's one way to do each thing. drift checks every repository against these rules and lists where each has drifted, and align brings them back in line. Usage says how to run them.
usage.md
craftz is used through its commands and its plugin.