---
title: "Requirements"
url: https://una-lang.org/en/docs/language/requirements/
release: v0.4.0
source: https://github.com/una-lang/una/blob/v0.4.0/docs/guide/syntax-reference.md
---

# Requirements

Requirements record human intent with origin and owner, so contracts can be traced to it.

```una
module demo

requirement EVENTS_3
  text "An event with no remaining seats is always shown as sold out"
  source policy "Box Office Handbook 2.1"
  owner box_office
  status active

pub kind Availability = SoldOut | Open

pub availability(remaining: Int) -> Availability
  ensures remaining < 1 implies result is SoldOut
  derived from EVENTS_3
=
  if remaining < 1 then SoldOut else Open
```

| Field | Values |
| --- | --- |
| `text` | the statement |
| `source` | `human`, `policy "<doc>"`, `regulation "<doc>"`, `generated "<task>"` |
| `owner` | accountable team or person (`snake_case`) |
| `status` | `proposed` or `active` |

- **IDs** are unique per package (U1002).
- **Generated requirements must be `proposed`** (U1007). Agents may propose; a person activates a requirement by changing its source.
- **`derived from`** in a function header links the function to requirements; `una trace EVENTS_3` shows the chain from requirement to contract to proof status.

---


## Constructs

- [requirement and derived from](https://una-lang.org/en/docs/language/requirements/requirement.md)
