@kekkai/blueprintArchitecture as Code

Keep architecture executable ​

Architecture rules usually live in diagrams, review comments, and memory. They drift because the code, the documentation, and the instructions given to coding Agents evolve separately.

Blueprint puts the durable architecture model in blueprint.config.mjs. From that definition it can produce structural ESLint checks, a human-readable handbook, and guidance for the coding Agents that work in the project. inspect, doctor, deps, and the other commands then measure the real repository against that model.

Adopt with AI ​

Choose the architecture contract you want this repository to follow. Blueprint will not infer this decision from the current folder shape.

Want to understand the decision or run the CLI manually? See init in Commands.

Evidence ​

Case studies and experiment records about Blueprint are published as GitHub Discussions. This list reads them from GitHub when the page loads, so new, edited, and deleted articles are reflected here within five minutes.

Upgrade or remove with AI ​

After adoption, ask your coding Agent in plain words. The Agent contract Blueprint generates routes both requests to Blueprint's own lifecycle commands, so the Agent does not reconstruct migrations from release notes or uninstall the package first.

Upgrade Blueprint to the latest version.

The Agent runs npx @kekkai/blueprint@latest upgrade, completes any operations in the resolved blueprint-upgrade.md playbook, and finishes only when Blueprint verifies the upgrade. A repository adopted with a release older than the lifecycle commands has no such guidance in its Agent contract yet, so name the command the first time: Upgrade Blueprint to the latest version with npx @kekkai/blueprint@latest upgrade.

Remove Blueprint from this project.

The Agent runs npx blueprint remove --dry-run, resolves any ownership conflicts it reports, then runs npx blueprint remove, which removes the package last. See upgrade and remove for what each command proves before it changes anything.

Go deeper ​

• Commands — every public command, flag, output, and refusal boundary, including upgrade and removal.
• Configuration — the complete blueprint.config.mjs model.
• Generated Files — what init creates or changes, who owns it, and for how long.
• Philosophy — the engineering principles behind the contract.
• API reference — generated package signatures for library consumers.

Security reports and supported-version policy live in the repository Security policy. Release history lives in the repository Changelog.