---
title: "una.trace/1"
url: https://una-lang.org/en/docs/agents/schemas/una.trace-1/
release: v0.4.0
source: https://github.com/una-lang/una/blob/v0.4.0/docs/spec/08-requirements-and-examples.md
---

# una.trace/1

`una.trace/1` is a JSON document of the Agent ABI, defined in `spec/08 §1`. 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.

## Requirements

From `spec/08 §1`, the parts that name this schema.

`una trace EVENTS_3` lists every function deriving from the requirement, its contract clauses and the verification status of each obligation. It reads the package in the current directory and checks it at tier 1, then prints the requirement (identifier, status, text, source, owner) and every function derived from it, by qualified name, with its `requires` and `ensures` clauses and the status of each of its obligations. With `--json` it prints `{"schema":"una.trace/1","requirement":{...},"functions":[{"function":...,"requires":[...],"ensures":[...],"obligations":[{"id":...,"kind":...,"status":...,"goal":...}]}]}`. The package's diagnostics, those of its project files included, are reported before the identifier is resolved, with exit code 1 (ADR 0036); in a package without diagnostics, an unknown identifier is a usage error (exit code 2), and an obligation that is not proven gives exit code 1 (ADR 0034).
