CLI readiness
Runtime is in development. These guides explain design intent; they are not a released API or installation reference. Read the release policy →
Current status
Section titled “Current status”There is no public Runtime CLI distribution on this site. No zernova commands, package coordinates, flags, exit codes, or installation paths are specified. Do not infer a command interface from the product name.
What a future reference must establish
Section titled “What a future reference must establish”A release-specific CLI reference needs a reproducible installation procedure and a tested compatibility matrix. Each documented command must identify required inputs, side effects, output, failure reporting, and exit status.
| Area | Required evidence |
|---|---|
| Installation | Verified artifact, authenticity and integrity procedure |
| Validation | Valid and invalid input fixtures, stable diagnostics |
| Execution | Lifecycle, shutdown, interruption, and failure behavior |
| Automation | Non-interactive operation and machine-readable results where supported |
| Secrets | Safe input methods and redaction behavior |
How to prepare now
Section titled “How to prepare now”Document the workflow you need rather than inventing commands. For example: validate an integration without remote side effects, run a local test with isolated credentials, and identify why execution failed.
The future command reference should show commands copied directly from release tests. Examples need to run from a clean directory with stated prerequisites. Dangerous or externally visible actions need to be identified before execution.
Find actual availability
Section titled “Find actual availability”The downloads page will identify approved artifacts when they exist. The release lifecycle describes the publication checklist. Local commands for developing this public website belong in the web repository README and do not imply a Runtime CLI.