# Required adoption limits

Host-admitted currency and issuer fields are assertions from a trusted caller, not authenticated evidence. A complete independent host must resolve source/policy/catalogue pins; verify exactness, valuation compatibility, aggregation purpose, allowed signs, identity and rights; authenticate actors; enforce storage/CAS, read/write permissions, retention and current status. The calculation proves only its arithmetic on supplied inputs.

256 input amounts and 256 existing, 256 incoming and 256 unique merged receipt records are bounded reference limits. A production store needs a separately reviewed paging/history design. Read the full pinned ZIP: native installation copies only specification, AGENTS, runtime path schema, nested schema and companion code. It is not the whole adoption documentation. No source data is automatically fetched or sent anywhere.

No ISO/SI/accounting conformance, cash settlement rule, live currency resolver, source authentication, digital signature, payment, ledger, tax, uncertainty, FX feed, general numeric engine, calendar availability, translation service, real-company profile or existing-Dimension migration is claimed. EM-XCT-06 remains incomplete after this slice. Parent models retain all their research holds. No whole-parent inheritance is asserted.

## Bounded native and storage contract

This reference has a hard lifetime limit of 256 receipt IDs per Dimension, including every correction and historical receipt. It requires the complete Dimension-wide register for this model. Splitting registers or omitting old leaves loses same-ID conflict detection and is unsupported. This is a bounded adoption fixture, not a production store; production paging/indexing/retention requires a separately reviewed design.

validate_native binds the genesis object record only. It does not discover or authenticate the current head, later object revisions, current access/state, or later fact supersession. Object revision, retirement and native retraction are outside this version. A trusted host must inspect full native history and current permissions before access; passing an old genesis record never proves current access. Native record timestamps are strict UTC seconds, without fractional seconds.

The same closed resource bounds apply to receipt JSON and native envelopes: depth 16, 32 keys per object, lists at most 256, generic strings at most 512 characters, integer magnitude at most 9999, and 2 MiB canonical/wire size. This intentionally accepts a narrower envelope vocabulary than general V3. Schema-specific bounds may be tighter.