lispex embed run

The invocation topaz lispex embed run main.tpz --language-version 5.21 is expected to exit with 2.

Arguments and rejection

Require exactly one each of --source <rule.lspx>, --input <value.lpxvalue>, --limits <limits.json> and --output <new-directory>. Their order is free. Paths are nonempty separate arguments and may not be mistaken for another option.

Reject positional operands, missing or repeated options, equals forms and all unlisted options. In particular reject compiler, language, root and output format selectors.

Read source, input and limits as named regular files. Reject symlinks and special files. The limits file is UTF-8 JSON using topaz.lispex-embed-limits/v1 and is at most 65536 bytes. Source and canonical input must satisfy the byte ceilings declared by those limits.

Output

A successful invocation writes no report to standard output. It publishes report.json using topaz.lispex-embed-run-report/v4 in the requested directory. Publish result.lpxvalue only when the settled outcome supplies a canonical result.

The report contains schema, admission, execution, operations, outcome, semantic and portableProviderReceipt. outcome records string fields category, operation and code. semantic records the admitted component and codec identities, limits and source and input digests, with a result digest or null. The Lispex outcomes contract distinguishes canonical settlement from admission and interrupted attempts.

Human usage, refusal and engine explanations use standard error. There is no human rendering of the result directory and no --format option. Its fixed JSON report and canonical value file are artifacts of evaluation.

Exit status

Exit 0 only after the complete settled report has been published. A semantic failure or limit exhaustion recorded by the evaluator is a settled outcome and still exits 0.

Exit 2 for CLI usage errors or an unreadable, oversized, non UTF-8 or invalid limits file.

Exit 3 for source or canonical input refusal, size violations, an invalid or already existing output destination, inability to reserve staging storage, or failure to write or publish the output without replacement.

Exit 4 for evaluator identity or selection failure, violated component contracts, engine faults or operational failures inside the evaluator.

Filesystem effects

The output parent must already exist. Require a new UTF-8 directory name and reject every existing destination, including an existing empty directory or symlink.

Write report and result files into a private sibling staging directory. Publish that directory without replacement only after every required file has been written. A competing creation of the destination is a refusal.

On failure retain the caller source, input, limits and existing destination bytes. Remove only the staging directory created by this invocation. A failure to clean private staging must not authorize deletion elsewhere.

Network access

The admitted evaluator is embedded in the executable. Do not discover, download or fall back to another evaluator. Evaluation has no filesystem, network or process capability.

Reproducibility

With identical source bytes, canonical input bytes, limits, evaluator bytes, runtime policy, target and product release, a settled report and result have identical bytes.

Private staging names and host operational failures are outside the semantic result. An engine fault or transport refusal must not be rewritten as a deterministic semantic outcome.

Packages and locks

This command does not load topaz.toml, topaz.lock or a registry. Relative paths are resolved from the invocation directory and do not select a package.

The embedded component identity is fixed by the installed product. There is no component selector, dependency resolution or lock update.