Canonical Settlement Intent
1. ABSTRACT
Defines the canonical structure of a Settlement Intent (I), the object a participant submits to express a desired economic outcome prior to obligation compilation.
2. MOTIVATION
A minimal, canonical intent structure is required before obligations can be compiled deterministically. Without a fixed shape, downstream compilers cannot be verified against a shared reference.
3. TERMINOLOGY
Settlement Intent (I) — a participant's expressed desired economic outcome, prior to compilation into an Obligation Object.
4. SPECIFICATION
I {
originDomain: DomainID
desiredDomain: DomainID
notional: Decimal
unit: CurrencyCode
maxExecutionWindow: Seconds
disclosurePreference: MINIMAL | STANDARD | DISCLOSED
}
An intent MUST NOT reference a specific execution path, corridor, or Human Settlement Cell. Binding an intent to specific infrastructure is the responsibility of the compiler (NIP-0002) and router (NIP-0003), not the intent itself.
5. INVARIANTS
An intent MUST NOT reference execution path, corridor, or HSC. `maxExecutionWindow` MUST meet or exceed the network minimum.
6. FAILURE CONDITIONS
Intents with an invalid `originDomain`/`desiredDomain` or a below-minimum `maxExecutionWindow` MUST be rejected before an Obligation Object is compiled.
7. SECURITY CONSIDERATIONS
Intents are considered untrusted input. A compiler MUST validate `originDomain` and `desiredDomain` against the current domain registry before compiling an Obligation Object, and MUST reject intents with a `maxExecutionWindow` below the network minimum to avoid unroutable obligations flooding the graph.
8. REFERENCE IMPLEMENTATION
The reference implementation is the NIL-0 simulation network. No production implementation of this proposal exists; behavior described here is normative for the simulation only.