# Boundaries of duty

## What duty does NOT do in 0.2

- `recurring` (periodic duty) is reserved for 0.2: the
  parser does not accept it (see this directory's `README.md`).
- `SATISFIED` for `maintenance` requires a monitoring certificate, a
  closure policy over the whole window, or adjudication; otherwise after the window —
  `UNDETERMINED`. Absence of a counterexample is not performance.
- `VIOLATED` for `achievement` after the window — only on explicit
  non-performance (negative support), a completeness certificate, or
  adjudication.
- There is no contrary `unless C then not Duty` form (`LDC-E1302`).
- PENDING→ACTIVE reads on the case's `legal_time`, not on the system clock.

## Scope

A duty models
a role's behaviour under a norm, fitting wherever there is an addressee; unfit for
laws of nature and theorems (there — `definition`/`rule strict`).

## Known corrections applied

`claim` is rejected in favour of `duty`; forbearance reads as
maintenance of a negation; a tautological goal warns (`LDC-E1371`);
an `unless` range restriction reaches down to the generated `unless` node; a bare
boundary name is rejected; `-infinity` is legal; a power's effect
is invisible to a same-round defeater — an adjacent boundary for
mixed packages.

## Reserved

`recurring`; the `during`/`overlaps`/`before`/`after` predicates — RESERVED
(`LDC-E2102`).

## Neighbour selection rule

- "Shall" + a person + a deadline → `duty achievement`.
- "Must maintain / must not allow" → `duty maintenance`.
- "Is prohibited / is not allowed" → `prohibition`.
- "May / is entitled to" → `liberty`, not `duty` with an empty goal.
- "Is competent to terminate / appoint" → `power`.
- A status with no addressee ("is deemed to have defaulted") → an institutional
  `rule strict` head, not `duty`.