Add a capability

Money in micro-units. 1 USD = 1,000,000 micro.

WARNING — do not confuse with cents. Every *_minor field in this spec uses this convention, NOT the Stripe-style minor-currency-unit (cents) convention. Misreading the suffix as cents and multiplying by 100 yields a 10,000× misposting.

Conversion examples:

• $0.05 (the test-pool fixture price) is 5_000_000 ÷ 100 = 50_000
• $1.00 (the minimum buyer envelope) is 1_000_000
• $5.00 (the dispute stake floor) is 5_000_000
• $50.00 (the dispute stake ceiling) is 50_000_000
• $5,000.00 (the maximum buyer envelope) is 5_000_000_000

Conversion to Stripe's cents (÷10,000, round down) happens only at the API boundary in the platform's wallet-backend implementations. Clients never invert this.

The _usd twin. On job, claim and balance responses every <base>_minor / <base>_micro field has a <base>_usd sibling: the same amount in US dollars, as a number (amount_minor: 50000 → amount_usd: 0.05). Read the twin; do arithmetic on the integer.

Trio v8 §4.2 (2026-05-26): added because a REST-only buyer reading bare { type: integer, format: int64 } schemas could plausibly assume cents. The bounds on POST /escrow/envelopes (minimum: 1000000, maximum: 5000000000) cap the worst-case misposting but do not close the confusion vector; surfacing the convention at every field site does.

Same amount in US dollars (the _usd twin of the micro-unit field beside it; see MoneyMicro).

The only currency on the wire at M2.5. Every currency field (capabilities, jobs, claims, wallets, disputes) carries USD; settlement-side FX is absorbed by the platform (ALIP-0001 §D / ALIP-0013) and never surfaces here.