Operate
The day-2 layer — what you run after the first initiative ships. The homepage covers what each command does; this page covers when to run them.
When a new methodology version ships, upgrade
shows what changed before touching anything — dry-run by default, non-breaking by design.
Previewing costs nothing, so run it whenever you sit back down on a project.
$ npx @nino-chavez-labs/blueprint-cli upgrade
Running Blueprint on more than one project, fleet
is one report across all of them: which are current, which have fallen behind.
Check it before starting new work, not after something drifts.
$ npx @nino-chavez-labs/blueprint-cli fleet doctor loads the config, every
reviewer, and the portal — and says what it didn't check. Wire it into CI so drift
fails the build instead of surfacing in a stakeholder demo.
$ npx @nino-chavez-labs/blueprint-cli doctorPlanned
Multi-operator coordination
ai-hive integration (integrate, not absorb). Flip hive.enabled once a second operator joins the initiative.
Planned
Hosted fleet dashboard
Deferred to v2 (scope ceiling B). v1 is git-host + npm + local files only — no hosted service.
Haven't shipped a first initiative yet? Start at Learn — getting started, the full tutorial, and role-routed paths.