---
title: "una.version/1"
url: https://una-lang.org/en/docs/agents/schemas/una.version-1/
release: v0.4.0
source: https://github.com/una-lang/una/blob/v0.4.0/docs/spec/13-diagnostics-and-abi.md
---

# una.version/1

`una.version/1` is a JSON document of the Agent ABI, defined in `spec/13 §5`. This page gathers what the specification says about it at v0.4.0: each section whole where it opens with the document, and otherwise the parts that name it.

## Command line

From `spec/13 §5`, the parts that name this schema.

Global flags: `--json` (machine output on stdout, nothing else on stdout), `--color never|auto|always`. (v0.4, ADR 0124 rule 3.) `una __solver` is internal: the solver child that `una check` starts (`spec/12 §5`); it is not listed by `--help`, and its interface may change in any release. (v0.2, #305.) `una --version` prints the version of `una`, the editions it serves and the Z3 version its default lock pins, one per line, as `una 0.4.0`, `editions: 0.1, 0.2, 0.3, 0.4, 0.5`, `z3: 5.1.0` for v0.4.0. (v0.3, ADR 0056 amendment.) A version that serves edition `0.3` lists it, as it lists every edition it serves. (ADR 0121 rule 7.) After `editions:`, a line `preview: ` lists the editions this release serves as previews, those that §7 marks "is a preview", comma separated, as `preview: 0.3, 0.4, 0.5`; a release with no preview prints no such line. With `--json` it prints `{"schema":"una.version/1","version":...,"editions":[...],"preview":[...],"z3":...}`, with keys in that order; `preview` is always present, `[]` when there is none, and is additive within `una.version/1`. Neither names a commit, so a build of a version prints the same text from any checkout. (v0.4, ADR 0124 rule 19.) A development build, one built without the solver taken by digest or (ADR 0124 step 2) without the runtime built in, prints `development build` as its last line, and with `--json` adds a last key `build` with the value `development`; a release build prints neither, and `z3` names the solver built into it. `una` with neither a command nor `--version` is a usage error. (v0.4, ADR 0124 rule 6.) Every command that takes `--solver-wallclock` also takes `--solver-memory <MiB>`, the memory limit of each solver query, an integer from 256 to 1,048,576 (default 4096); another value is a usage error. Exit codes (ADR 0036): `0` success; `1` the output holds at least one error diagnostic with a registered code, or reports an obligation that is not proven (`una obligations`, `una trace`, `una report`) or a failed example (`una test`); `2` a usage error, a problem of the invocation (its flags, grants, paths or names) printed to stderr without a code, with no diagnostic document on stdout; `3` internal compiler error (U8001). A problem of the project files is a diagnostic like any other, in human and `--json` output: an invalid `una.toml` (U7002) and a missing or invalid `verification.lock` (U7004) exit with `1`.
