Authoring blueprints

verified_on: 2026-07-19

Recipe anatomy

A blueprint is a finished project translated into files an agent can verify and run.

• Put the recipe under ai-automation/.
• Keep ai-automation/nemu.manifest.json as the source of truth for metadata, inputs, services, steps, and final verification.
• Use the seeded shop_build blueprint as the executable reference.
• Keep examples concrete; avoid placeholder product names that hide required inputs.

Write steps agents can finish

• Each step should name one goal, the allowed_actions it needs, and the verify command that proves completion.
• Codex should stop when required inputs are missing or any {{...}} marker remains unresolved.
• Provider credentials stay in the user's local CLIs, browser sessions, or provider settings. Nemu never receives them.

Skeletonize safely from self-owned software

Only skeletonize projects you wholly own. Client-owned or client-derived code is not eligible for Nemu publishing.

nemu scan --path .
nemu skeleton export --path . --i-own-this
nemu scan --path <exported-skeleton>

Before publishing, scan the export. It must return zero fail-severity findings.

ai-automation/skeleton-report.json is private evidence and is excluded from public mirrors.

Real-project founder review remains manual until M26 is complete.

Create an automated skeleton from self-owned software

Only skeletonize software you wholly own. Client-owned or client-derived code does not belong in Nemu.

# inside Codex after installing generated prompts
/create_automated_skeleton
# alias
/nemu_skeletonize

The command inventories the project, runs the scan/export loop, writes Manifest v2 recipe files, runs validation and lint, records a diff summary, and stops for author review.

The skeletonizer stops at review. It does not publish.

Publishing stays separate:

/nemu_publish

Real proof projects remain M9 until the founder selects self-owned targets.

Declare hosts and services

Use declared_hosts for any host that recipe text or verification commands contact. The safety linter fails executable egress that is not declared.

Run the safety checks

nemu validate
nemu lint
nemu verify --sum

Fix validation errors in the manifest first, then use /docs/safety-linter for lint findings. If signed verification fails, refresh with nemu pull --sum before asking an agent to continue.

Verified boundary

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

This page is local-evidence accurate. Live invited-author walkthrough evidence remains tracked separately until launch.