Home / Docs / Specification / 13. Diagnostics, Agent ABI and project files
13.6 Build report
una report --json produces:
{
"schema": "una.report/2",
"package": { "name": "events-example", "version": "0.1.0", "profile": "app" },
"edition": { "name": "0.1", "preview": false },
"lock": { "solver_version": "...", "hash": "..." },
"proven": { "semantic": 14, "security": "by typing", "authority": "by typing" },
"obligations": { "proven": 14, "refuted": 0, "unknown": 0, "cached": 14 },
"authority": [ { "function": "events.checkin.check_in", "public": true, "uses": ["@registrations: Registrations[find]", "@audit: Audit[record]", "@keys: Keys[hmac]"], "inferred": false } ],
"handler_authority": [],
"dependencies": [],
"information": { "policy_calls": [ { "policy": "events.keys.attendee_key", "purpose": "...", "owner": "privacy", "site": { "file": "...", "start": { "line": 30, "col": 13 } } } ] },
"escapes": { "checked": [ { "module": "events.types", "count": 1, "budget": 1 } ] },
"assumptions": [ { "capability": "events.checkin.Registrations", "operations": ["find"], "ensures": [] } ],
"premises": [ { "id": "H1", "statement": "...", "used_for": [] }, { "id": "H2", "statement": "...", "used_for": [] }, { "id": "H3", "statement": "...", "used_for": [] }, { "id": "H4", "statement": "...", "used_for": [] }, { "id": "Env", "statement": "...", "used_for": [] }, { "id": "H5", "statement": "...", "used_for": [] } ],
"tcb": { "trusted_modules": [ { "module": "events.keys", "lines": 17 } ], "host_capabilities": ["Keys"], "solver": "z3 <version>", "proof_cache": ".una/cache/", "proof_cache_key": "~/.una/proof-cache.key", "registries": [], "dependency_trust": [], "serve_grants": [], "server": null, "tls": null },
"requirements": [ { "id": "EVENTS_3", "status": "active", "derived": ["events.seating.availability"] } ],
"coverage": { "pub_functions": 3, "with_ensures": 1, "with_derived_from": 1, "trivial_ensures": 0 },
"native": { "target": "aarch64-apple-darwin", "arbitrary_precision": ["events.seating.clamp_seats.raw"], "kernels": { "variants": ["baseline"], "fma_allowlist": ["una_core::dense::variants::x86_64_v3", "una_core::dense::variants::x86_64_v4"] } },
"out_of_model": ["timing", "termination and divergence", "resource consumption and allocation", "stack exhaustion", "external systems beyond declared signatures", "races between the check and the use of a file path", "hard links", "order of effects across concurrent tasks", "the time of a host stop", "interference of the host's load with the timing of an expression", "uncatchable termination", "waits at limits and at `start`", "which branch of `first of` wins, beyond its label"],
"warnings": []
}trivial_ensures counts ensures clauses the solver proves valid without any hypothesis (for example ensures true); they are reported as missing contracts.
una report [path] checks the package at tier 1. When the checks report diagnostics, it prints them as una check does; otherwise it prints the report, and exits with code 1 when an obligation is not proven. Its sections, in the order of the example (ADR 0034):
-
package: the name and version ofuna.toml, or ofita.unafrom edition0.4; a single file is named after its module, with version0.0.0. (v0.3, ADR 0109 rules 4 and 7.) Thenprofile,"app"or"systems", andmax_memory, the declared memory budget in MiB, only when the manifest declares one; the human form prints them asprofile: systemsandmax memory: 256 MiB. Both keys are additive, and the schema staysuna.report/2. -
edition(ADR 0121 rule 8):name, the package's edition, andpreview, whether this release serves it as a preview (§7); the human form printsedition: 0.1, oredition: 0.5 (preview). The key is additive, and the schema staysuna.report/2. This release does not emit rule 8's third key,preview_constructs, each construct of a preview edition the package uses: it lands with the edition ledger of ADR 0121 rule 9 (#1752). -
lock: the solver version, and the hex SHA-256 of the lock's contents (for a single file, of the default lock's text; from edition0.4, ofita.lockas written, spec/30 §7). -
proven: the number of proven obligations assemantic;securityandauthorityare"by typing".obligations: the counts by status, thencached, how many of these results came from the proof cache of spec/12 §9 rather than from the solver (ADR 0041). -
authority: every function of the package withuses, by qualified name, withpublic, itsusesas written in a header, and whether they are inferred. (v0.2, ADR 0062.) Auses of pclause is listed as written, as"of each". The effects of a lambda count for the function that writes it, within itsuses. -
handler_authority(v0.2, ADR 0081), afterauthority: every handler of the package withusesclauses, by qualified name, withcapability, the capability it implements by its qualified name,public, and itsusesas written in its header, in the form ofauthority. A handler'susesare always written, so an entry has noinferred. The key is additive, and the schema staysuna.report/2(ADR 0076). -
dependencies(edition0.4, ADR 0122 rule 58), afterhandler_authority: every package of the program other than the root, in name order, with its source, digest, the ceiling each dependent writes for it, its effective ceiling, the authority its code uses, and the trust it adds (spec/30 §12 rule 8). A package with no dependencies has[]. The key is additive, and the schema staysuna.report/2. -
information.policy_calls: every call of a policy, in source order, with the policy, its purpose and owner, and the site. -
information.timing(edition 0.4, ADR 0116 rule 21), afterpolicy_calls: eachfor ever within, in source order, as{"construct": "for ever within", "function": "m.f", "label": "internal", "site": {...}}, with the timing label of its body (spec/26 §7), and (ADR 0117 rule 13) eache within dwhose timing label is abovepublic, as{"construct": "within", ...}, with the timing label ofe(spec/27 §5), and eachfirst ofwhose timing label is abovepublic, as{"construct": "first of", ...}, with the join of the timing labels of its branches (spec/27 §6), and (#1708) each check point whose count data abovepublic, at mostinternal, decide in a package whose program can run started tasks, as{"construct": "task switch", ...}, with that label (spec/27 §8 rule 5), and (ADR 0116 amendment of 2026-11-09, accepted, #898) each reading ofClock.nowwhose timing labelL_clkis abovepublic, as{"construct": "Clock.now", ...}, with that label (spec/14 §3), all in source order. Atask switchor aClock.nowin a handler's operation body names the handler,m.h, as itsfunction. The report of a package that its diagnostics refuse has notask switchentry: the list is of an accepted package. The key is absent when the list is empty, so the reports of earlier editions do not change, and the schema staysuna.report/2. -
escapes.checked: every module that useschecked, with the count and the budget ofuna.toml. -
assumptions: every capability the package declares, with its operations and theirensuresclauses asop: clause. -
premises(ADR 0094 rule 5), afterassumptions: the premises on the host that the acceptance of a package rests on, the Assumed zone's part that the deployment, not the package, must make true. They are assumed, never proven: neitheruna checknor the formal model establishes them. Each is an object{"id": "H1", "statement": "...", "used_for": [...]}, in this order, with the statement as written here:- H1: whether a read fails depends on the path and on which files exist, not on their content.
- H2: whether a write fails, and which files it leaves, does not depend on what it writes.
- H3: a response does not depend on the program's type annotations (the host is given text).
- H4: every successful HTTP response is a
Responseof spec/24. - Env: the environment variables that exist are the same in both runs; their values may differ.
- H5: what an operation answers through a binding where it is labeled l′, and whether it fails, is a function only of the arguments and of the part of the host state at or below l′.
A premise is listed with what the package uses it for, in
used_for: for H1 to H4 andEnv, the operations of host capabilities (spec/14 §3, not a package capability of the same name) that theusesof the package's functions and handlers list and that the premise covers, asCapability.opin name order (Files.readfor H1,Files.writefor H2, every operation ofHttpfor H3 and H4, every operation ofEnvforEnv); for H5, every operation that theusesof a function's or a handler's header labels withgives, asmodule.function: @binding.op gives labelormodule.handler: ..., functions first and then handlers, each by module and in declaration order. An operation is listed when a header lists it, whether or not the body calls it, soused_formay over-list, never under-list. A premise the package does not use is listed with[]: the set of premises is the model's, not the package's. A labeled operation is accepted on the checker's rules alone until the formal model covers operation labels (#563,docs/plan/formal-track-status.md). Without--json, the section prints asassumed of the host:, one line per premise,H1: used for Files.read, orused for nothing. The key is listed for a package of every edition, since H1 to H4 andEnvare premises of the model in each; it is additive, and the schema staysuna.report/2(ADR 0076). -
tcb: the trusted modules with their line counts, the host capabilities the package's functions and handlers use (handlers since ADR 0081;HttpServeralso for a package that serves, edition 0.4 preview, spec/31 §7 rule 6), the solver asz3 <version>, andproof_cache, the proof cache of the package,.una/cache/. In v0.1 its entries were trusted, not authenticated (ADR 0041). (v0.2, ADR 0064.)proof_cache_keyfollows: the key file that authenticates the cache's entries and is in the Trusted zone. It is~/.una/proof-cache.keyfor the default, or the value ofUNA_PROOF_KEYas given, andnullwhen the run used no cache.registriesanddependency_trustfollow (ADR 0122 rule 58, spec/30 §12 rule 8): each registry source of the program with the digest of its root metadata, and the trusted modules of dependencies that the root consented to, with their line counts, by package;trusted_moduleskeeps the root's own. (v0.4, ADR 0124 rules 7 and 28.)solver_buildfollows, an object withsource_sha256andlibrary_sha256, the digests of the Z3 source tarball and of the library built intouna, present whenunahas the solver built in; thensolver_confinement,"own"when the solver children confined themselves and"outer"when an outer sandbox did, present when a child ran; and, under"outer",solver_outer_denied, the probes of the fixed list of ADR 0124 rule 7 (as its amendment of 2026-11-01 states it) that the outer sandbox denies, in that order, each named by its operation and, when it has one, its filter or place, such asnetwork-outbound,network-outbound tcp 127.0.0.1,network-bind unix-socket,file-write-finderinfo /Usersorfile-write-data (home). A probe is listed when it is denied under the outer sandbox, by the profile or by the system (the system denies some writes at some places whatever the profile), so the list does not say the profile denied a probe. Under"outer"the list names every probe that the minimum requires to be denied, and may also name recorded ones (reads,file-revoke,process-exec*,process-fork). The keys are additive, and the schema staysuna.report/2. -
requirements: every requirement, by identifier, with its status and the functions derived from it. -
coverage:pub_functionscounts the public functions,with_ensuresthose with at least oneensuresclause that is not trivial,with_derived_fromthose with aderived fromclause, andtrivial_ensuresthe trivial clauses of public functions. Anensuresclause is trivial when the solver proves it with no hypothesis, its parameters andresultunconstrained: one more query per clause of a public function, cached like the others; a solver that cannot answer these queries gives U5003 or U8001 instead of the report. -
native(v0.2, ADR 0055):target, the host target ofuna build(spec/16 §1), andarbitrary_precision, the bindings whoseIntthe native backend keeps at arbitrary precision: every parameter and result of typeIntof the package's functions whose refinements do not prove a range within a machine word, asmodule.function.parameterandmodule.function.result(NB-3, FW-1). A parameter's refinements are proven by each call and a result's by the function, soclamp_seats, whose result isSeats = Int in 0..5000, lists only its parameter.kernels(ADR 0120 rules 56 and 57, and its Appendix A amending ADR 0106) follows:variants, the variants of the dense kernels that an executable for the host target holds and chooses among once at start, by the processor's features (baseline,x86_64_v3andx86_64_v4on x86-64;baselineelsewhere), andfma_allowlist, the demangled symbol prefixes inside which an x86-64 release artifact may hold an FMA instruction, which the FMA disassembly gate ofdocs/release-gates.mdreads. The allowlist is the same on every host, since it describes the x86-64 artifacts the gate scans. The key is additive, and the schema staysuna.report/2. Without--json, they print as the lineskernels:andfma allowlist:. (v0.4, ADR 0124 rules 14 and 28, step 2.)runtime_sha256follows, the SHA-256 of the runtime library built intouna, which every executable it builds links (spec/16 §2 rule 8), present whenunahas the runtime built in, so absent in a development build; without--jsonit prints as the lineruntime sha256:. The key is additive, and the schema staysuna.report/2. (v0.4, ADR 0124 rule 28, step 3.)linkerfollows, the linker ofuna buildon the host:una <version>whereunalinks by itself (spec/16 §6),ccwhere the system linker links; without--jsonit prints as the linelinker:. Thendebuggable, whether an executable thatuna buildmakes without--debuggablelets a debugger attach:falsewhere the internal linker signs it with the hardened runtime (spec/16 §2 rule 9),truewhere the system linker links it. Both keys are additive, and the schema staysuna.report/2. -
generic_results(v0.2, ADR 0067), afternative: every public generic function of the package, by qualified name, with itsresult_labelsasuna contractprints them, or[]for one whose summaries are all empty (spec/07 §7 rule 8), and itsof_raises, asuna contractprints them. The key is additive, and the schema staysuna.report/2. -
out_of_model: the channels outside the model of spec/07 §1, in this order: timing, termination and divergence, resource consumption and allocation, stack exhaustion, external systems beyond declared signatures, races between the check and the use of a file path, hard links, order of effects across concurrent tasks, the time of a host stop, interference of the host's load with the timing of an expression, uncatchable termination, waits at limits and atstart, and which branch offirst ofwins, beyond its label (spec/14 §3 for hard links; v0.2, ADR 0065 and spec/19 §3 for the order of effects, which the list gained with the release that implements spec/19; ADR 0116 rule 21 and spec/26 §6 for the time of a host stop, the interference of the host's load and uncatchable termination, and ADR 0117 rule 13 and spec/27 §6,§7,§9and§10for the waits atstart, at the limits of grants and at alimiter, and the winner offirst of, additions withinuna.report/2). (Edition 0.4 preview, ADR 0123 rule 22, spec/31 §7 rule 6.) A package with aserve:grant or aservesection gains, at the end ofout_of_model, the three entries of the server. -
tcb.serve_grants,tcb.serverandtcb.tls(edition 0.4 preview, ADR 0123 rule 22), after the other keys oftcb: eachserve:grant with its address, scheme, limits and whether it checksHost,[]for none; the host's server code,"una-http/serve", for a package that serves, elsenull; andnullwhile no TLS server is built (spec/31 §7 rule 6). -
warnings(edition 0.4 preview, ADR 0123 rule 22), afterout_of_model: the report's warnings about the package'sserve:grants,[]when none (spec/31 §7 rule 6). The keys are additive, and the schema staysuna.report/2.
Without --json, the same sections print as labeled lines.
(v0.2, ADR 0055.) The report is una.report/2 from the first release that ships una build (spec/16), v0.2.0-alpha.1: it added the section native, and the out_of_model entry "interpreter stack exhaustion" became "stack exhaustion". Releases up to v0.1.2 write una.report/1.