Publishing blueprints

verified_on: 2026-07-19

Before you publish

Publishing turns a clean recipe into an immutable Nemu version.

• Nemu is curated at launch. If you are not invited yet, contact the owner for access.
• Run nemu login and approve the device code from the author dashboard.
• Confirm your terminal identity before publishing.

nemu login
nemu whoami
nemu validate
nemu lint
nemu verify --sum

Publish from Codex

Use the generated /nemu_publish command after installing the Codex command pack. It tells Codex to run signed-sum verification, validation, linting, a git diff summary, and changelog confirmation before it asks for publish approval.

nemu agents install codex
# then run /nemu_publish inside Codex
nemu publish --bump --yes
nemu publish --version vN --yes

Stop before publish if verification, validation, or lint fails. Use /docs/authoring and /docs/safety-linter to repair findings.

After publish

The final CLI output prints the version URL and the exact command another builder should run, such as:

nemu use shop_build@v2
nemu verify --sum

Review /dashboard/blueprints for version stewardship, /dashboard/publishes for publish history, /dashboard/audit for audit-chain health, and /docs/trust for signed nemu.sum behavior.

Invite-gated for launch

Nemu is curated at launch. If you are not invited yet, contact the owner for access.

Yank and un-yank are owner-only controls. Publishing tokens are shown once, scoped to publish:blueprints, and never displayed again.

Verified boundary

Verified on 2026-07-19 against the local Nemu CLI and registry fixtures.

This page does not claim physical deployment, live Codex publish proof, or Claude Code success. Those remain final-run evidence tasks.