Learn

Start here.

Find your role, take the first action, read the three links. No need to read the rest.

Everyone — step 1

Getting Started →

Install the CLI and scaffold your first portal in five minutes.

Everyone — step 2

Run Your First Initiative →

The full pipeline end to end — every stage, every reviewer gate, deploy, verify.

Prefer watching first? /demo — 35s sizzle or the step-through walkthrough.

Then pick your role

Each role gets a first action and three reads. These are the four.

Operator

You run an initiative end to end and make the stage-gate calls.

First action — Scaffold a portal

$ npx @nino-chavez-labs/blueprint-cli init --name=my-initiative

Read first

METHODOLOGY.md — how the pipeline thinks
variant-selection.md — which pipeline you run
portal-and-tier-ladder.md — how you externalize to stakeholders

Contributor

You send a fix or feature upstream into the methodology.

First action — Route your change

File an RFC or a plain PR — one question decides which. open ↗

Read first

CONTRIBUTING.md — the routing question + PR checklist
amendment-classification-pattern.md — the 4-bucket taxonomy
methodology-amendments-convention.md — how to write a promotable amendment

Reviewer

You write or run stage gates and conformance checks.

First action — Run a reviewer

$ npx @nino-chavez-labs/blueprint-cli review <name> --target=<dir>

Read first

reviewers/README.md — the roster + spec/executable contract
METHODOLOGY.md — the stages your gates sit in
voice-template.md — a concrete gate spec

Stakeholder

You own oversight and approval, and consume the output.

First action — Read the 5-minute pitch

The leadership-facing "why" and what Blueprint produces. open ↗

Read first

README.md § Evaluating for your team — what Blueprint is + what it outputs
00-charter.md — the charter, requirements, gap scorecard
productization/README.md — what shipped and when

Going further — running a team

Solo Blueprint needs none of this. The moment a second operator (or a second concurrent agent session) joins, coordination is Hive — optional, off by default, and worth standing up only when sessions genuinely contend. Read the readiness test before setting one up.

team-roles-and-conventions.md — the three zero-infra conventions + the crawl→walk→run litmus (read this first)
hive-coordination-pattern.md — what Hive is, when to use it, and blueprint hive setup to stand one up
hive-identity-gap.md — the shared-credential trust limitation; required reading before any client engagement