← Command reference · lean-pkg palomar · CLI overview

lean-pkg palomar prepare

build the submission bundle (formalization.yaml, comparator configs, receipts, README.txt, MANIFEST.sha256); event palomar-prepared.

Usage

lean-pkg palomar prepare [--out DIR] [--dry-run] [common flags] NAME

[common flags]: --json, --commit, --push, --no-commit, also accepted before the command name; see the CLI overview.

Arguments and flags

Argument or flag	Description
NAME
--out DIR	bundle directory (default <checkout>/.lean-receipts/palomar-<HEAD12>/); must not exist or be empty
--dry-run	run every check and print the plan; write nothing

Details

Form	What it does	Key flags
palomar prepare NAME	build a Palomar submission bundle; no network request, nothing submitted. Default directory <checkout>/.lean-receipts/palomar-<HEAD12>/ (--out DIR elsewhere; an existing non-empty target is refused, never overwritten): formalization.yaml (the renderer’s output, schema-valid; placeholders are warnings), configs/<path> (every comparator configuration tracked at HEAD, byte-identical, and the headline configuration when one is declared; README.txt names it for the main-results entry and its record command; JSON headline_config), receipts/<file> (the recorded gate and comparator receipts, validated against HEAD: bound to it or to an evidence-only ancestor), README.txt (the manual steps, the Palomar URLs and the record ... palomar-submitted command), MANIFEST.sha256 (sha256 path per file; sha256sum -c MANIFEST.sha256). Refused (exit 1, nothing written, --dry-run included) without either receipt or when one is not bound to HEAD, without consent, when the render fails the schema, when palomar check finds any error gap at HEAD (each listed as ✗ CODE: detail with its fix; warn gaps never refuse and print as lean-pkg: warning: palomar check: ...), or on blocking public-safety hits in the bundle (scanned like a fresh-history export). Records palomar-prepared {commit, bundle, bundle_sha256 (sha256 of MANIFEST.sha256)}. --dry-run runs every check and prints the plan, writing nothing. --json: {ok, name, dry_run, bundle, commit, configs[], files[], bundle_sha256, placeholders[], public_safety {block_hits, warn_hits}, palomar_check {ready, commit, errors, warns, codes[], command}, manuscript_findings, warnings[], event}; manuscript_findings is the claims ledger’s summary of what the formalization found in the manuscript (one text line when there is one; not in the bundle, never a refusal)	[--out DIR] [--dry-run]