Invocation, options and results
Ссылкаtopaz compiler validate
topaz compiler validate <dir>
Ввод
Use topaz compiler validate <dir> with exactly one observation directory and no options.
Reject a missing or extra operand, every compiler, root, language, terminal or format selector, equals forms and all unknown options before loading the bundle.
Require the admitted observation bundle schema and all mandatory members. Reject malformed JSON or JSON Lines, unsupported schemas, duplicate or unsafe member paths, missing members, digest mismatches, nonregular members and symlinks.
Параметры и конфликты
| Параметр | Значение по умолчанию | Контракт | Конфликты |
|---|
Каналы вывода
stdout
stderr
Статус завершения
0
The supplied complete observation bundle is valid, including a bundle that records compiler rejection.
1
Arguments, input access or observation bundle validation fails.
Эффекты
Read the supplied directory without modifying, repairing or regenerating any member. Reject symlinked members rather than following them outside the bundle.
Do not allocate a compiler workspace, produce a new bundle, delete extra files or rewrite a digest.
Perform no network access and no lookup of missing schemas or source files from remote locations.
The same bundle bytes and member paths under the same validator schema registry produce the same validity result. Directory enumeration order does not affect it.
Human paths and operating system error details are environmental output. A valid bundle does not depend on the original source tree still being available.
Do not load a package from the current directory or regenerate package facts. Package and lock facts stored in the bundle are validated as evidence rather than resolved against a live registry.
The command does not create, verify against the caller package or rewrite its topaz..
Operation
СсылкаUse validate before comparing or consuming observation files. Validation checks an existing bundle.
Example contract
СсылкаExample contract
The invocation topaz compiler validate main. is expected to exit with 1.
This command does not provide a JSON report format. The invocation is rejected during argument validation before processing the program.
Причина
This command does not provide a JSON report format. Rejecting the option prevents a successful exit from silently ignoring the requested output format.
Behavior contract
СсылкаCommand behavior
Arguments and rejection
Use topaz compiler validate <dir> with exactly one observation directory and no options.
Reject a missing or extra operand, every compiler, root, language, terminal or format selector, equals forms and all unknown options before loading the bundle.
Require the admitted observation bundle schema and all mandatory members. Reject malformed JSON or JSON Lines, unsupported schemas, duplicate or unsafe member paths, missing members, digest mismatches, nonregular members and symlinks.
Output
Write one human confirmation identifying the directory and its valid observation status to standard output only after the complete validation succeeds.
Write the first validation or input failure to standard error and emit no success confirmation for an invalid bundle. There is no stdout JSON report and - is rejected.
Validation covers the manifest, declared members, schemas and internal consistency. It does not claim the observed program compiles successfully or that two different compiler implementations agree.
Exit status
Exit 0 for a valid complete observation bundle, including a valid bundle that records a compiler rejection.
Exit 1 for command misuse, unreadable input, an invalid directory or any bundle validation failure.
Filesystem effects
Read the supplied directory without modifying, repairing or regenerating any member. Reject symlinked members rather than following them outside the bundle.
Do not allocate a compiler workspace, produce a new bundle, delete extra files or rewrite a digest.
Network access
Perform no network access and no lookup of missing schemas or source files from remote locations.
Reproducibility
The same bundle bytes and member paths under the same validator schema registry produce the same validity result. Directory enumeration order does not affect it.
Human paths and operating system error details are environmental output. A valid bundle does not depend on the original source tree still being available.
Packages and locks
Do not load a package from the current directory or regenerate package facts. Package and lock facts stored in the bundle are validated as evidence rather than resolved against a live registry.
The command does not create, verify against the caller package or rewrite its topaz..
Причина
Validation asks whether supplied evidence satisfies its schemas and digests. Recompiling or repairing the bundle would answer a different question and could hide corruption in the original evidence.
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 tests rejection of the unsupported JSON format option. Valid and corrupt observation bundles are outside the single source file execution fixture.
Example
СсылкаArgument-rejection example
Ссылкаfunction identity<T>(value: T) -> T {value}
Ожидаемый результат
Ожидаемый результат
Textual rejection details remain Pending in the reference model. The independent Tools example gate expects exit 1.
This command does not provide a JSON report format. The invocation is rejected during argument validation before processing the program.
Verification scope
СсылкаObserved with Topaz 5.21.3 on 2026-11-06T08:36:29.642Z. This invocation passed; exit 1. 3 assertions were evaluated against the independent expected result. Execution record. This result covers the displayed invocation.