본문으로 건너뛰기
토파즈6.0 · 출시 전
다운로드 →

문서 검색

명세 6.0

방향키로 결과를 고르고 Enter를 눌러 여세요.

API 이름, 진단 번호, 규칙 또는 프로젝트 주제를 입력하세요.

    도구

    lispex embed run

    Runs an exact bounded embedded Lispex request.

    Invocation, options and results

    링크

    topaz lispex embed run

    호출 형식
    1. topaz lispex embed run --source <rule.lspx> --input <value.lpxvalue> --limits <limits.json> --output <new-directory>

    입력

    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.

    옵션과 충돌

    옵션기본값계약충돌
    --source <rule.lspx>미지정

    Takes the indicated value. Required.

    없음
    --input <value.lpxvalue>미지정

    Takes the indicated value. Required.

    없음
    --limits <limits.json>미지정

    Takes the indicated value. Required.

    없음
    --output <new-directory>미지정

    Takes the indicated value. Required.

    없음

    출력 채널

    stdout

    stderr

    종료 상태

    0

    A complete settled evaluator report is published, including a recorded semantic failure or limit exhaustion.

    2

    Command usage or limits file validation fails.

    3

    Source or input admission, output destination checks, staging, writing or publication without replacement is refused.

    4

    Evaluator selection, admitted component verification, an engine contract or engine operation fails.

    효과

    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.

    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.

    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.

    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.

    Operation

    링크

    Supply the embedded evaluator request shape accepted by the installed component. Language and resource constraints belong to that request.

    Example contract

    링크
    규칙tools-commands-lispex-embed-run.rule.invocation

    Example contract

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

    The restricted embedded-evaluator parser rejects the positional fixture operand. No evaluator request is executed and no output directory is created.

    이유

    An evaluator request names its source, input, limits, and output separately. Rejecting an unlabelled operand prevents a path from being assigned the wrong role.

    Behavior contract

    링크
    규칙tools-commands-lispex-embed-run.rule.behavior

    Command behavior

    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.

    이유

    Source, canonical input, limits and output have different roles and require named path options. A settled language outcome is useful output even when evaluation fails semantically. Separating that outcome from usage, refusal and engine failures preserves the evidence the caller requested.

    The linked public CLI recipe checks the exact displayed argument rejection before the requested operation. It does not execute the successful operation or verify its effects.

    The reviewed recipe only checks rejection of a positional source operand. Evaluation with three input files and creation of an output directory is outside the execution allowlist.

    Example

    링크

    Argument-rejection example

    링크
    main.tpzArgument-rejection example플레이그라운드 열기 →
    1. function identity<T>(value: T) -> T {
    2. value
    3. }
    대상 제품 5.21.3
    기대 결과

    기대 결과

    Textual rejection details remain Pending in the reference model. The independent Tools example gate expects exit 2.

    The restricted embedded-evaluator parser rejects the positional fixture operand. No evaluator request is executed and no output directory is created.

    Verification scope

    링크

    Observed with Topaz 5.21.3 on 2026-11-06T08:36:29.642Z. This invocation passed; exit 2. 3 assertions were evaluated against the independent expected result. Execution record. This result covers the displayed invocation.

    Related references

    링크

    Compiler selection →

    Packages, locks and targets →

    메뉴

    다운로드 →